12 ms·

I recently configured my router to support IPv6 and had to disable it. A lot of websites that resolved to AAAA didn't have a working server on the other side. M

I recently configured my router to support IPv6 and had to disable it. A lot of websites that resolved to AAAA didn't have a working server on the other side. Major websites half loading became common and I spent a lot of time troubleshooting everything. It was a bummer.

seiferteric 9y ago
Sigh me too, but only because for some reason my ipv6 traffic was capped at about 1.5Mbps from my ISP even though I have 100Mbps internet.
vmp 9y ago
Same here :/ It seems that IPv6 is a mere afterthought for most content providers - like Linux ports for popular Games... or civil discussion on forums. ;) The weirdest thing I noticed in the past was, that IPv6 via Tunnelbroker.net actually worked better than ISP-provided-native-v6, though I haven't tried using a tunnel in a long time.
- thwarted 9y ago
  A lot of websites that resolved to AAAA didn't have a working server on the other side. It seems that IPv6 is a mere afterthought for most content providers IPv6 via Tunnelbroker.net actually worked better than ISP-provided-native-v6 Sounds more like a problem with your ISP's IPv6 support than the content providers. It seems unlikely that someone would go to the trouble to add an IPv6 address to DNS if they didn't have a working server up. It's much more likely that crappy ISPs don't have their IPv6 infrastructure set up correctly.
mmagin 9y ago
I haven't had much problem that I'm aware of it at home, though on a couple occasions I had comcast fuck up ipv6 routing while ipv4 worked fine. But with work I have more problems. Some of our machines do have ipv6 addresses and AAAA records, but the IT-department-maintained VPN doesn't do ipv6. So I had to tell ssh to only use v4 in my .ssh/config. It's amazing to me how far we're still from reasonably universal ipv6.
subway 9y ago
This is almost certainly your ISP (or tunneling configuration), not the content providers screwing up, as networks like T-Mobile and Verizon are quickly becoming IPv6-first networks. A great many folks successfully pass a majority or all their traffic across IPv6 without even being aware it exists.
Twirrim 9y ago
It's been working fine for me on Comcast, apart from one point last weekend when their IPv6 got messed up for an hour or so. Took me a while to realise that was why some sites were working and others weren't. I'd bet you'd find more traffic was happening over IPv6 than you realised.

seiferteric 9y ago

Sigh me too, but only because for some reason my ipv6 traffic was capped at about 1.5Mbps from my ISP even though I have 100Mbps internet.

vmp 9y ago

Same here :/ It seems that IPv6 is a mere afterthought for most content providers - like Linux ports for popular Games... or civil discussion on forums. ;) The weirdest thing I noticed in the past was, that IPv6 via Tunnelbroker.net actually worked better than ISP-provided-native-v6, though I haven't tried using a tunnel in a long time.

thwarted 9y ago
A lot of websites that resolved to AAAA didn't have a working server on the other side. It seems that IPv6 is a mere afterthought for most content providers IPv6 via Tunnelbroker.net actually worked better than ISP-provided-native-v6 Sounds more like a problem with your ISP's IPv6 support than the content providers. It seems unlikely that someone would go to the trouble to add an IPv6 address to DNS if they didn't have a working server up. It's much more likely that crappy ISPs don't have their IPv6 infrastructure set up correctly.

mmagin 9y ago

I haven't had much problem that I'm aware of it at home, though on a couple occasions I had comcast fuck up ipv6 routing while ipv4 worked fine. But with work I have more problems. Some of our machines do have ipv6 addresses and AAAA records, but the IT-department-maintained VPN doesn't do ipv6. So I had to tell ssh to only use v4 in my .ssh/config. It's amazing to me how far we're still from reasonably universal ipv6.

subway 9y ago

This is almost certainly your ISP (or tunneling configuration), not the content providers screwing up, as networks like T-Mobile and Verizon are quickly becoming IPv6-first networks. A great many folks successfully pass a majority or all their traffic across IPv6 without even being aware it exists.

Twirrim 9y ago

It's been working fine for me on Comcast, apart from one point last weekend when their IPv6 got messed up for an hour or so. Took me a while to realise that was why some sites were working and others weren't. I'd bet you'd find more traffic was happening over IPv6 than you realised.