1239948 - Feature request: Add support for NAT64 / 464XLAT

Status: UNCONFIRMED

(Core :: Networking, enhancement, P5)

Description

[mdjrosenau]

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:43.0) Gecko/20100101 Firefox/43.0
Build ID: 20160105164030

Steps to reproduce:

Many (especially mobile) internet providers begin to use 464XLAT for internet connections. Unfortunately Desktop versions of Windows do not support 464XLAT on OS level so applications need to have support for this when using certain web sites.

Even if only mobile providers will use 464XLAT: There are many customers who use mobile connections (UMTS/LTE) with a laptop or even desktop computers so it is necessary that 464XLAT is also supported on desktop computers.


Actual results:

Using an internet provider that uses NAT64/DNS64 all servers that use DNS names should work propperly (such as "www.example.com"). However you often find addresses in web sites that look like this:

<img src="http://192.0.2.123/example.png" />

In this case loading the image (or whatever) will fail when the connection uses any kind of NAT64 variant (NAT64/DNS64 or 464XLAT).


Expected results:

In the dialog window where you can select between:

"Direct connection" and "Use a proxy server"

There should be three choices:

"Direct connection", "NAT64 or 464XLAT" and "Use a proxy server".

If you choose "NAT64 or 464XLAT" you may use the default prefix (64:ff9b::/96) or type in the prefix used by your provider (e.g. 2001:db8:1234::).

IPv6 addresses behave like "direct connection" while IPv4 addresses are translated to IPv6 addresses in NAT64 mode: 192.0.2.123 becomes 2001:db8:1234::C000:27B so actually http://[2001:db8:1234::C000:27B]/example.png will be accessed instead of http://192.0.2.123/example.png.

Comment 1

[Firefox Bug Husbandry Bot]

Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258