Hi, there's definitely some issue with the ftp-proxy since 3.4.26 -> 3.4.27. Seems like active ftp gets NAT'ed incorrectly, the ftp data port gets translated to port 0 *for some clients*.
I have run a few tests with various ftp clients, logging into 2 different servers and typing "ls" (so the data channel gets opened). With 3.4.27, some clients would apparently hang (ie not getting the data channel). When I do "ipnat -ls", I can see the hanging clients with their data channel mapped to port 0. MAP 192.168.45.13 1497 <- -> xxx.xx.218.3 1497 [yyy.yyy.63.64 0] MAP 192.168.45.13 1496 <- -> xxx.xx.218.3 1496 [yyy.yyy.63.64 21] Here's a summary of FTP clients working/failing (I've quickly tested this against 2 external FTP servers, results were identical): stock IRIX 6.5.x hangs stock sparc Solaris 8 ok SuSE Linux 7.3 (pasv) ok SuSE Linux 7.3 (actv) hangs stock MS Win2k WS hangs All tested FTP client machines are located in the same RFC1918 internal network - behind the firewall and getting NAT'ed / ftp-proxied. The firewall and NAT rules for the ipf box (incl ftp-proxy) are pretty standard, and have worked fine with 3.4.24 and before. The tested ipf box runs ipfilter 3.4.27 on OpenBSD 2.9 / i386. I have experimentally downed the tested ipf box to 3.4.26, and my primitive testing "connect, then ls" worked fine for all clients listed above [except Win2k not tested]. Looks like problems with active ftp, the IRIX and MS Win clients do this by default AFAIK. Newer Linux clients default to passive (works), but fail when forced to active ftp. I have not run a packet trace on the failing clients yet. Darren, let me know how we can help tracing this issue. ciao, chakl
