| ▲ | IPv6 delegation, an unusually subtle failure mode(savyasacheejha.com) |
| 46 points by genghizkhan 3 days ago | 30 comments |
| |
|
| ▲ | miyuru 30 minutes ago | parent | next [-] |
| One my LTE router's had a similar issue, which i documented for anyone(or AI agents) stumbling on it here. https://blog.miyuru.lk/zlt-ipv6-fixes/ |
|
| ▲ | arcfour 2 hours ago | parent | prev | next [-] |
| Why do you even need networkd for a router? Setting one up on Alpine (so not all this cruft) is easy as pie and the whole thing can cold boot in under 10 seconds... Would make the whole setup much more understandable + smaller attack surface... > I usually prefer using systemd utilities wherever possible. Ah. There's your problem. When something promises it can do anything and everything, rarely can it do much of it well, I find... The type of issue you encountered is a pervasive failure mode you will encounter the more and more systemd utilities you rely on. For something like a router, systemd is wholly unnecessary. Try it! You'll agree. |
| |
| ▲ | o_-_o 2 hours ago | parent | next [-] | | Yeah this is why I have that Arch Linux uses systemd* by default. Will try Artix Linux[1]. "Artix Linux is a rolling-release distribution, based on Arch Linux. It uses real init systems, because PID1 must be simple, secure and stable." [1] https://artixlinux.org/
[*] https://systemd-free.artixlinux.org/ | |
| ▲ | hylaride 30 minutes ago | parent | prev [-] | | Networking is the biggest cause of issues I've had with systemd, mostly because of the systemd maintainer's insistence on strict adherence to modern RFC's to the detriment of legacy support. This has resulted in my having to deal with gross workarounds for various issues, including this 032 issue with multiple domains: https://docs.aws.amazon.com/linux/al2023/ug/deprecated-al2.h... | | |
| ▲ | lmz 5 minutes ago | parent [-] | | That multiple domain issue doesn't seem to stem from "modern RFCs", just a decision to not be bug compatible with the previous implementation. > Windows and other Linux operating systems treat the value as a single domain, which results in unexpected behavior. The parent poster's suggestion to use Alpine is amusing in the context of your problem because musl libc is notorious for sticking to the spec when compared to glibc. |
|
|
|
| ▲ | RVuRnvbM2e 2 hours ago | parent | prev | next [-] |
| 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 an hour 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 29 minutes 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 an hour 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 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. | | |
| ▲ | 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 2 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... | | |
| ▲ | throw0101c an hour ago | parent | 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 an hour 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. |
|
|
|
|
|
| ▲ | wowczarek an hour ago | parent | prev | next [-] |
| I thought PD in Linux and *BSDs was a solved issue. I think I've been spoilt by dedicated NOSes. |
| |
| ▲ | thedougd 30 minutes ago | parent [-] | | This is a narrow issue related to PD when a PPP connection is used. I can attest that PD works well for me with systemd-networkd. |
|
|
| ▲ | o_-_o 2 hours ago | parent | prev | next [-] |
| I think the most disturbing part of this article is; "I haven't replaced the dead CMOS battery on my router and the clock resets every time the router restarts." O_o |
| |
| ▲ | tosti 2 hours ago | parent [-] | | That would be bad for a server, not so much for a router. | | |
| ▲ | tosapple 2 hours ago | parent [-] | | and if it has a deterministic rng, it will restart/initialize at seed[0] every time? | | |
|
|
|
| ▲ | jon128 an hour ago | parent | prev [-] |
| Part of how some of my devices cope with ISPs doing things the wrong way is to ping IP addresses belonging to nearby AS and some remote AS from the source addresses of each local IP prefix. When a local IP prefix is detected as stale relative to other local IP prefixes, my local router(s) sound out appropriate router announcements to squash the stale prefixes. Devices I travel with do the same. It seems these days, most eyeball networks aren't too technical, rely on whatever closed source software vendors poop out, and for the most part they are just plugging things in. That, and billing. |