bugzilla.mozilla.org will be intermittently unavailable on Saturday, March 24th, from 16:00 until 20:00 UTC.
Having read most of the IPv6 bugs, I don't even know if this is possible, but it was proposed in bug 86449 after several contributors scratched their heads for several months. If it is possible, we should disable support with a pref, and set it off by default. As an example, in the "commercial" Netscape 6 functional tests that I do for general networking, we do not do any IPv6 testing at this time. At the same time, IPv6 is probably the future, so we need documentation here, so we can get more testers on board focused on these features, <insert usual 'helpwanted' text...>
Indeed. As IPv6 isn't quite functional on the internet right now, it seems to be more trouble than it's worth to chase this moving target.
It would be more trouble than its worth to find all the places we need ifdefs for, I think.
THere really hasn't been much pressure on anyone to do this.
Priority: -- → P5
Target Milestone: --- → Future
People who are on IPv6 systems need to be smarter than the average IPv4 user anyhow. This is a good RFE, but probably not a big deal. What we need is better documentation about IPv6, like how to help someone determine that someone else turned it on...
moving neeti's futured bugs for triaging.
Assignee: neeti → new-network-bugs
*** Bug 181610 has been marked as a duplicate of this bug. ***
Recommend WONTFIX. Time marches on.
-> dariin for decision. I'm too behind on my IPv6 bugmail to really know what is going on.
Assignee: new-network-bugs → darin
Note that IPv6 is now disabled on Mac OS X if you're not running 10.3 or higher (bug 222031)
Based on the DNS problems we have in bug 68796, I think this bug should be re-considered. For example, if I upgrade to Mac OS X 10.3, I am not going to be using IPv6, even if the OS and mozilla support it. If these features create problems, I should be able to run w/o them.
If you're not on an IPv6 network, bug 68796 doesn't affect you.
A pref (network.dns.enableIPv6) now exists to turn IPv6 name lookups off, and that pref is set to true on OS X by default. I suggest WONTFIX. :)
(In reply to comment #9) > Note that IPv6 is now disabled on Mac OS X if you're not running 10.3 or higher > (bug 222031) In fact, in 1.7a and the latest nightly of Firebird, IPV6 is completely disabled on 10.3.3 I'm dead in the water with my favourite browsers since I'm on IPV6. I have to use the Safari hack to surf.
(In reply to comment #13) > I'm dead in the water with my favourite browsers since I'm on IPV6. I have to > use the Safari hack to surf. If you need IPv6 on Mac OS 10.3, you can do so by setting the pref "network.dns.disableIPv6" to false? You can use about:config to do this. If IPv6 doesn't work after that, it's a bug and you should let me know. :) This was mentioned in the release notes for 1.7a, but maybe it deserves more attention. I should post it to the apple-ipv6 mailing list, since it's mainly an OS bug and maybe they can fix it.
14 years ago
Assignee: darin → nobody
QA Contact: benc → networking
Target Milestone: Future → ---
Effectively a duplicate of bug 377383 "enable ipv6 by default". More recent discussion has been taking place there.
I'm of the mind to WONTFIX this bug for two reasons: The original purpose of this bug was to use the technical issue to hilight the problem area, which was that we needed to add ipv6 support in two ways: 1- Add features that support IPv6 (mostly through changing network API's) 2- Do platform + product checking to make sure that as vendors started sliding in IPv6 support, that it works. and... 3- A master switch would have allowed people to add IPv6 address support at higher levels, but off by default, to avoid accidental regressing of the rest of the world... I would imagine that #1 is almost done, and #2 did not create enormous problems (probably because at some point, the DNS switch was added via "design by bug"). Because we've gone from "very little IPv6" to "almost everyone but pre-Vista", I think we should close this bug, and let new problems go to new bugs. The only possible reason I can think of why we'd preserve an IPv4-only mode would be for embedding, but those devices are inevitably going to operate in an IPv6 world...
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.