Open
Bug 987785
Opened 10 years ago
Updated 5 months ago
MacOS X: Can not connect to IPv4-only sites from IPv6-only node via SOCKS proxy
Categories
(Core :: Networking: Proxy, defect, P3)
Tracking
()
UNCONFIRMED
People
(Reporter: ayourtch, Unassigned)
References
Details
(Whiteboard: [ipv6][necko-backlog])
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_2) AppleWebKit/537.74.9 (KHTML, like Gecko) Version/7.0.2 Safari/537.74.9 Steps to reproduce: 1. Use a pure IPv6 access network (no NAT64), using Google's DNS (2001:4860:4860::8888) 2. Open an SSH connection with SOCKS (-D 1080) to a dual stack server (ssh -D 1080 username@dualstack.server.example.com) 3. Configure Firefox to use SOCKS proxy on localhost:1080 4. Attempt to connect to www.cnn.com, for example. Actual results: The "Problem loading page" window appears, saying "Firefox can't find the server at www.cnn.com." The tcpdump on the wire shows that the firefox is doing a AAAA lookup for the server (which returns no info), does not attempt to do A lookups, and never attempts to communicate via SOCKS proxy. Expected results: The browser should have attempted either to use an IPv4 address, or a hostname, to connect to the target.
Mac OS X version is 10.9.2. I am submitting this report using Safari, which appears to work correctly (with SOCKS configured in the system preferences). Chrome works correctly as well.
Updated•10 years ago
|
Whiteboard: [ipv6]
Comment 2•10 years ago
|
||
please report if the problem is the same with network.proxy.socks_remote_dns set to true
If I set network.proxy.socks_remote_dns to true then the problem disappears! A great workaround, thanks! (When starting SSH with the debug flag, I noticed that Chrome uses remote DNS by default - the connections are opened by names, as opposed to addresses in Firefox's case)
Updated•9 years ago
|
Whiteboard: [ipv6] → [ipv6][necko-backlog]
Comment 4•7 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P1
Comment 5•7 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: P1 → P3
Updated•2 years ago
|
Severity: normal → S3
Comment 6•5 months ago
|
||
Moving bug to Core/Networking: Proxy.
Component: Networking → Networking: Proxy
You need to log in
before you can comment on or make changes to this bug.
Description
•