On Thu, 11 Jan 2007, Ryan Corder wrote: > However, the 4.0 ftp-proxy and the 3.8 ftp-proxy don't seem to like > working with each other. When I attempt to ftp from the inside network > all the way out to the internet, I can get connected, but if I attempt > to do a transfer I receive a 'connection refused'. Here is the output > of 'ftp':
The old ftp-proxy is not transparent. It directs the data connections to and from the firewall itself, instead of the real endpoint FTP server. The new ftp-proxy does not accept that. (it behaves like a 'strict' ftp client itself). Workarounds are as follows - run old ftp-proxy on both 3.8 and 4.0 - run new ftp-proxy on both 3.8 and 4.0 - run old ftp-proxy with -n so that at least passive mode works An option for new ftp-proxy to accept data connections to another IP then that of the control connection is on my TODO... but that's it. -- Cam
