But unstable prefixes are not a fundamental problem with IPv6, more of a teething problem where some ISPs may take some time to get clued in.
Meanwhile it never hurts to automate your handling of renumbering, it'll happen eventually anyway - just like letsencrypt short expiration times actually help you avoid cert expiration problems.
> If your ISP assigns you dynamic prefixes (mine does), you can end up with devices not being able to connect to the internet after the router/modem reboots, since they're not told about the new prefix you just got from your ISP and happily keeps using the old one.
You have a broken router setup, it's not doing router advertisement. Every reply of yours in this thread is just you complaining about something that you misconfigured on your router or did not bother reading about in any decent IPv6 introduction. Please stop the FUD.
> If your ISP assigns you dynamic prefixes (mine does)
Well there goes your problem…
Re:IP addresses and routing
by magicalhippo on Thursday July 26, 2018 @06:50AM
(#17616432)
Yes it's not what is currently (19 years after IPv6 RFC) considered best practices[1], but that's what my ISP hands me, so that's what I got to work with.
Either they really don't understand IPv6 or they are creating a false scarecity to charge you more money for what is essentially a free and virtually infinite resource to them, probably both.
Or they're running 6rd and giving him a dynamic ipv4?
Re:IP addresses and routing
by magicalhippo on Thursday July 26, 2018 @12:03PM
(#17618496)
Not sure what they're running. They do hand me a dynamic IPv4 address, but unless the modem is offline for more than an hour or so, I get the same address.
For whatever reason I get a new IPv6 prefix every time the modem or router reboots.
For one, address allocation is entirely different. Devices will have several addresses, and some of them can be temporary addresses.
If your ISP assigns you dynamic prefixes (mine does), you can end up with devices not being able to connect to the internet after the router/modem reboots, since they're not told about the new prefix you just got from your ISP and happily keeps using the old one.
If your ISP assigns you dynamic prefixes (mine does), dynamic DNS is required for each server box (apparently one can centralize this by using DHCP-PD, but I haven't figured this out for my pfSense router).
And if you're writing an IPv6-enabled application, parsing client/server address input is a PITA compared to IPv4.
The list goes on and on, but these were the major pain points I found while trying to use IPv6 at home, which are non-existent when using IPv4.