Cyberduck Mountain Duck CLI

#998 closed enhancement (worksforme)

Connecting to FTP server behind firewall with port forwarding failing

Reported by: epugh Owned by: dkocher
Priority: normal Milestone: 2.7.3
Component: ftp Version: 2.7.2
Severity: normal Keywords:
Cc: Architecture:

Description (last modified by dkocher)

I have a FTP server behind a firewall... The firewall is, and the server is When I connect using cyberduck I get back the PORT to use as, not my public IP address!

Here is the text of my IM conversation with my friend who diagnosed it: 
ok, so an ftp server sends its ip address in the response to a passive mode PORT request, along with the port number to connect to...
» ie. I send PORT, it sends back (my ip):5005 or somesuch.
Eric Pugh 
Because you're forwarding ports, the server is (correctly) sending back
Eric Pugh 
And cyberduck, not being very smart, is taking it at its word, and not noticing that that is not the ip address it connected to initially.
» ...and is not routable from where you are....
Eric Pugh 
Most ftp clients (incl the cmd line one) will try the ip address they know to be correct in the case of a private ip being returned in response to PORT.
Eric Pugh 
submitting bug to cyberduck
» fugu seems to do the same thing

Change History (2)

comment:1 Changed on Jan 18, 2007 at 3:01:02 PM by dkocher

  • Component changed from core to ftp
  • Description modified (diff)
  • Type changed from defect to enhancement

comment:2 Changed on Jul 2, 2007 at 6:34:30 PM by dkocher

  • Milestone set to 2.7.3
  • Resolution set to worksforme
  • Status changed from new to closed

Should be fixed as of 2.7.3

Note: See TracTickets for help on using tickets.