The current IP allocation/usage procedures are a bit beyond most people
ULA would let you maintain your internal lan with custom subnets and DNS even if you switch carriers or use multiple carriers. No need to update your internal DNS servers for ULA.
If you're running a server on your dynamic residential service, you must be using dyndns for ipv4. So do the same with ipv6.
Residential random prefixes is the nature of residential networks, as ISPs don't want to preserve state. With a business grade service, you'd get a static prefix, much like static ipv4. Then the only time you need to update anything is when you switch your ISP and need to update global DNS addresses for your servers.
[0] Ideally pure v6 if possible; I think there's some way to encapsulate/NAT v4 traffic out from a pure v6 network so I don't actually need dual stack.
Maybe I will write one this weekend and make a hn post.
As for the actual configuration you'll want something specific to your exact network device as learning any of it with a guide for how another device expects the configuration to be entered will be hair pulling.
Multiple carriers has no (consumer level) solution I've found myself happy with. It's anywhere from "hope all your devices handle multiple public prefixes quickly and without errors" to "NAT and deal with the pain you had from v4 again" to "Use some other way to relay or host your static services which need to be externally accessible" to "go back to dealing with trying to automatically update that DNS server entry on and making sure it always stays consistent"
And yeah, folks need to understand that ULA addresses are functionally equivalent to RFC 1918 addresses, and ask themselves why they'd expect an ISP who charges extra for an unchanging globally-routable IPv4 address to give you an unchanging globally-routable IPv6 prefix for free.
That's not the same for not changing an ipv6 address
Over the last several decades of me having residential Internet service from a variety of ISPs here in the US, I've never had an IPv4 address that was not globally-accessible. Relatedly, I've never had a guaranteed-static IPv4 address, but I COULD get one if I paid the ISP additional money.
I understand that in other regions of the world NOT being behind CGN is not guaranteed.
> That's not the same for not changing an ipv6 address
Hopefully you now understand the context in which I made my remarks. In the world that I (and many other folks) live in, I get one globally-accessible, but definitely-not-static IPv4 address.
If I use a global unicast prefix, the IPs I see on my devices are their real honest to goodness routable IP. That is great!
But I can’t use that IP in any configuration because it will change. That’s not so great.
So I have to compromise by not using the routable IP in places where I need to put the address in a config file.
Nobody wants ULA. ULA is a solution for the fact that your prefix will change, which I wish didn’t happen.
You can say it’s unreasonable to expect a stable prefix (and we could argue about that all day) but don’t pretend it wouldn’t be massively beneficial if I could rely on one. It is absolutely a compromise. A necessary one? Yes. A reasonably simple solution to implement? Yes. But it’s still a compromise.
> don’t pretend it wouldn’t be massively beneficial
It would be barely beneficial to me.
I don't want to memorize my global prefix anyway.
This is the proper ipv6 solution.
With ipv6, one ethernet interface is _supposed_ to have multiple addresses. You wouldn't want your lan routing to stop working when your ISP goes down, right? So configure your internal DNS with ULA (which should be stable for each machine for a given prefix, even with SLAAC) and be done with it, much like internal DNS using private addresses in ipv4.
For externally visible servers, do the normal thing, that is, those servers dynamically update global dns, much the same way with ipv4 dyndns.
Another learning curve for ipv6 is that people get frustrated by dynamic prefixes, but it's the nature of residential networks: the ISPs want a stateless solution, so customers get a dynamic prefix. Maintaining the same prefix across power outages needs a stateful solution, so only business plans offer them for an extra fee, much like static ipv4 addresses.
And we've had dyndns for decades now for exactly that use case. Just keep using that.
I'm surprised based on my experience: in 15 years of residential IPv6 usage I've always had the same IPv6 prefix (for a given ISP contract of course), even for those ISPs that insisted on handing out dynamic IPv4 with no option for a static one plus had no qualms renewing the IP at any moment, not just power down.
> stateful solution
I'm seeing this the other way around: dynamic needs lease tracking while static just needs a permanent record attached to the already present auth mechanism.
Out of curiosity, what residential ISPs were handing out IPv6 15 years ago?
- I think Free had it since forever and a half, although IIRC it was some weird 6rd or something. Freebox v6 (2011) for sure had it, v5 (2006) may had supported it from the start and for sure supported it down the road, I think v4 could have had it too through an update at least but honestly can't recall.
- Orange in France had a public opt-in experiment for native IPv6 over ADSL to which I enrolled at the time.
- Then I lost IPv6 because I moved to a cable operator which did not support DOCSIS 3.0 (a requirement for IPv6 on cable connections) at the time.
- After that FTTH rolled out and basically every ISP provided native IPv6 on it from the get go.
Non-biz IPv6 support in France is sitting in the ballpark of 99% these days, both residential and mobile. National regulations helped a lot. Residentially there has been a huge plan towards a national FTTH rollout, including in remote areas (the idea being that no one should be cast aside of a full speed internet); this plan also had specific requirements to enforce competition to prevent regional or local monopolistic situations such as the one that historically happened with cable operators (or like the ones I keep hearing about in the US). For mobile it was simpler: you want a radio license for 5G? you have to support IPv6, or else.
Is it that you'd still have the globally addressable addresses on NICs with a ULA too, just that's not what you'd use for routing internally? (Not that I'm really sure of the benefit of that residentially either?)
Whose power outage?
The ISP needs to reliably track allocations despite some of their equipment going out, except in the extreme edge case of their entire operation cold starting.
If the client modem goes out it can just be told the same number again when it boots.
And that's not even getting into how trivially small this amount of information is to save to disk.
Non-persistent allocation has technical benefits when your devices keep moving between nodes or when they're offline most of the time. Otherwise not so much.
If you want stable local addressing, announce a ULA on your LAN. Not all routers support it, unfortunately, but you can announce a ULA from any device. Just don't announce your raspberry Pi as an outbound router.
ULAs use SLAAC and will derive at least one IP address from your devices' MAC address. There's a chance of instability if you have devices with the same MAC addresses (there's detection for that problem but you end up with a race condition after a network reboot), but your network will probably break in other ways if you have such a setup.
I get an /56 by my ISP and have 6 or so different /64 in my residence.
A real world example my ISP provides /56 at the router level but if you put a firewall behind it, that gets a /64 (cannot be changed). Now the firewall cannot further delegate prefixes since it's already used. Some firewalls allow RA pass-through but in my case this wasn't an option so I had to set up NAT66 (non-standard :/) just to get outbound ipv6 connectivity.
What? SLAAC configures addresses on all -er- not-expired prefixes advertised on the link. So, if the border router advertises a ULA prefix and a globally-routeable prefix, SLAAC assigns two addresses to the computer.
If whatever network-configuration tooling you're using causes your computer to not generate an address for every advertised prefix (and you've not told the tooling to behave in this way) then it's broken.
That's a configuration problem on your end. Your border router needs to notice that it's being instructed to switch delegated prefixes and instruct radvd (or whatever route advertising daemon it's using) to advertise the now-defunct prefixes with a zero lifetime just before or just as you're advertising the new prefixes.
With this information, devices on your LAN that aren't asleep will do the right thing, and devices that were asleep should reconfigure their network interfaces when they wake up... assuming that the world hasn't changed while they've been asleep is something only morons would do (coughAppleComputerscough).
I’ll let you guess what daemon is deprecated, and what daemon is the new one you’re supposed to use in OpenBSD.
Oh, that's sad. I take it you've tried signalling rad to reload its configuration when a prefix on interfaces it advertises changes? IIRC, that's how you instruct radvd to do the thing.
Anyway, if that doesn't do what you need, then I don't see how you using bad software makes this any less a configuration problem on your end.
My intention here was to say that the fact that the 'rad' software fails to advertise prefixes with a zero lifetime is sad. That's like basic, essential functionality and it's always sad when software fails to implement basic, essential functionality.
My intention was NOT to assert that your configuration (or -worse- you, yourself) was sad or whatever.
> ...now you’re saying I’m using “bad software” for using the built-in, recommended router advertisement daemon...
Yes? It's possible for the recommended thing to be bad software. If you haven't discovered this, you DEFINITELY will as time goes on.
The answer to this is usually something like “duh, use DNS”, but how are you going to configure that DNS server if your whole network’s IP address range could change at any time? Yes, multicast DNS is a thing, but it’s not supported in all software (I’m looking at you, OpenBSD, which has no out of the box support for it and I’ve not figured out how to configure it.)
So the real answer is to create a ULA prefix on the side that you generate randomly (or make an easy to remember one because this is residential use, who cares about collisions, it’s a private space) and use that for any use case that involves hardcoded IPs, like DNS server configuration.
But it still feels like a compromise to me. I wish more software was “prefixless”, including DNS server indication and even DNS zone files, such that a lack of prefix means “prepend the prefix you are already communicating on”… Firewall configuration would be simpler, DNS zone files could survive re-prefixing, all sorts of configuration could be made to work this way, but instead you’re left with either a ton of automation to reconfigure things when the prefix changes, a bunch of manual work, or just bite the bullet and use ULA.
Oh, and did I mention that in my particular setup, all my devices would keep trying to communicate on their old addresses even after a new prefix gets assigned and the new RA’s are sent? Meaning they essentially lose all connectivity if you’re using an IPv6-mostly setup like I have? Oh sure, they grab addresses on the new prefix, but they don’t drop the old one until the lifetime expires, which defaults to 4 hours in the environment I’m in (I think the rad daemon in OpenBSD inherits the lifetimes from its upstream router’s lifetimes, which makes the duration Comcast’s fault, but the proper thing to do is rescind the old RA’s when the interface changes addresses, and rad does not do this out of the box for me, or if it does it doesn’t work right.)
Ok rant over. I want to like IPv6 but dynamic prefixes are really the Achilles heel for me.