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.

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

And if you want static ips either use dhcp6 or disable the randomisation of eui64 addresses

[–] jlh@lemmy.jlh.name 2 points 5 months ago (1 children)

I have static IPs for my Kubernetes nodes, and I actually use DHCPv6 for dynamic dns so I can reach any device with a hostname, even though most of my devices don't have static IPs.

The issue is those static IPs are tied to my current ISP, preventing me from changing ISPs without deleting my entire Kubernetes cluster.

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

It certainly looks like you can give it a prefix to assign out, possibly even multiples

load more comments (14 replies)