News for hackers. Stuff that matters.
Re:IPv6 delegation, an unusually subtle failure mode by rnhmjoj on Wednesday November 18, 2026 @08:48AM (#50546286)
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.

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

Re:IPv6 delegation, an unusually subtle failure mode by izacus on Wednesday November 18, 2026 @08:52AM (#50546319)
I hear that this is a common practice nowadays across worlds' ISPs though :/
Re:IPv6 delegation, an unusually subtle failure mode by lmz on Wednesday November 18, 2026 @09:34AM (#50546794)
Wouldn't want the users to be too attached to the prefix if they're not paying for a business plan.
Re:IPv6 delegation, an unusually subtle failure mode by throw0101c on Wednesday November 18, 2026 @09:47AM (#50546966)
> 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.

Re:IPv6 delegation, an unusually subtle failure mode by lmz on Wednesday November 18, 2026 @09:58AM (#50547088)
Yes, but switching the prefixes regularly keeps them from easily putting the addresses in DNS, facilitating an upsell to the business plan.
Re:IPv6 delegation, an unusually subtle failure mode by kccqzy on Wednesday November 18, 2026 @09:01AM (#50546435)
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.
Re:IPv6 delegation, an unusually subtle failure mode by wernam on Wednesday November 18, 2026 @11:14AM (#50548091)
NAT64 is for ipv4. How does relate to ipv6 routing?? Also, ULA is non routable and has lower precedence (3) than ipv4 (35), so ipv6 will never be used in your case
Re:IPv6 delegation, an unusually subtle failure mode by eqvinox on Wednesday November 18, 2026 @12:19PM (#50549081)
> ULA is non routable

ULA is absolutely routable. Are you confusing it with LLA?

> and has lower precedence (3) than ipv4 (35)

This already got changed in https://datatracker.ietf.org/doc/html/draft-ietf-6man-rfc672..., the document is fully done with the RFC editor queue and only waiting for the [SNACBIT] reference to get published.

New preference table:

  Prefix        Precedence Label
  ::1/128               50     0
  $known_local/4x       45    14 (**)
  ::/0                  40     1
  fc00::/7              30    13 (*)
  ::ffff:0:0/96         20     4 (*)
  2002::/16              5     2 (*)
  2001::/32              5     5
  ::/96                  1     3
  fec0::/10              1    11
  3ffe::/16              1    12
Re:IPv6 delegation, an unusually subtle failure mode by wernam on Wednesday November 18, 2026 @01:41PM (#50550301)
ULA is routable, not internet routable, I stand corrected.

Yes many keep track of that RFC. However you're aware that every client device, tv, phone, esp32, iot device, has to apply this change? That will take decades

Re:IPv6 delegation, an unusually subtle failure mode by kccqzy on Wednesday November 18, 2026 @01:54PM (#50550478)
[delayed]
Re:IPv6 delegation, an unusually subtle failure mode by wernam on Wednesday November 18, 2026 @02:05PM (#50550603)
If you're using GUA then how are you handling the rotating prefix by the ISP, the problem mentioned in article? You don't have a fixed GUA. Most residential networks have this exact same problem as in the article.
Re:IPv6 delegation, an unusually subtle failure mode by kccqzy on Wednesday November 18, 2026 @02:10PM (#50550661)
Simple. The same way the original article solves it: using odhcpd from OpenWrt.
Re:IPv6 delegation, an unusually subtle failure mode by kccqzy on Wednesday November 18, 2026 @01:19PM (#50549963)
[delayed]
Re:IPv6 delegation, an unusually subtle failure mode by throw0101c on Wednesday November 18, 2026 @09:34AM (#50546784)
> 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/

Re:IPv6 delegation, an unusually subtle failure mode by thedougd on Wednesday November 18, 2026 @10:20AM (#50547379)
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.
Re:IPv6 delegation, an unusually subtle failure mode by pepperoni_pizza on Wednesday November 18, 2026 @09:38AM (#50546849)
They probably do it so you have to pay for a static one.
Re:IPv6 delegation, an unusually subtle failure mode by crote on Wednesday November 18, 2026 @02:50PM (#50551194)
I can easily see quasi-persistent prefixes being a giant support nightmare, because people will assume it is persistent, hardcode it everywhere, and then get upset when it suddenly changes after a year or two due to a big ISP network reconfig. Intentionally rotating it more often than strictly needed prevents this kind of ossification, because any user has to account for renumbering from the very start.

To me it seems the main issue is that the old prefix immediately stops being valid. There's not exactly a shortage of IPv6 addresses, so the ISP shouldn't be in any hurry to reuse the old prefix. If they were to still route it to the customer for, say, 24 hours, then it would give equipment time to switch over to the new one.