![](https://seccdn.libravatar.org/avatar/5e9a036e00cdd0d11139cfe5a3aa4e71.jpg?s=120&d=mm&r=g)
Sorry about the lag of this reply, I haven't checked my email in a couple of days. I have SuSE's ftp-proxy set up and running on my sort of firewall (It's got too much running on it to be a real firewall). To start off I set up my ftp server to run on a different port number than 21 (up in the 1024 and up range). I then used ipchains to block the servers new port and prevent connections directly to my ftp server. I then set up SuSE's ftp-proxy to listen on port 21 and proxy all the traffic to my ftp server's new port. I set it up this way this because my firewall is the only computer I have up and running 24/7, but it would be just as easy to have it proxy to another machine if that's what you desire. Although running an ftp server on my firewall is not the most secure thing to do, I feel a little more secure knowing the SuSE's ftp-proxy is there limiting the commands that ftp users are allowed, spoofing the server's identity, and hopefully protecting me against common ftp expoits. fj On 5 Jan, sworley@houston.rr.com wrote:
Hi,
Has anyone got SuSE's ftp-proxy working? If your setting it on a firewall machine what do you use for the DestinationAddress? The IP of the 2nd interface or one of the machines' IP's behind the firewall? I read the docs and they're not complete, especially the part on the config file.
TIA scott sworley@houston.rr.com
-- --> flaw@videotron.ca --> http://pages.infinit.net/fdesigns --> PGP Key found on site -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/