Revision as of 11:38, 1 March 2024 (view source) Adsb (talk \| contribs) m (Not really a better way) ← Older edit		Revision as of 11:50, 1 March 2024 (view source) Adsb (talk \| contribs) (Fixed!) Newer edit →
We need a way for the WAN to tell the LAN about the wider routing block, whilst letting the LAN only use for itself the first /64 block. This turns out to be remarkably easy. On the AAISP control panel, add a /60 block of IPv6 addresses. When DHCPv6 requests prefix delegation, AAISP returns the lowest number address block - if this is the new /60 then that's what you'll get, otherwise you might have to unroute some or more of the /64 blocks. ~~I'm investigating the options:~~ In my case I see for ''wan_6'': * Configure IPv6 on the WAN manually, not using DHCPv6 Protocol: Virtual dynamic interface (DHCPv6 client) Uptime: 0h 40m 58s IPv6: 2001:8b0:1111:1111:0:ffff:abcd:pqrs/128 IPv6-PD: 2001:8b0:xyz:4520::/60 And for ''lan'': * Configure automatically with DHCPv6, and then add the missing route(s) IPv6: 2001:8b0:9d7:4520:xxxx:xxxx:xxxx:xxxx/64 ~~# ip -f inet6 route add default via fe80::203:97ff:feba:900 dev pppoe-wan~~ It's the ''ip6assign'' option in the config for the lan which determines that the lan uses a /64. * See whether delegating a /60 is any better - does DHCPv6 PD reply with the /60 or just one /64 ? = Enabling IPv6 in the local network =

OpenWRT routers (view source)