On Wed, 15 Aug 2001, Mike Smallwood wrote:
> I know this topic has come up many time before, but my situation seems to be
> unique and one that I can find no info on. So here's the deal:
> I'm running qpopper 4.03 inside NAT (with all the proper policies) on a
> redhat 7.1 system. It is a dev mail server that appears to be working fine
> with one exception (here's the tricky part.) When logging into port 110 of
> the machine via its outside NAT IP from anywhere on the *trusted* side
> (inside) of the firewall there is a 35 second delay before the Qpopper
> banner appears. When logging into port 110 of the machine via inside IP from
> anywhere on the *trusted* side (inside) there is no delay. From anywhere
> else outside the firewall, there is no delay. Telnetting in to any other
> port (like 21) has no delays from *anywhere*!
>
it's possible that xinetd is trying to reverse lookup, yes.
you said telnetting to port 21 i.e. ftp daemon, is fine, is the ftp daemon
run under xinetd? if so, are both the ftp daemon and qpopper bound to the
same interface, or to all interfaces?
i would take xinetd out of the equation firstly, by compiling and
running qpopper in standlone mode, and see if that fixes it.
-Tony
.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-.
Anthony J. Biacco Network Administrator/Engineer
[EMAIL PROTECTED] Intergrafix Internet Services
"Dream as if you'll live forever, live as if you'll die today"
http://www.asteroid-b612.org http://www.intergrafix.net
.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-.
