Opened 11 years ago

Last modified 5 years ago

#3689 closed Bug report

Unknown SOCKS protocol version

Reported by: darkoddio Owned by:
Priority: high Component: FileZilla Client
Keywords: Cc: darkoddio, Tim Kosse
Component version: Operating system type:
Operating system version:

Description

Using the same socks 5 proxy, connection work with Filezilla version 2.2.32 but I receive error "Unknown SOCKS protocol version: 1" with FileZilla version 3.1.1.1

Attachments (4)

filezilla_bug.JPG (142.7 KB) - added by darkoddio 11 years ago.
configurations and logs
filezillacap.zip (3.7 KB) - added by darkoddio 11 years ago.
wireshark captures
filezilla_bug2.JPG (39.8 KB) - added by darkoddio 11 years ago.
with nightly build
FileZillaCap3.zip (747 bytes) - added by darkoddio 11 years ago.

Download all attachments as: .zip

Change History (17)

Changed 11 years ago by darkoddio

Attachment: filezilla_bug.JPG added

configurations and logs

comment:1 Changed 11 years ago by Tim Kosse

Last time I checked, port 8118 is for HTTP proxies. You sure you got the correct port?

comment:2 Changed 11 years ago by darkoddio

yes, I am sure the SOCKS proxy is configured on port 8118
The port, as many other programs, is configurable by the user
As you can see in the screenshot, with 2.2.32 version of filezilla is working perfectly

comment:3 Changed 11 years ago by Tim Kosse

Please run a network sniffer like Wireshark to monitor the communication with the proxy to see the difference. Attach your results here.

Changed 11 years ago by darkoddio

Attachment: filezillacap.zip added

wireshark captures

comment:4 Changed 11 years ago by darkoddio

In the attachment you can find two capture files
I changed some ip, username and password in the 2.2.32 version capture, so you can see some TCP CHECKSUM INCORRECT
Hope this can help, bye
File Added: filezillacap.zip

comment:5 Changed 11 years ago by Tim Kosse

Thanks for reporting, fix has been committed to the repository. Please try the upcoming 2008-08-20 build from http://filezilla-project.org/nightly.php and reopen this report if it still does not work.

Changed 11 years ago by darkoddio

Attachment: filezilla_bug2.JPG added

with nightly build

comment:6 Changed 11 years ago by darkoddio

With nightly build downloaded today something changed, but still no success
see attachment with debug level 4
File Added: filezilla_bug2.JPG

comment:7 Changed 11 years ago by Tim Kosse

Got another capture?

Changed 11 years ago by darkoddio

Attachment: FileZillaCap3.zip added

comment:8 Changed 11 years ago by darkoddio

Capture with nightly build
(sorry for duplicate ticket)
File Added: FileZillaCap3.zip

comment:9 Changed 11 years ago by Tim Kosse

According to the log you have a TCP checksum error and possibly other problems as well. This would make this a problem with your system, nothing that can be caused nor solved by FileZilla.

comment:10 Changed 11 years ago by darkoddio

if you read previus comments, the invalid checksum is caused by me: I changed ip, username and password with text editor in the cap file

comment:11 Changed 11 years ago by Tim Kosse

I usually do not reread the entire bug report, only the relevant changes. Saves a lot of time.

Should be fixed now with the upcoming 2008-08-22 nightly.

comment:12 Changed 11 years ago by darkoddio

thanks codesquid, it works
I'm glad to help you :-)

Note: See TracTickets for help on using tickets.