Remix.run Logo
▲ RVuRnvbM2e 3 hours ago

Isn't it a misconfiguration that the ISP is handing out a different prefix each time pppd restarts? Shouldn't the prefix be fairly static?

▲rnhmjoj 2 hours ago | parent | next [-]

It's likely not a misconfiguration, but it's a bad practice [1] to implement dynamic IPv6 prefixes like they were IPv4 addresses from a pool. I see no reason to do it like this other than "that's what we have always done with IPv4".

Non-sticky, dynamic prefixes cause all sort of mayhem because suddenly your RAs, firewall rules, DNS recods, NAT64 pools etc. are all outdated and you have to somehow update them, leaving the network in a broken state until the changes have propagated.

[1]: https://www.ripe.net/publications/docs/ripe-690/

▲throw0101c 2 hours ago | parent | next [-]

> It's likely not a misconfiguration, but it's a bad practice [1] to implement dynamic IPv6 prefixes like they were IPv4 addresses from a pool.

I don't necessarily disagree with the assessment, but to a certain extent I like getting new addresses/prefixes to help with privacy: with my previous ISP I had my own Asus router (now have to use ISP-provided), and it had built-in functionality to schedule reboots.

* https://www.asus.com/support/faq/1049258/

I would get a new IPv4 address and IPv6 prefix each day.

Yes, there are (e.g.) browser-based mechanisms for tracking, but if I open sites in (say) a private window I would avoid some of those; there are also add-ons/extensions that allow for (auto-)expiring cookies.

▲thedougd an hour ago | parent [-]

This seems like a good use for DUID with the DHCPv6 request. The ISP would return the same prefix for the same DUID, but if you wanted a rotation, rotate your DUID.

▲pepperoni_pizza 2 hours ago | parent | prev | next [-]

They probably do it so you have to pay for a static one.

▲kccqzy 2 hours ago | parent | prev | next [-]

Yeah it’s annoying enough that I had to set up my DNS server on a ULA network, so I can hardcode it in my RA without thinking about ISP prefixes. As for NAT64, I just stuck to the well-known 64:ff9b instead of using my own prefixes. It also simplifies DNS64.

▲izacus 2 hours ago | parent | prev [-]

I hear that this is a common practice nowadays across worlds' ISPs though :/

▲lmz 2 hours ago | parent [-]

Wouldn't want the users to be too attached to the prefix if they're not paying for a business plan.

▲throw0101c an hour ago | parent [-]

> Wouldn't want the users to be too attached to the prefix if they're not paying for a business plan.

Residential assignments are often /56 (2^8 subnets) or even maybe /60 (2^4 subnets): this may or may not be enough for business needs, depending on the size of the organization.

▲lmz an hour ago | parent [-]

Yes, but switching the prefixes regularly keeps them from easily putting the addresses in DNS, facilitating an upsell to the business plan.

▲BadBadJellyBean 3 hours ago | parent | prev [-]

No. Not necessarily.

▲RVuRnvbM2e 2 hours ago | parent [-]

Yes it is. The exact scenario from the article is a well known problem with dynamic prefixes: https://www.ietf.org/archive/id/draft-palet-v6ops-prefix-ass...

▲ebiederm 11 minutes ago | parent | next [-]

Agreed.

That draft BCP doesn't put it as well as the RFC's unfortunately.

In short renumbering as little as possible is the current best practice because IPv6 renumbering is not as robust as it can be.

Flash renumbering (AKA renumbering without warning) has been documented as a problem.

The practical problem is the default lifetimes for prefixes are in days or weeks, and without something to notice and report the prefix is gone hosts continue to use it.

A number of RFCs are working their way through the system to get the handling of renumbering and especially flash renumbering as robust as possible.

Even when it is documented the best way to handle the sitation and the RFCs are published. It will take a little bit for all of the software to be updated.

All of that said renumbering somewhat regularly (monthly?) on IPv6 remains important so that bugs don't creep into the process unnecessarily.

▲throw0101c 2 hours ago | parent | prev | next [-]

> https://www.ietf.org/archive/id/draft-palet-v6ops-prefix-ass...

PSA: You may wish to point to the most recent revision (or use a link that lists all revisions, and would point to the perhaps-eventual RFC):

* https://datatracker.ietf.org/doc/draft-ietf-v6ops-prefix-to-...

▲RVuRnvbM2e 2 hours ago | parent [-]

Right, thanks. It was difficult finding a vaguely recalled RFC draft on my phone :D

▲Joker_vD an hour ago | parent | prev [-]

It boggles my mind that they would deliberately design Internet (!) Protocol that poorly handles the dynamic nature of the networks its supposed to interconnect. The prefixes are dynamic, that's the fact of life.

But then again, at least half of the IPv6 design looks as a deliberate and somewhat spiteful attempt to force the ISPs and ASs to do things in a radically different ways than they are doing already just fine.

▲throw0101c an hour ago | parent [-]

> It boggles my mind that they would deliberately design Internet (!) Protocol that poorly handles the dynamic nature of the networks its supposed to interconnect. The prefixes are dynamic, that's the fact of life.

The 'dynamic' nature of these delegations is a policy decision of the ISP and not of the protocol: nothing is stopping them from giving the same prefix to the same customer.

It's no different than a DHCP(v4) server on a corporate network remembering which MAC got which IPv4 address in the past and giving the same one over the course of time, or the IT folks telling the DHCP system to not remember and give a new address each time.