No replies yet, but TIA. PROBLEM Solaris ftpd/in.ftpd doesn't allow explicit specification of which passive ftp data ports it uses. Intermittent ftp problems insue. It works for me and not them. Then they are ok and I'm not, etc. Our range of ports was too narrow to account for ftpd's fluid allocation of ports, so during testing things worked, during production they got randomnly flakey, and then things flat out broke. SOLUTION This can be fixed one of two ways: (1.) Allow a big range of ports, but this defeats the purpose of firewalling to some degree. (2.) Use a ftpd that allows explicit specification of ports, i.e. WU-ftpd or proftpd, etc. Joseph P Frazee frazee.23@osu.edu On 14 Aug 2001 18:08:55 -0400, Joseph P Frazee wrote: > So, > > new job == inheriting bunches of stuff == ugh! > > OpenBSD ipfilter firewall with these rules: > > pass in proto tcp from 128.146.0.0/16 to any port = ftp > pass in proto tcp from 140.254.0.0/16 to any port = ftp > pass in proto tcp from any to any port 41952 >< 65535 > pass in proto tcp from any to any port = 65535 > pass in proto tcp from any to any port = ftp keep state > > Running in.ftpd via inetd == bad I know, but its what we have at the > moment. > > FTP's are timing out right and left. > > Is the problem running ftp from inetd. I have never done that as I know > it isn't a performance enhancer per se ;) Or is it the firewall. > > Thanks, > > > Joseph P Frazee > frazee.23@osu.edu > > _______________________________________________ > sunmanagers mailing list > sunmanagers@sunmanagers.org > http://www.sunmanagers.org/mailman/listinfo/sunmanagers >Received on Wed Aug 15 17:01:39 2001
This archive was generated by hypermail 2.1.8 : Wed Mar 23 2016 - 16:25:01 EDT