this post was submitted on 16 Aug 2025
19 points (100.0% liked)
networking
3219 readers
10 users here now
Community for discussing enterprise networks and the ensuing chaos that comes after inheriting or building one.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Certain equipment need to support IPv6 in certain ways, but not necessarily be assigned a v6 address. Anything OSI layer-2 or layer-1 will not need to "explicitly" support v6, with exceptions. The network terminal (ONT/modem) usually needs to support v6, as they will generally have security features to prevent a subscriber from using random addresses they were not assigned, or using multiple.
At a minimum, core/edge routing supporting v6, premise equipment supporting v6, at least one upstream provider or transit provider that supports v6 in combination with diverse peering with v6, and ancillary servers to provide DHCPv6 and DNS6. Generally I would assume a provider adding v6 is going to do dual stack, which is great for usually not being NATed on at least one IP stack.
What's nice about v6 being so old.. is that a lot of the equipment they are using will support v6. Most consumer routers just need to get a dhcp reply with v6 with default settings.
We are deploying v6 to both brand new fiber customers and very legacy dsl customers without widespread equipment replacement now, at a US based ISP, but I don't work at Bell or have any idea of what other hurdles they may have that we don't.
Thanks!