Hi,
following scenario:
Gateway (running radvd) [00:50:BF:06:B4:F5] and a client with one interface
(forwarding disabled) [00:e0:18:90:92:05].
Client boots, neigborhood detection works and take the given prefix from
radvd to assign a global address for the one and only interface.
14:00:54.475785 :: > ff02::1:ff90:9205: icmp6: neighbor sol: who has
fe80::2e0:18ff:fe90:9205
14:00:58.476075 fe80::2e0:18ff:fe90:9205 > ff02::2: icmp6: router solicitation
14:00:58.502708 fe80::250:bfff:fe06:b4f5 > ff02::1: icmp6: router advertisement
14:00:58.996090 :: > ff02::1:ff90:9205: icmp6: neighbor sol: who has
3ffe:400:100:f101:2e0:18ff:fe90:9205
Ok, 3ffe:400:100:f101:2e0:18ff:fe90:9205 was added on client interface,
routing entries are also added.
But if I switch down and up the network (completly or only interface), the
mechanism won't work:
14:01:22.037731 :: > ff02::1:ff90:9205: icmp6: neighbor sol: who has
fe80::2e0:18ff:fe90:9205
14:01:26.038013 fe80::2e0:18ff:fe90:9205 > ff02::2: icmp6: router solicitation
14:01:26.142629 fe80::250:bfff:fe06:b4f5 > ff02::1: icmp6: router advertisement
the final "neighbor sol" is missing, neither address nor routing is well
configured for global usage.
Looks like the client do not accept the advertisement. But "accept_ra" is
unchanged, also forwarding on client side - still disabled.
Is there a hidden switch somewhere or something else like a retrigger?
Happens with 2.2.17 and 2.4.0.
Can someone reproduce this? Any hints?
TIA,
Peter
|