Opened 3 years ago

Closed 3 years ago

#11197 closed Bug report (rejected)

Filezilla requiring passive mode to ftp server on foscam camera on non standard FTP port

Reported by: Mark Owned by:
Priority: normal Component: FileZilla Client
Keywords: Cc:
Component version: 3.24.1 Operating system type: OS X
Operating system version: 10.11.6 (El Capitan)

Description

Until a recent update, I was having no trouble connecting to a FOSCAM camera, but now it fails. I've tried forcing active connections, but filezilla insists on going into passive mode. There are no firewalls between me and the camera. All traffic is going over an always on VPN. Here's the log details:
2017-03-09 08:57:08 1901 1 Response: 331 User root OK. Password required
2017-03-09 08:57:08 1901 1 Command: PASS
2017-03-09 08:57:08 1901 1 Response: 230 OK. Current directory is /
2017-03-09 08:57:08 1901 1 Status: Server does not support non-ASCII characters.
2017-03-09 08:57:08 1901 1 Status: Logged in
2017-03-09 08:57:08 1901 1 Status: Retrieving directory listing...
2017-03-09 08:57:08 1901 1 Command: PWD
2017-03-09 08:57:08 1901 1 Response: 257 "/" is your current location
2017-03-09 08:57:08 1901 1 Command: TYPE I
2017-03-09 08:57:08 1901 1 Response: 200 TYPE is now 8-bit binary
2017-03-09 08:57:08 1901 1 Command: PASV
2017-03-09 08:57:08 1901 1 Response: 425 Unable to open a passive connection: Permission denied
2017-03-09 08:57:08 1901 1 Command: PORT 192,168,3,113,248,216
2017-03-09 08:57:08 1901 1 Response: 200 PORT command successful
2017-03-09 08:57:08 1901 1 Command: MLSD
2017-03-09 08:57:28 1901 1 Error: Connection timed out after 20 seconds of inactivity
2017-03-09 08:57:28 1901 1 Error: Failed to retrieve directory listing

Connection Settings:
Logon Type: Normal
Encryption: Only use plain FTP
Protocol: FTP
Port: 50021
Transfer mode: Active
Charset: Autodetect
Server Type: Autodetect

Change History (1)

comment:1 by Tim Kosse, 3 years ago

Resolution: rejected
Status: newclosed

As you can see in the log, passive mode is not required, the client falls back to active mode after the server rejects passive mode.

It looks like your VPNs routing tables are not setup correctly on the server, breaking active mode.

Note: See TracTickets for help on using tickets.