![](https://seccdn.libravatar.org/avatar/9346938c7445407e30501c9e4cc1561a.jpg?s=120&d=mm&r=g)
On 4/4/19 8:50 AM, Per Jessen wrote:
Per Jessen wrote:
So, I pinged the router which somehow made it wake up and start sending RAs to 'nano1'. I still have a 'nano2' in this weird state - now I'm wondering what I might investigate on the router side?
Well, this is also interesting - on the main router:
# ip -6 neigh | egrep '2446|ba7a|39b0' fe80::12d0:7aff:fef6:39b0 dev eth0 lladdr 10:d0:7a:f6:39:b0 STALE fe80::96a1:a2ff:fea4:2446 dev eth0 FAILED fe80::96a1:a2ff:fea3:ba7a dev eth0 FAILED
It means neighborhood discovery failed. It tried probing the address and received no response. Is there some firewall running on the nanos? neighborhood discovery is happening over ICMPv6 so if that is blocked, it will cause problems..
I don't understand that FAILED state. From my desktop, I'm logged in to both nano1 and nano2 over ssh, for days. It works fine.
hmmm... I'm assuming you are not using link local address for this?
The only thing that set those two nanos apart is that they are connected over another wifi AP (we have three), a Netgear WG602v3. I don't understand why there should be an issue with link-local addresses.
There is no issue with link-local address as that's already on the IP layer. It could also be a link-layer issue, so that the wlan connection is down somehow and neighbourhood discovery fails? - Adam -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org