3 ms·

ipv6 is very, very widely deployed in mobile networks. Download some net tools and check out your phone's interface table. Also v6 did a bunch of things right

ipv6 is very, very widely deployed in mobile networks. Download some net tools and check out your phone's interface table. Also v6 did a bunch of things right. NDP and link local addresses for v6 actually work. The fragmentation changes were 100% the right thing to do. v6 extensions like SR and uSID are both solid and consolidate a lot of stupid stuff into something clean. v6 had a bad, rocky start. A lot of that was completely inadequate attention to the transition, and the vendors fucked up almost everything for years, on their own gear and interop, but at this point v6 is fine. Would I launch a v6 only service? No, because at this point the SPs are the problem. Verizon as of a few years ago and maybe now still didn't do v6 to any of their home users. So many things like that.

lxgr 3y ago
> Verizon as of a few years ago and maybe now still didn't do v6 to any of their home users. So many things like that. My FIOS home connection has had IPv6 since some time last year. Consumer ISPs are actually quite motivated to offer IPv6 since it gives them a path forward without an IPv4 address per customer better than CG-NAT. Many consumers also just use their ISP's CPE, which makes this shift easier as well. I think the bigger obstacle will be managed corporate connections (for Wi-Fi or other client access connectivity) that are only upgraded once every few years and just don't support IPv6.
unethical_ban 3y ago
I finally got IPv6 working on my home network this week. /60 prefix from the ISP, Slaac with PD for addresses, RA for DNS, unbound DNS working just fine. OPNsense works great! This is something I've wanted to get working for years.
hot_gril 3y ago
Ipv6 isn't just an upgraded protocol over ipv4. It could've been, but it's not. It's a totally separate network with its own routing. So just changing all hardware along the way to support ipv6 doesn't mean it's adopted.
- doublepg23 3y ago
  IPv6 isn’t just an upgraded protocol because the designers knew they didn’t want to go through the painful process again and wanted to get it right.

lxgr 3y ago

> Verizon as of a few years ago and maybe now still didn't do v6 to any of their home users. So many things like that. My FIOS home connection has had IPv6 since some time last year. Consumer ISPs are actually quite motivated to offer IPv6 since it gives them a path forward without an IPv4 address per customer better than CG-NAT. Many consumers also just use their ISP's CPE, which makes this shift easier as well. I think the bigger obstacle will be managed corporate connections (for Wi-Fi or other client access connectivity) that are only upgraded once every few years and just don't support IPv6.

unethical_ban 3y ago

I finally got IPv6 working on my home network this week. /60 prefix from the ISP, Slaac with PD for addresses, RA for DNS, unbound DNS working just fine. OPNsense works great! This is something I've wanted to get working for years.

hot_gril 3y ago

Ipv6 isn't just an upgraded protocol over ipv4. It could've been, but it's not. It's a totally separate network with its own routing. So just changing all hardware along the way to support ipv6 doesn't mean it's adopted.

doublepg23 3y ago
IPv6 isn’t just an upgraded protocol because the designers knew they didn’t want to go through the painful process again and wanted to get it right.