Adam Majer wrote:
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.
Right. I also see the state go INCOMPLETE, then back to FAILED every now and then.
Is there some firewall running on the nanos? neighborhood discovery is happening over ICMPv6 so if that is blocked, it will cause problems..
There's no firewall on either, and neighbour sol/adv works fine: 13:12:17.255717 IP6 fe80::96a1:a2ff:fea3:ba7a > 2001:db8:4c68:1::1000: ICMP6, neighbor solicitation, who has 2a03:7520:4c68:1::1000, length 32 13:12:17.265141 IP6 2001:db8:4c68:1::1000 > fe80::96a1:a2ff:fea3:ba7a: ICMP6, neighbor advertisement, tgt is 2a03:7520:4c68:1::1000, length 24 13:12:22.375707 IP6 fe80::96a1:a2ff:fea3:ba7a > 2001:db8:4c68:1:221:86ff:fe4f:8ac4: ICMP6, neighbor solicitation, who has 2a03:7520:4c68:1:221:86ff:fe4f:8ac4, length 32 13:12:22.379097 IP6 2001:db8:4c68:1:221:86ff:fe4f:8ac4 > fe80::96a1:a2ff:fea3:ba7a: ICMP6, neighbor advertisement, tgt is 2a03:7520:4c68:1:221:86ff:fe4f:8ac4, length 24 (roughly every 50sec). First solicitation is for the nameserver at 1::1000, the second one is my desktop. Both nanos show the same traffic.
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?
Right, both nanos have dynamic addresses from a pool.
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?
It is a slightly poor wifi connection, but easily good enough for an ssh session. Both nanos also have a thttpd running, serving graphs for a website. (which does not work without the default route). nano1:~ # iwconfig wlan0 wlan0 IEEE 802.11 ESSID:"ENIDAN" Mode:Managed Frequency:2.462 GHz Access Point: 00:14:6C:E0:71:FB Bit Rate=54 Mb/s Tx-Power=31 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on Link Quality=55/70 Signal level=-55 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:1 Invalid misc:0 Missed beacon:0 nano2:~ # iwconfig wlan0 wlan0 IEEE 802.11 ESSID:"ENIDAN" Mode:Managed Frequency:2.462 GHz Access Point: 00:14:6C:E0:71:FB Bit Rate=54 Mb/s Tx-Power=31 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on Link Quality=53/70 Signal level=-57 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 -- Per Jessen, Zürich (2.4°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org