I have two 'router' type devices setup on my network.
One is my actual IPv6 router - a Cisco 2621 (
fe80::xxxx:3e60). It's the correct default router.
Another is a DLINK DIR-615 (
fe80::xxxx:5760). It's IPv6 aware but at the moment is only configured for link-local addressing as it's only being used as a WAP.
Both devices are sending out ICMPv6 RA messages and as a result both are being added to my clients' routing table:
$ ip -f inet6 route | grep default default via fe80::xxxx:3e60 dev wlan0 proto kernel metric 1024 expires 1741sec mtu 1500 advmss 1440 hoplimit 64 default via fe80::xxxx:5760 dev wlan0 proto kernel metric 1024 expires 1791sec mtu 1500 advmss 1440 hoplimit 64
The trouble arises from the fact is that my clients now have a choice of default routers. One sends packets merrily on their way, the other doesn't. I can remove the incorrect route but it just gets re-added when the next RA comes along.
fe80::xxxx:3e60 (the correct router) is sending out RAs advertising a prefix of 2001:xxxx:xxxx::/64 (my network)
fe80::xxxx:5760 (the incorrect router) is sending out RAs advertising a prefix of fe80::/64 (link-local)
So… who's at fault here?
fe80::xxxx:5760for sending out RAs when it can't provide a valid prefix?
fe80::xxxx:5760for sending out RAs with the link-local prefix?
- my clients for adding
fe80::xxxx:5760to the route table when it's advertising the link-local prefix?
- Something else?