Re: Network entanglement
On 5/14/21 8:38 AM, Ed Greshko wrote:
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
Tried the correct address as soon as my mind quit pl aying tricks on me
then caught on that the second ipv6 address wanted the tag of the local
device attached
ip -4 add show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
group default qlen 1000
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel
state UP group default qlen 1000
inet 192.168.1.185/24 brd 192.168.1.255 scope global dynamic
noprefixroute enp2s0
valid_lft 56762sec preferred_lft 56762sec
traceroute -n 192.168.1.211
traceroute to 192.168.1.211 (192.168.1.211), 30 hops max, 60 byte packets
1 192.168.1.211 0.292 ms 0.204 ms 0.167 ms
traceroute -n 2600:1702:4860:9dd0:210:75ff:fe28:5e30
traceroute to 2600:1702:4860:9dd0:210:75ff:fe28:5e30
(2600:1702:4860:9dd0:210:75ff:fe28:5e30), 30 hops max, 80 byte packets
1 2600:1702:4860:9dd0:210:75ff:fe28:5e30 0.938 ms 0.837 ms 0.795 ms
traceroute -n fe80::210:75ff:fe28:5e30%enp2s0
traceroute to fe80::210:75ff:fe28:5e30%enp2s0
(fe80::210:75ff:fe28:5e30%enp2s0), 30 hops max, 80 byte packets
1 fe80::210:75ff:fe28:5e30%enp2s0 0.300 ms 0.176 ms 0.276 ms