> > > 1) For active FTP to work, I noticed I have to specify the back-end > > > network, as well as the address of the server itself. I mean this most > > > elegant syntax > > > > > > map em1 0/0 -> 0/32 proxy port ftp ftp/tcp > > > > > > is supposed to work if I understood the FAQ correctly, but is does not. > > > This only works for FTP traffic originating from the firewall itself, > but > > > not for hosts behind it. Instead I have to use this: > > > > > > map em1 <extip>/32 -> 0/32 proxy port ftp ftp/tcp > > > map em1 192.168.2.0/24 -> 0/32 proxy port ftp ftp/tcp > > > > That is weird. I think map em1 0/0 -> 0/32 proxy port ftp ftp/tcp > > should have worked. What do you see with ipnat -lv when you try to ftp > > out? > > > > -Guido
For outbound active FTP with no NAT, I have been using 0/0 -> 0/0 successfully for years. With NAT (for FTP only), I earlier used 0/0 -> NATtedIP/32 instead.
