It should only be needed if your ISP is brain-dead and only gives you a /64 instead of what they should be doing and also giving you a /56 or /48 with prefix delegation (I.e it should be getting both a 64 for the wan interface, and a delegation for routing)

You router should be using that prefix and sticking just a /64 on the lan interface which it advertises appropriately (and you can route the others as you please)

Internal ipv6 should be using site-local ipv6, and if they have internet access they would have both addresses.

[–] dan@upvote.au 1 points 5 months ago* (last edited 5 months ago) (5 children)

My ISP does this right (provides a /56 for routing), but unfortunately both are dynamic and change periodically. Every time I disconnect and reconnect from the internet, I get a different prefix.

I ended up needing to have ULAs for devices where I need to know the IPv6 address on my network (e.g. my internal DNS servers).

[–] Thiakil@aussie.zone 1 points 5 months ago (4 children)

Indeed, that's correct ula usage, but shouldn't need nat rewriting. The global prefixes just need to be advertised by RA packets

[–] Thiakil@aussie.zone 1 points 5 months ago (1 children)

I use openwrt on my home network which uses dnsmasq for dhcp. It can give a static suffix which just works with the global prefix on the interface and the site local / ula prefix it uses

[–] dan@upvote.au 1 points 5 months ago (1 children)

Note that Android doesn't support DHCPv6, just in case you have Android devices and ever have to debug IPv6 on them.

[–] Thiakil@aussie.zone 1 points 5 months ago

Yup indeed. That's why it advertises both dhcp and slaac

load more comments (2 replies)

load more comments (13 replies)