Closed Bug 92002 Opened 23 years ago Closed 23 years ago

SOCKS: MacOS fails to connect

Categories

(Core :: Networking, defect)

Product:
Core
Component:
Networking
Platform:
PowerPC
Mac System 9.x
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: benc, Assigned: smeredith)

References

Details

MacOS 07-20-03-092, commercial.

This is supposed to be a known bug, but I couldn't find it, so I created this:

Using a Netscape SOCKS v5 server that works with Win32 and Linux.

After several seconds, the error: "connection refused" is returned.

Here's a quick packet trace I did:

h-208-12-40-158.netscape.com -> www.packetgram.com SOCKS C port=49210

           0: 0204 0564 0101 0101                        ...d....

www.packetgram.com -> h-208-12-40-158.netscape.com SOCKS R port=49210

           0: 0204 0564                                  ...d

h-208-12-40-158.netscape.com -> www.packetgram.com SOCKS C port=49210

           0: 0501 0000 0000                             ......

www.packetgram.com -> h-208-12-40-158.netscape.com SOCKS R port=49210


www.packetgram.com -> h-208-12-40-158.netscape.com SOCKS R port=49210

           0: 0500                                       ..

h-208-12-40-158.netscape.com -> www.packetgram.com SOCKS C port=49210

           0: 0501 0001 3fc9 391d 5000                   ....?.9.P.

           0: 0501 0001 3fc9 391d 5000                   ....?.9.P.

www.packetgram.com -> h-208-12-40-158.netscape.com SOCKS R port=49210


www.packetgram.com -> h-208-12-40-158.netscape.com SOCKS R port=49210

           0: 0505 0001 0000 0000 5000                   ........P.

www.packetgram.com -> h-208-12-40-158.netscape.com SOCKS R port=49210


h-208-12-40-158.netscape.com -> www.packetgram.com SOCKS C port=49210

           0: 0000 0000 0000                             ......

www.packetgram.com -> h-208-12-40-158.netscape.com SOCKS R port=49210


h-208-12-40-158.netscape.com -> www.packetgram.com SOCKS C port=49210

           0: 0000 0000 0000                             ......

Here's the log file, for what it's worth:

[23/Jul/2001:16:19:50] 265 request: * 5 connect: ok 208.12.40.158:49208 -> 216.2
00.247.134:20480
[23/Jul/2001:16:20:05] 265 request: * 5 connect: failed 208.12.40.158:49208 -> 2
16.200.247.134:20480
[23/Jul/2001:16:20:27] 266 request: * 5 connect: ok 208.12.40.158:49209 -> 208.1
42.131.191:47873
[23/Jul/2001:16:20:42] 266 request: * 5 connect: failed 208.12.40.158:49209 -> 2
08.142.131.191:47873
[23/Jul/2001:16:22:50] 267 request: * 5 connect: ok 208.12.40.158:49210 -> 63.20
1.57.29:20480
[23/Jul/2001:16:22:50] 267 request: * 5 connect: failed 208.12.40.158:49210 -> 6
3.201.57.29:20480
#
The SOCKS code on the mac swaps the bytes around for the port number. This has
been fixed in bug 65583, which is awaiting review.
Status: NEW → ASSIGNED
Steve - you need to reassign a bug to yourself before marking it assigned.
Marking dependancy.
Assignee: neeti → smeredith
Status: ASSIGNED → NEW
Depends on: 65583
Fixed by fix for 65583.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
reassigning QA Contact to myself
QA Contact: benc → trix
changing QA contact to lrg@netscape.com
QA Contact: trix → lrg
I have been able to connect using SOCKS 4/5 on MacOS 10.x an 9.x, so i am
marking this as verified
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.