Closed Bug 527714 Opened 15 years ago Closed 14 years ago

IPv6 preferred over IPv4

Categories

(Firefox :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: gabriele, Unassigned)

References

()

Details

(Whiteboard: [CLOSEME 2011-1-30])

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.4) Gecko/20091028 Iceweasel/3.5.4 (Debian-3.5.4-1) Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.4) Gecko/20091028 Iceweasel/3.5.4 (Debian-3.5.4-1) It seems that default and only behavior in firefox makes IPv6 preferred over IPv4 when available, this makes some sites which got both IPv4 and IPv6 addresses unavailable. Setting the option network.dns.disableIPv6 to true solves this issue but also breaks IPv6 connectivity. Considering bugs 376226 and 494727, I think the best and very easy solution to this problem and these bugs should be to implement a new configuration option network.dns.IPv4preferred that, if enabled, makes IPv4 preferred over IPv6. Another more likely but most complex solution should be having an automatic IPv4 fallback when loading a website with IPv6 fails or takes too long. Thank you Reproducible: Always Steps to Reproduce: 1.Have a PC with both IPv6 and IPv4 connectivity 2.Open a website both IPv6 and IPv4 accessible 3.The website will be opened using its IPv6 address, if unreachable, connection will fail.
dupe of bug 213121 ?
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode? If not, please close. These links can help you in your testing. http://support.mozilla.com/kb/Safe+Mode http://support.mozilla.com/kb/Managing+profiles You can also try to reproduce in Firefox 4 Beta 8 or later, there are many improvements in the new version, http://www.mozilla.com/en-US/firefox/all-beta.html
Whiteboard: [CLOSEME 2011-1-30]
I don't see this in 4.0b9 ... http://www.comcast6.net reports my IPv6 address
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.