On 14/05/2021 19:35, Robert McBroom via users wrote:
On 5/12/21 6:46 PM, Ed Greshko wrote:
On 13/05/2021 04:05, Roger Heflin wrote:
Do an "ip route" on both the source and destination nodes.
also do an "ip neigh" on both.
And an "ip link" on both.
Yes, that would be very helpful if Robert would supply that information.
Thanks for making that suggestion
Have to apologize. Cockpit error. The address should have been
192.168.1.211 instead of 192.168.1.112
From the host system
Well, the information below would seem to be incomplete since you probably have not tried to access 192.168.1.211.
We do see FAILED for 192.168.1.112 since you've probably tried it and a host with that IP address doesn't exist.
You can see that for the IPv6 address of 2600:1702:4860:9dd0:210:75ff:fe28:5e30 the hwaddress of 00:10:75:28:5e:30
matches that of eth0 in the "ip link" results of the target system. That would indicate physical connectivity.
So, would you do these in order?
ip -4 add show
ping 192.168.1.211
traceroute -n 192.168.1.211
ip neigh
[rm3]RobertPC ~]$ ip route
default via 192.168.1.254 dev enp2s0 proto dhcp metric 100
10.237.214.0/24 via 192.168.1.254 dev enp2s0 proto static metric 100
192.168.1.0/24 dev enp2s0 proto kernel scope link src 192.168.1.185 metric 100
[rm3@RobertPC ~]$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
link/ether 00:1d:60:35:b8:13 brd ff:ff:ff:ff:ff:ff
[rm3@RobertPC ~]$ ip neigh
192.168.1.254 dev enp2s0 lladdr 8c:5a:25:e4:56:b0 REACHABLE
192.168.1.111 dev enp2s0 FAILED
192.168.1.239 dev enp2s0 lladdr 00:00:c0:33:7b:6f STALE
192.168.1.112 dev enp2s0 FAILED
fe80::6038:e0ff:fec2:54a8 dev enp2s0 lladdr 62:38:e0:c2:54:a8 router STALE
2600:1702:4860:9dd0:210:75ff:fe28:5e30 dev enp2s0 lladdr 00:10:75:28:5e:30 STALE
fe80::8e5a:25ff:fee4:56b0 dev enp2s0 lladdr 8c:5a:25:e4:56:b0 router REACHABLE
fe80::210:75ff:fe28:5e30 dev enp2s0 lladdr 00:10:75:28:5e:30 STALE
from the target system
[rm3@RobertPC ~]# ssh alarm@2600:1702:4860:9dd0:210:75ff:fe28:5e30
alarm@2600:1702:4860:9dd0:210:75ff:fe28:5e30's password:
Last login: Wed May 12 15:59:14 2021 from fe80::c466:3bc6:17fa:9268%eth0
[alarm@alarm ~]$ ip route
default via 192.168.1.253 dev eth0 proto dhcp src 192.168.1.211 metric 1024
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.211
192.168.1.253 dev eth0 proto dhcp scope link src 192.168.1.211 metric 1024
[alarm@alarm ~]$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
link/ether 00:10:75:28:5e:30 brd ff:ff:ff:ff:ff:ff
[alarm@alarm ~]$ ip neigh
192.168.1.253 dev eth0 lladdr 62:38:e0:c2:54:a8 STALE
192.168.1.254 dev eth0 lladdr 8c:5a:25:e4:56:b0 STALE
fe80::8e5a:25ff:fee4:56b0 dev eth0 lladdr 8c:5a:25:e4:56:b0 router STALE
fe80::1eb5:75df:b84:98d1 dev eth0 lladdr 00:1d:60:35:b8:13 STALE
2600:1702:4860:9dd0:21d:60ff:fe35:b813 dev eth0 lladdr 00:1d:60:35:b8:13 DELAY
fe80::6038:e0ff:fec2:54a8 dev eth0 lladdr 62:38:e0:c2:54:a8 router STALE
--
Remind me to ignore comments which aren't germane to the thread.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
