I have two computers in a WiFi network:
Sometimes (once in ten) after rebooting B, I can not go from A to B:
$ ssh 192.168.201.128 ssh: connect to the host 192.168.201.128 port 22: no route to host
When I try to ping, I get:
$ ping 192.168.201.128 PING 192.168.201.128 (192.168.201.128) 56 (84) bytes of data. From 192.168.201.133 icmp_seq = 1 Destination Host Unreachable From 192.168.201.133 icmp_seq = 2 Destination Host Unreachable From 192.168.201.133 icmp_seq = 3 Destination Host Unreachable
ARP could be the problem:
$ arp HWtype Address HWaddress Flags Mask Iface gateway ether 70: 4c: a5: a7: c2: 57 C wlp2s0 192.168.201.128 (incomplete) wlp2s0
I was trying to fix it like this:
$ sudo arp -d 192.168.201.128 $ arping -c 10 -I wlp2s0 192.168.201.128 ARPING 192.168.201.128 from 192.168.201.133 wlp2s0 Sent 10 probes (10 broadcast (s)) Has 0 replies
no effect 🙁
I can not work around the problem by plugging the monitor and keyboard into B (server) and performing:
1) ping A (client)
2) typing "route" in the terminal
Then everything returns to normal.
An idea why this could happen?
My hypothesis is that B sometimes does not discover the gateway correctly. I am not able to check it because when I type "route" in the terminal B, everything returns to normal.
Notes from side:
- There is no firewall on B (server)
- One (client) is Ubuntu 18.04 Desktop
- B (server) is Ubuntu 16.04 minimal (maybe missing an important package for discovery arp / auto gw?)