#17510: /60 rather than /64 IPv6 'interface' route created on LAN interface
-----------------------------+-----------------------------------
Reporter: markzzzsmith@… | Owner: developers
Type: defect | Status: reopened
Priority: normal | Milestone:
Component: base system | Version: Barrier Breaker 14.07
Resolution: | Keywords:
-----------------------------+-----------------------------------
Comment (by cyrus):
No the problems are actually a bit more tricky. I actually filed a bug
against the kernel here which describes and fixes the issue
http://patchwork.ozlabs.org/patch/320782/ but was rejected.
The core source of the trouble is that we handle RAs entirely in userspace
to make our uplink routes source-restricted, so that we can do multihoming
with IPv6 correctly (avoiding traffic going out an uplink with a source
from another uplink's delegated prefix). Thus we need to deal with quirky
and inconsistent netlink behavior as described above.
The reason for the /60 hack is that in order for the DHCPv6-server to be
aware of changes of addresses and available prefixes for RA, IA_NA and
IA_PD (so we can trigger sending RAs or send DHCPv6-Reconfigure etc.) we
need a communication channel and I just let the server watch kernel
netlink events here. Anyway I will change the on-link routes to /64 then
your concerns are addressed and the DHCPv6 server is still happy.
--
Ticket URL: <https://dev.openwrt.org/ticket/17510#comment:7>
OpenWrt <http://openwrt.org>
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-tickets
