Configuring ftp clients for poorly configured servers..

[p0rnflake]

Someone please help me figure this one out...

In order for a ftp client to properly list the contents of a remote ftp server both the router/firewall at the server-end and at the client-end needs to be properly configured right ?

My problem is that I'm having problem listing contents on alot of ftp server - (using both active and passice ftp) - On me Windoze system using FlashFXP I've solved this by simple bind'ing my public IP to the ftp client (FlashFXP makes sure that any IP reported to the server is in fact my WAN IP and not my local PC IP as most client will do) - I've also set a fixed port range for flashfxp to use for data channels - these are forwarded in my firewall to my PC.

It's work with 99.99% of all ftp servers - the problem is AFAIK there's no linux ftp client capable of the same stunt. Neither gftp or IglooFTP pro lets you bind the IP or lock down the ports used for data channels :confused:

This is my LAST problem in my Windoze to Linux migration - please help me ;)

[superbnerd]

I am assuming you have a dynamic ip from your ISP. if this is true, you should get a domain name from dyndns. that way linux won't have to bind to a specific ip.

[p0rnflake]

I have a static IP from my ISP - and a NAT router between the linuxbox and the internet (otherwise there wounldn't be a problem in the first case)

Like I said the setup is working fine under windows where the client allows me to dictate which ports to use..

[jeru]

Why would you need to bind a FTP clients ip to the gateways/firewalls ip? PASV is a RPC generated port range defined and instanciated by the ftp server for the client to use.

FlashFXP isn't ftp. It encapsulates ftp as part of it's peering/remoting service as well as supports traditional ftp. But binding a client doesn't do anything for you unless it's FlashFXP on both ends.

Sounds like you have 2 things confused with each other. As with pure ftp, binding any of your ports to your public IP won't do a lick of difference under windows or linux if the server is configured wrong. All you can do is disable PASV and hope for the best. (with FlashFXP I believe what might have made it work for you is because you were remotely telling the other deamon to transfer to you, instead of you requesting transfers from it)

But I believe there are Linux FlashFXP alternatives. I saw some java application that supported it once, but don't remember anything about it. Just type FlashFXP in google using this;

http://www.google.com/linux

[p0rnflake]

FlashFXP isn't ftp. It encapsulates ftp as part of it's peering/remoting service as well as supports traditional ftp. But binding a client doesn't do anything for you unless it's FlashFXP on both ends.

FlashFXP is your avarage run of the mill ftp client - it's does not have a server part, so I cant follow you on the 'flashFXP on both ends part'

What FlashFXP does is that it's able to alter the packages sent through the ftp connection channel (default port 21 - but any port will do) and theirby fixing the problem with active ftp and NAT routers.

All I'm asking for is a linux client with the same functionality - the setup I described works, I can connet with active FTP to 99.99% of all ftp servers - without the FlashFXP setup I cant do a standard list command on most of them not even with passive ftp.


From the FlashFXP forums:


Q:
What exactly does the 'Bind local ports to this ip' and when do you use it ?
Does it can resolve fxp problem when it's behind a router nat/firewall ?

A:
When using PORT mode behind a router/firewall without NAT it will use your local IP which results in a failed connection.

By setting this option to your external IP address and configuring your router/firewall to forward a range of ports to your IP address you can over come this problem.

[p0rnflake]

Is everybody managing with gFTP ?? - there must be loads and loads of ftp servers that you cant use ??

[mark]

Is everybody managing with gFTP ?? - there must be loads and loads of ftp servers that you cant use ?? The only problem I've had with gFTP is "too many users" at the server end. It's worked quite nicely for me - and I also have a static IP address. I just plugged in my IP address, my ISP's gateway, primary and secondary DNS server addresses and away it went.