On 03/04/2019 23.56, Per Jessen wrote:
Carlos E. R. wrote:
On 03/04/2019 16.06, Per Jessen wrote:
Per Jessen wrote:
Looking at RAs being sent (my radvd doesn't use multicast), I don't see any RAs going out to the nanopis, whereas other machines are fine. Any reason why radvd would stop sending RAs to certain addresses??
Here is something interesting -
I looked up the neighbours:
# ip -6 neigh 2001:db8:7f7f:1::1000 dev wlan0 lladdr 00:08:02:58:7f:ac REACHABLE 2001:db8:7f7f:1:ff99::dde5 dev wlan0 lladdr 94:a1:a2:a4:24:46 STALE fe80::202:a5ff:fe3f:7f45 dev wlan0 lladdr 00:02:a5:3f:7f:45 STALE 2001:db8:7f7f:1:221:86ff:fe4f:8ac4 dev wlan0 lladdr 00:21:86:4f:8a:c4 REACHABLE 2001:db8:7f7f:1:ff99::d98d dev wlan0 lladdr 88:25:2c:d4:ec:f5 STALE fe80::1 dev wlan0 lladdr 00:0b:cd:3f:5f:d3 router STALE 2001:db8:7f7f:1:fc8a:1197:7ee0:9a0d dev wlan0 lladdr 00:01:6c:84:9b:86 STALE
The default gateway is supposed to be fe80::1, so I thougfht I would try pinging it:
nano1:~ # ping6 -I wlan0 fe80::1
Why fe80, is that not a hardware address?
No, that's just link-local.
Ok, but the numbers are tied to the hardware. To the MAC. It is not an address you define. And does not work on firefox, for instance.
So, I pinged the router which somehow made it wake up and start sending RAs to 'nano1'.
You pinged from the nano, or from other?
From the nano.
Ah, so the router found out the nano existed.
I still have a 'nano2' in this weird state - now I'm wondering what I might investigate on the router side?
Reboot it?
Investigate(!) - the router is obviously working fine. All our office and datacentre traffic passes thru it.
If rebooting the router cures the issue for now, that's another bit for the investigation :-) -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)