Opened 16 years ago
Last modified 11 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)
Change History (17)
by , 16 years ago
| Attachment: | filezilla_bug.JPG added |
|---|
comment:1 by , 16 years ago
Last time I checked, port 8118 is for HTTP proxies. You sure you got the correct port?
comment:2 by , 16 years ago
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 by , 16 years ago
Please run a network sniffer like Wireshark to monitor the communication with the proxy to see the difference. Attach your results here.
comment:4 by , 16 years ago
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 by , 16 years ago
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.
comment:6 by , 16 years ago
With nightly build downloaded today something changed, but still no success
see attachment with debug level 4
File Added: filezilla_bug2.JPG
by , 16 years ago
| Attachment: | FileZillaCap3.zip added |
|---|
comment:8 by , 16 years ago
Capture with nightly build
(sorry for duplicate ticket)
File Added: FileZillaCap3.zip
comment:9 by , 16 years ago
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 by , 16 years ago
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 by , 16 years ago
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.
configurations and logs