Wireless can't ping wireless (even more info)

[Jim Lewis]

> On 01/25/15 12:46, Ed Greshko wrote:
>> When in this condition, what is the output of "arp" on big4?
>
> I meant "arp -n"
>

 Great idea Ed! It's been years since I worked on Ethernet drivers for IBM
and forgot all about that command. Checking man it shows arp to be
obsolete so I used ip:

big4 /temp # ip -s neigh
fe80::9afc:11ff:fe83:6dfe dev eth0 lladdr 98:fc:11:83:6d:fe router ref 1
used 1364540/1364600/1 STALE
192.168.1.111 dev eth0  ref 1 used 140/200/137 FAILED
192.168.1.1 dev eth0 lladdr 98:fc:11:83:6d:fe ref 31 used 71/11/44 REACHABLE

  As you can see laptop1 at 192.168.1.111 cannot be pinged by big4. Now I
will ping big4 from laptop1:
laptop1 ~ # ping -c 1 192.168.1.109
PING 192.168.1.109 (192.168.1.109) 56(84) bytes of data.
64 bytes from 192.168.1.109: icmp_seq=1 ttl=64 time=0.666 ms

--- 192.168.1.109 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.666/0.666/0.666/0.000 ms

 Now running the ip command again from big4:

big4 /temp # ip -s neigh
fe80::9afc:11ff:fe83:6dfe dev eth0 lladdr 98:fc:11:83:6d:fe router ref 1
used 1364856/1364916/1 STALE
192.168.1.111 dev eth0 lladdr 00:23:4e:df:d1:5d ref 3 used 47/47/32 STALE
192.168.1.1 dev eth0 lladdr 98:fc:11:83:6d:fe ref 25 used 23/11/1 REACHABLE

  Of course the ping/ssh work now as well. Will look at new routers tomorrow.


Jim Lewis