Hi! While trying to restrict the port range the ftp-proxy uses for PASV data connections, I noticed that apparently the listening port number does NOT get incremented. For example: fw1:~ # telnet ftpproxy1 ftp ... 220 ftpproxy1 FTP server (Version 1.7tp7 - 2001/06/20 21:05:20) ready. user username 331 Password required for username. pass ****** 230 User username logged in. pasv 227 Entering Passive Mode (a,b,c,d,porthigh,portlow) When doing this twice in a row (without first closing the connection or initiating a transfer!), the same port number (PassiveMinDataPort) will be used - and the second attempt will (of course) fail... ("TECH-ERR can't bind Cli-Data to a.b.c.d:41000-41999 for e.f.g.h (errno=98 [Address already in use])") "SockBindRand yes" fixes the problem (at least temporarily). Doesn't this look very much like the DestinationMinPort/ DestinationMaxPort bug mentioned a while ago? (BTW: has that one been fixed yet?) Bye, Martin
participants (1)
-
Martin Köhling