42.be (IPv6 only)(42.be)
42.be
42.be (IPv6 only)
http://42.be
21 comments
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
I'd bet you'd find more traffic was happening over IPv6 than you realised.
Looks amazing tbh http://i.imgur.com/V0B5HlY.png
https://i.imgur.com/qLWmI5p.png can't wait to see
What is the point of this? To test IPv6 connectivity? Because the end result is an extremely slow loading but mostly broken mosaic of small images that make up a silly meme.
http://ipv6test.google.com/ or http://test-ipv6.com/ are way better
http://ipv6test.google.com/ or http://test-ipv6.com/ are way better
Owner here, site is almost 6 years old.
There is no point to it, I was just trying out some fun things to do that wasn't possible with ipv4.
It's also not made for much traffic :)
It's also not made for much traffic :)
The Google site is sort of misleading, it’ll show a green checkmark even if you don’t have IPv6 at all. The other site is more informative.
If it's mostly broken, so is your IPv6 connectivity. I loaded all pictures but two myself, so got a complete image.
Seems many just timed out - how would ipv6 functionality show up as some images not working while others do?
Because your ISP doesn't have correct peering agreements, and doesn't see all IPv6 addresses...
[deleted]
3 (IPv6 only) sites and counting:
Edit: I forgot about ct.filippo.io -- we're up to 3 IPv6 only websites now!
http://loopsofzen.co.uk/
http://42.be/
https://ct.filippo.io/
Edit: I forgot about ct.filippo.io -- we're up to 3 IPv6 only websites now!
[deleted]
Been using IPv6 only addresses for my company internal use websites for years now.
Road warriors get on via our ipv6 only openvpn servers. Works like a charm.
Road warriors get on via our ipv6 only openvpn servers. Works like a charm.
> The image above is build-up of 1000 different images. Each image has its own ipv6 address.
archive.is mirror, in case you don't have IPv6 yet (interestingly, archive.org fails to mirror this site)
https://archive.is/cxAB9
archive.is mirror, in case you don't have IPv6 yet (interestingly, archive.org fails to mirror this site)
https://archive.is/cxAB9
Ah, so it's like the dancing kame of old: http://www.kame.net/
The site doesn't work. So naturally that means I don't have ipv6 support. What can do to change that or is it entirely upto my isp?
Also how do I get a ipv6 based instance in a host like amazon or linode etc?
Also how do I get a ipv6 based instance in a host like amazon or linode etc?
If you are inferring lack of IPv6 support from that site not loading, be aware that the site loads very slowly. If you want to see if you have working IPv6, try here [1].
If that says you do not have IPv6, then here are thing to check.
1. Check your computer to make sure it is asking the router for an IPv6 address. On my Mac, for example, it was originally only asking for an IPv4 address. When I changed the settings for my ethernet port to ask for an IPv6 address too it worked.
2. If your computer is asking for an IPv6 address but not getting one, check the modem or router provided by your ISP. On its settings or status page it should say if it supports IPv6, and whether or not it has got an address from the ISP, and whether or not its DHCP server is configured to let your computers have an IPv6 address.
3. If your computer and the ISP supplied modem or router all support IPv6 and are configured to use it, check any intermediate routers you use. For example, if your ISP supplied router is wired-only, and you have a wireless router of your own plugged into it via ethernet, and your computer gets to the internet via that wireless router, you'll need to have it set up to support IPv6 too.
[1] http://test-ipv6.com
If that says you do not have IPv6, then here are thing to check.
1. Check your computer to make sure it is asking the router for an IPv6 address. On my Mac, for example, it was originally only asking for an IPv4 address. When I changed the settings for my ethernet port to ask for an IPv6 address too it worked.
2. If your computer is asking for an IPv6 address but not getting one, check the modem or router provided by your ISP. On its settings or status page it should say if it supports IPv6, and whether or not it has got an address from the ISP, and whether or not its DHCP server is configured to let your computers have an IPv6 address.
3. If your computer and the ISP supplied modem or router all support IPv6 and are configured to use it, check any intermediate routers you use. For example, if your ISP supplied router is wired-only, and you have a wireless router of your own plugged into it via ethernet, and your computer gets to the internet via that wireless router, you'll need to have it set up to support IPv6 too.
[1] http://test-ipv6.com
If your ISP provides IPv6, then it's up to your router to support it and hand out an address to your computer. You might be able to get a firmware update for it, or use a good third-party one. Your OS almost certainly supports IPv6 already, it just needs access.
If your ISP doesn't provide IPv6 at all, then aside from switching ISPs, you can try getting a tunnel from a service like https://tunnelbroker.net/ (Hurricane Electric), although I've never used that service, only SixXS when it was around.
Who's your ISP?
If your ISP doesn't provide IPv6 at all, then aside from switching ISPs, you can try getting a tunnel from a service like https://tunnelbroker.net/ (Hurricane Electric), although I've never used that service, only SixXS when it was around.
Who's your ISP?
Yeah feared as much. Don't think my isp is going to roll out ipv6 anytime soon (government owned, stuck in ie6 age isp, BSNL).
[deleted]
[deleted]
See also tetris on traceroute: https://news.ycombinator.com/item?id=14621887
Interesting trying to tcpdump this; of course it basically explodes in reverse DNS queries. tcpdump -n is needed, but I wonder if this sort of behaviour could be exploited in some nasty/interesting way.
Hey zbuf, if you go to any of Cleanfeed's blog posts, the FAQ and Contact links in the footer are broken.
I didn't care much about the IPv6 rollout until I spent 2 days a few weeks ago tracking down a routing table issue that I resolved by using IPv6 everywhere in my internal network.
Now it can't come soon enough.
Now it can't come soon enough.
IPv6, that mythological creature.
It's not all that mythological. Here are the IPv6 deployment percentages for major US IPSs:
53% Comcast
64% AT&T
24% Charter
86% Verizon Wireless
85% T-Mobile
41% AT&T Wireless
33% Cox
47% Sprint Wireless
68% Google Fiber
I don't believe those numbers for a goddamn second.
Verizon tells me they have IPV6, but after talking with techs for over an hour, and going through 3 people that didn't know what I was talking about and were confused because "we can reach your ONT, so your internet should be working!", I finally got to someone who never set it up in my area despite telling me that it was supported.
I don't know what it means to be supported, but it sure as hell doesn't mean I can actually use it.
Verizon tells me they have IPV6, but after talking with techs for over an hour, and going through 3 people that didn't know what I was talking about and were confused because "we can reach your ONT, so your internet should be working!", I finally got to someone who never set it up in my area despite telling me that it was supported.
I don't know what it means to be supported, but it sure as hell doesn't mean I can actually use it.
Verizon Wireless != Verizon FIOS
Fair enough, I obviously misread that!
But i'm still peeved that they continue to tell me IPV6 is supported, but can't ever get it working, their equipment or mine.
But i'm still peeved that they continue to tell me IPV6 is supported, but can't ever get it working, their equipment or mine.
Verizon (not VZW) have said IPv6 is coming to Fios for about 5 years now. They routers they provide have supported it for about as long as well. Supposedly the hangups include their older video on demand service (and/or set top boxes) not supporting IPv6, and older equipment in some of the earlier deployment areas. Still not a great excuse to not roll it out gradually, but in the meantime I've set up a tunnel with Hurricane Electric and an alternative DNS server to filter out AAAA requests for Netflix (which blocks HE).
Well, while we're trading anecdotes, Comcast IPv6 just works out of the box here for me and they even fixed their bufferbloat a few months ago.
As much as I criticized Comcast relentlessly (and switched to Sonic the moment I was able to), their IPv6 rollout was flawless for me.
Yep. Been a happy Comcast v6 customer for many years. Flawless rollout from my end.
Interesting... just tried my AT&T Wireless iPhone, apparently I'm in the 59% that doesn't have IPv6.
One fifth of Google traffic seems non-trivial: https://www.google.com/intl/en/ipv6/statistics.html
br$ netstat -s
[...]
ip6:
97835547 total packets received
We have IPv6 at my workplace (part of a university) and initially configured all of my servers and clients to use it. However, it has ended up being more trouble than it's worth, so now I disable it by default. There need to be more graceful fallback mechanisms in the transition period, and those might need to happen higher up the protocol stack, for it to work well enough for the average person.
[deleted]
Note: Even if you have full IPv6 support, this site loads extremely slowly, and there may be infrequent misses. You can perform an alternative test on http://test-ipv6.com/ if you are unsure.
Works for me only if I turn wifi off. A good reminder to try re enabling IPv6 on my router!
Well. That crashes my router immediately and repeatably. (Edit: Immediately with firefox, after slightly longer with chrome.)
Looks nice though, once I throttle connections.
Looks nice though, once I throttle connections.
Is there any practical reason you'd host each of your website's images or scripts or whatever at different addresses, if IPv6 was widespread?
Thank you for reminding me to check whether my Google Wifi supports IPv6 yet. (It does now!)
Well... at the very least I now know my IPv6 actually works.
Why is it so slow? Is that because of IPv6?
Server not found, here. Comcast.