|
I had the same problem with the Direct Routing and SMTP and POP3. It
looked like a problem with the Ident lookup to the server by the client,
it was what always was occurring during that time out period. I saw
this while doing tcpdumps on the virtual server where the client would
just keep asking for Ident lookups to the Virtual IP address which are
from the client port 113 to a random port above 1023 on the virtual
server. I can see how this is tricky with the direct routing method
since this traffic should be sent on to the real server but is not. I
sort of gave up on Direct Routing for now since this looks pretty hard
to fix if it really is Ident and the client requirements getting in the
way.
Chris K
Ted Pavlic wrote:
>
> I'm connecting directly to the IP. But just to be sure, I'll add an entry to
> the nameserver for that particular IP -- in both forward and reverse
> lookups...........done.....
>
> And it still does the same thing. :(
>
> Understand that the thirty seconds are *AFTER* the connection... Telnet
> connects, gives me the escape character, and sits. If it was a nameservice
> thing, I'd imagine it'd sit before it connected.
>
> <?> I'd actually be happier if it wasn't connecting. :) Then I'd know there
> was definitely something I needed to fix between me and the real machine.
> But when it connects and THEN has trouble... I'm lost. :(
>
> All the best --
> Ted
>
> ----- Original Message -----
> From: Rob Thomas <rob@xxxxxxxxxx>
> To: Ted Pavlic <tpavlic_list@xxxxxxxxxxx>
> Cc: <linux-virtualserver@xxxxxxxxxxxx>
> Sent: Tuesday, June 29, 1999 5:40 PM
> Subject: Re: SMTP -- very slow connection
>
> > Ted Pavlic wrote:
> > >
> > > And it sits for about THIRTY seconds. Then, after thirty seconds...
> > >
> >
> > That sounds like a DNS lookup timing out to me..
> >
> > --Rob
> >
>
--
Chris Kennedy
I-Land Internet Services, Network Operations Center
ckennedy@xxxxxxxxx
(660) 829-4638 x 117
|
