3 ms·

You have some misconfiguration on your local network. It's hard to tell from your description, but I'd guess maybe you don't have the firewall rules configured

You have some misconfiguration on your local network. It's hard to tell from your description, but I'd guess maybe you don't have the firewall rules configured for IPv6 or something. Breakage is extremely rare on the live web. I can't remember the last time I found a website that was only breaking on IPv6.

minimaul 3y ago
The other common mistake is blocking ICMPv6 completely. This creates a really broken IPv6 stack! edit: I've been running dual-stack with Windows, macOS, iOS & Linux for at least a decade now - I think it's closer to 20 years than 10! I've never seen it be like the parent post for my personal use, but I have seen it broken like that in places I've worked with incorrectly configured routers/firewalls. edit 2: this isn't a good idea for v4 either, but it's less broken than v6!
jedberg 3y ago
> You have some misconfiguration on your local network I’m sure I do. But that’s sort of the point. I only use standard commercial hardware with the default config. If that doesn’t work out of the box, what chance does someone who doesn't have my decades of networking experience have in fixing it? Granted I’m probably more sensitive than most because I know what network issues look like. Most people probably just think some things are slow sometimes. My ultimate point though is that this is probably a barrier to adoption.
- mahkoh 3y ago
  You have decades of networking experience but you are unable to get ipv6 to work, something that over 40% of internet users are using daily. [1] https://www.google.com/intl/en/ipv6/statistics.html https://www.google.com/intl/en/ipv6/statistics.html
  - jedberg 3y ago
    I can get it to work just fine. It just doesn't work as well as IPv4 and I can't be bothered to figure out why. I'm in that 40%. I use IPv6 on my phone whenever it's not in my house.
- minimaul 3y ago
  I think there's largely three groups that home users fall into here: 1. people who just use the router their ISP provides 2. people who go and buy off the shelf consumer routers/wifi - eg Netgear, Linksys, TP-Link 3. the kinds of people who run home labs and use small/medium business targeted routers/wifi like pfSense, VyOS, Unifi, Mikrotik, or even things like Juniper SRXes etc. The first group will get a 'blessed' and hopefully well tested IPv6 configuration when their ISP rolls it out, and I'd expect minimal problems there. Certainly haven't noticed anything big in the UK with some of our biggest ISPs rolling out v6. The third group will inevitably have teething troubles, but v6 works okay on those kinds of platforms once you know how to configure it, from my experience. The second group is where a lot of the pain will sit, imo. I've found consumer routers have really bad IPv6 implementations (things like broken prefix delegation, broken firewalling that can't be changed, IPv6 negotiation not working over PPPoE, weird RA settings, etc). The firmware on these kinds of devices is usually not great, and things like hardware acceleration engines in router CPUs are also frequently missing acceleration paths for v6 for things they already accelerate for v4. It will get fixed eventually, but it's going to be a pain point for a lot of years to come.
  - jedberg 3y ago
    I agree with you, this is a great assessment. And of course I'm in group two. I'm sure it's the router's fault, but other than IPv6 it works great, so there isn't really much reason to change it or dig into it. I'll just wait until I actually need v6 and then worry about it.
    - minimaul 3y ago
      And, each group is probably an order of magnitude smaller than the one before it - nearly everyone just uses their ISP's router. A small number of people use routers you can buy from Amazon, or in a store. A really tiny number of people use more professional equipment at home. The problem is, most IT professionals fall into one of the smaller two groups, so they get more friction than others, and that leads to them having more reluctance to roll out v6 at work, etc.
- deleted 3y ago
  [deleted]

minimaul 3y ago

The other common mistake is blocking ICMPv6 completely. This creates a really broken IPv6 stack! edit: I've been running dual-stack with Windows, macOS, iOS & Linux for at least a decade now - I think it's closer to 20 years than 10! I've never seen it be like the parent post for my personal use, but I have seen it broken like that in places I've worked with incorrectly configured routers/firewalls. edit 2: this isn't a good idea for v4 either, but it's less broken than v6!

jedberg 3y ago

> You have some misconfiguration on your local network I’m sure I do. But that’s sort of the point. I only use standard commercial hardware with the default config. If that doesn’t work out of the box, what chance does someone who doesn't have my decades of networking experience have in fixing it? Granted I’m probably more sensitive than most because I know what network issues look like. Most people probably just think some things are slow sometimes. My ultimate point though is that this is probably a barrier to adoption.

mahkoh 3y ago
You have decades of networking experience but you are unable to get ipv6 to work, something that over 40% of internet users are using daily. [1] https://www.google.com/intl/en/ipv6/statistics.html https://www.google.com/intl/en/ipv6/statistics.html
- jedberg 3y ago
  I can get it to work just fine. It just doesn't work as well as IPv4 and I can't be bothered to figure out why. I'm in that 40%. I use IPv6 on my phone whenever it's not in my house.
minimaul 3y ago
I think there's largely three groups that home users fall into here: 1. people who just use the router their ISP provides 2. people who go and buy off the shelf consumer routers/wifi - eg Netgear, Linksys, TP-Link 3. the kinds of people who run home labs and use small/medium business targeted routers/wifi like pfSense, VyOS, Unifi, Mikrotik, or even things like Juniper SRXes etc. The first group will get a 'blessed' and hopefully well tested IPv6 configuration when their ISP rolls it out, and I'd expect minimal problems there. Certainly haven't noticed anything big in the UK with some of our biggest ISPs rolling out v6. The third group will inevitably have teething troubles, but v6 works okay on those kinds of platforms once you know how to configure it, from my experience. The second group is where a lot of the pain will sit, imo. I've found consumer routers have really bad IPv6 implementations (things like broken prefix delegation, broken firewalling that can't be changed, IPv6 negotiation not working over PPPoE, weird RA settings, etc). The firmware on these kinds of devices is usually not great, and things like hardware acceleration engines in router CPUs are also frequently missing acceleration paths for v6 for things they already accelerate for v4. It will get fixed eventually, but it's going to be a pain point for a lot of years to come.
- jedberg 3y ago
  I agree with you, this is a great assessment. And of course I'm in group two. I'm sure it's the router's fault, but other than IPv6 it works great, so there isn't really much reason to change it or dig into it. I'll just wait until I actually need v6 and then worry about it.
  - minimaul 3y ago
    And, each group is probably an order of magnitude smaller than the one before it - nearly everyone just uses their ISP's router. A small number of people use routers you can buy from Amazon, or in a store. A really tiny number of people use more professional equipment at home. The problem is, most IT professionals fall into one of the smaller two groups, so they get more friction than others, and that leads to them having more reluctance to roll out v6 at work, etc.
deleted 3y ago
[deleted]