/* HINT: Search archives @ http://www.indyramp.com/masq/ before posting! /* ALSO: Don't quote this header. It makes you look lame :-) */ > Guess what happens when the client and server are both behind a NAT > firewall? > > There is a solution to the problem, though. You can hack the FTP server > to accept it's IP as a command line argument, rather than discovering the > IP itself. Then, you'd have to use SNMP (or something) to determine the > public IP that your DSL router has, and pass it as a command line argument > to the FTP server when it's started up. I thought about doing that a > while back, but never got around to it. >Anyone ever done this? I did and the solution is very simple. NAT kicks the ftp-masq-module cos the interarction is far too complicated. so why not simply store and forward the whole traffic? you need an ftp-proxy like jftpgw (freshmeat.net) the problematic part about NAT is the translation. if you place the proxy on the NAT-machine (linux for example), your NAT-ed clients can connect to the proxy which sits on a machine with a real ip. it functions just like a squid-proxy.... just for FTP. set it up and your problems will vanish. when I sell regular NAT-firewalls on linux-base it got a standard to install it. if you got problems to set it up, contact me on [EMAIL PROTECTED] marcus _______________________________________________ Masq maillist - [EMAIL PROTECTED] Admin requests can be handled at http://www.indyramp.com/masq-list/ -- THIS INCLUDES UNSUBSCRIBING! or email to [EMAIL PROTECTED] PLEASE read the HOWTO and search the archives before posting. You can start your search at http://www.indyramp.com/masq/ Please keep general linux/unix/pc/internet questions off the list.
