Currently none of the mozilla-related pages such as mozilla.org, mozilla.com, getfirefox.com, etc have an ipv6 presence, so Firefox is very difficult to obtain if all you have is ipv6 connectivity. Some of the mirrors do (mozilla.isc.org, for example), so if you just happen to know their addresses then you can find the binaries. However, this is a terrible thing to have to do, because the list of mirrors is on mozilla.org, and therefore isn't available via ipv6! Given that ipv6 tunnels are very easy to get even if your isp doesn't provide native ipv6 access (I get mine from sixxs.net), I think this problem shouldn't be too difficult to resolve.
This was techincally difficult to do prior to July when we moved to a different colo and improved our infrastructure. Ironically, all the major "parts" within the network are already running v6, however, I haven't had the time to pursue a native or tunneled connection with any of our upstream providers. I'll put this on my to-do list but it's not likely something I'll be able to do until after the new year.
Assignee: server-ops → mrz
Update - this requires a code upgrade on the Netscalers, which won't be available until Q1 2007. This adds the feature to present a v6 VIP for a pool of v4 servers. I'll hold this open until then.
Status: NEW → ASSIGNED
Whiteboard: Pending Netscaler code - Q1 2007
Component: Server Operations → Server Operations: Projects
now that landfill has ipv6, what needs to be done to enable it everywhere else?
Two things - 1. I'm waiting on Citrix to provide the ipv6 license key for that feature set 2. I don't have any native v6 transit. What I have is v4 tunnels to Sprint and ISC, both of which are gift'd tunnels and not something I'd want to run production traffic across - they aren't contractually required to support this or even keep it up. #1's in progress and #2 is something I'm researching.
I'm hesitant to just deploy v6 without making sure that I don't lose users in the process though. See my blog posting on that.
This is extremely low priority - moving to projects.
Severity: normal → enhancement
Oh yea, I had seen that post. Have you made any progress on using that logging idea from Nathan Ward? The code could use a little cleanup, but looks passable. Also, I doubt there are very many people with a real global unicast address but no connectivity, because in general nobody configures their network to have ipv6 addresses unless they have connectivity.
(In reply to comment #7) > Oh yea, I had seen that post. Have you made any progress on using that logging > idea from Nathan Ward? The code could use a little cleanup, but looks passable. > No, not yet. > Also, I doubt there are very many people with a real global unicast address but > no connectivity, because in general nobody configures their network to have > ipv6 addresses unless they have connectivity. > Not sure - Vista users will appear to have v6 connectivity without doing anythin special. Same with Airport Extreme users. In any case I want to make sure I don't lose users.
Mac OS X has shipped with ipv6 enabled by default since 10.2 or so. That's one of the popular troubleshooting tips for Mac folks without ipv6 connectivity to speed up their DNS resolution times is to disable ipv6.
(In reply to comment #8) > (In reply to comment #7) > > Oh yea, I had seen that post. Have you made any progress on using that logging > > idea from Nathan Ward? The code could use a little cleanup, but looks passable. > > > > No, not yet. In that case lets give it a try. If you can add the required dns entries to the landfill.bugzilla.org domain, then I'll add the html code to my test install of bugzilla. It wants ipv4.landfill.bugzilla.org, ipv6.landfill.bugzilla.org, ipv6and4.landfill.bugzilla.org
(In reply to comment #10) > It wants ipv4.landfill.bugzilla.org, ipv6.landfill.bugzilla.org, > ipv6and4.landfill.bugzilla.org landfill.bugzilla.org (both ipv4/ipv6), landfill.ip4.bugzilla.org (ipv4 only), landfill.ip6.bugzilla.org (ipv6 only)
https://landfill.bugzilla.org/bug369429/ has the code, though the script that collects the stats from the access log isn't completed yet. I'm still working on the output.
Marking as WONTFIX for now. There's so little user demand for v6 and we don't yet have any native v6 connectivity that I don't see this happening any time soon.
Status: ASSIGNED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → WONTFIX
As this is an RFE I don't see why it's wontfix. Why not leave it open and assigned to nobody like all other bugs that certainly are wanted but noone fixed them yet?
Sticking this back in the projects queue for when IPv6 support at Mozilla is working, especially since Mozilla now has its own IPv6 block (http://whois.arin.net/rest/net/NET6-2620-101-8000-1).
Assignee: mrz → nobody
Status: RESOLVED → REOPENED
QA Contact: justin → mrz
Resolution: WONTFIX → ---
Whiteboard: Pending Netscaler code - Q1 2007
Summary: mozilla.org isn't accessable from ipv6 only hosts → mozilla.org isn't accessible from ipv6 only hosts
Assignee: nobody → server-ops
Severity: enhancement → normal
Component: Server Operations: Projects → Server Operations
Whiteboard: [ Post FF4 ] → [goal for world ipv6 day]
Status: NEW → RESOLVED
Last Resolved: 10 years ago → 7 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.