During the past two Firefox releases (2.0.0.5 and 2.0.0.6) I’ve been running an dual-stake ipv4/ipv6 accessible download server. This box was serving Firefox updates and was part of releases.mozilla.org. I thought I could use traffic numbers to help justify a native ipv6 Internet connection.
Here’s what ipv4 traffic looked like during a one week period covering a release:
And ipv6…
Er, where is everyone?
Comments (4)
Hardly anybody has IPv6 connectivity. Even my dedicated server is losing it as the company’s been bought by another one who don’t offer IPv6 and don’t seem to be interested in using their acquisition of a company who do to start. Not that we ever used it. IPv6 just isn’t going to take off - at least, not until it comes standard with normal internet connections (not the hyper-expensive kind) and normal consumer routers support it. You really have to want it to get it, and be willing to pay more for it, and… what does it actually get you? At the moment, not very much.
Bit chicken and egg-y of course.
Does that server handle updates for nightlies? I’d be willing to bet that people with ipv6 are more likely to use a beta build.
Hi,
In an earlier entry you mentioned “secret IPv6 addresses”, When I trace the www.mozilla.org/www.mozilla.com/addons.mozilla.com addresses I do not see any AAAA entries in the DNS.
So, the fact you are getting queries at all must mean that all those people have manually put in AAAA addresses in their hosts file.
I’m, therefore, pretty impressed by that amount of traffic. Imagine if mozilla published the IPv6 AAAA entries in the DNS?
Regards,
Anand
That’s true but those graphs where specificially for download01.mozilla.org, the download mirror I’ve been running as a dual stack box. It also served releases.mozilla.org:
download01.mozilla.org has AAAA address 2620:0:330:21:218:71ff:fe87:3ec0
releases.mozilla.org has AAAA address 2001:4f8:0:2::1f
releases.mozilla.org has AAAA address 2620:0:330:21:218:71ff:fe87:3ec0
The graphs for www.mozilla.org/com and AMO are nearly non-existent.