ml> the key to passive FTP is that the server tells the client what ports to   
   ml> use for the connection... then the client makes a new connection for the   
   ml> transfer using those ports... this is the opposite to "active" FTP in   
   ml> which the server uses the existing connection for one part of the   
   ml> transfer and opens the other port for the actual transfer...   
      
   You hit the nail on the head right there, Mark. Over here I'm running the   
   Synchronet FTP server on port 21, and it works, so I can only guess that   
   Synchronet takes care of the passive side of things. OTOH, I run PureFTPd   
   to handle any FTN related downlinks that would rather write up a script   
   that runs lftp or something similar to pick up their packets, instead of   
   using a binkp server. That's on port 2121, and requires (and suggests) to   
   open a port range at high numbers to handle passive connections. Here I use   
   20000-20005, which I believe was recommended by the documentation of the   
   software itself.   
      
   I know you don't have to open many ports for passive mode as long as you're   
   able to specify them in the software you're using, and if memory serves me   
   right, they don't actually listen, but yet take redirection from the active   
   port when a passive connection is determined.   
      
   --- Mystic BBS v1.10 A20 (Linux)   
    * Origin: thePharcyde_ http://www.pharcyde.org (Wisconsin) (1:154/10.1)