On Tue, 2 Dec 2025, Marco Moock via NANOG wrote:
Now, if I want to assign static addresses for devices within my home
network, I don’t have a problem with v4 - everything’s RFC1918, so if
the public IP changes, NBD, and I can even do it with DHCP client
IDs. However, if my IPv6 PD changes and my home devices all have GUAs
assigned via SLAAC, then… guess what - every IPv6 device address in
my network just changed. Oops.
Practically, I’ve worked around this by manually assigning LUAs to
the devices that need static v6 addresses, like my SAN and the
machines that do NFS mounts from it. But 1. that’s more than
annoyingly clunky - hardly the improved experience that IPv6 promised
- and 2. weren’t we trying to get away from LUAs in the first place?
That is something your ISP is intentionally doing - unrelated to the
IPv6 specification.
There is no technical reason not to give a static net to a customer, it
doesn't cost more (although some ISP charge for that).
It's more work for the ISP (to make the static assignments, delete them
from DHCPv6 config when a customer terminates service, etc.). It's much
simpler to just define DHCP pools (and PD pools) and let the DHCP server
hand out IPs and subnets and keep track of the leases.
I'm curious though, do any broadband providers [of size] doing v6 assign a
static PD subnet to each customer? It's one thing to keep track of a
handful of statics. It's another to keep track of tens or hundreds of
thousands of them.
----------------------------------------------------------------------
Jon Lewis, MCP :) | I route
Blue Stream Fiber, Sr. Neteng | therefore you are
_________ http://www.lewis.org/~jlewis/pgp for PGP public key_________
_______________________________________________
NANOG mailing list
https://lists.nanog.org/archives/list/[email protected]/message/4KKELZMBL5YN24M3DTB4EQWP6UVR7FSH/
