[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: strange SSH behavior
See this is the thing -- in my case it WAS because of failed reverse
lookups (even though I turned that off). And normally I'd be ok with
that, except that the problem surfaced entirely on it's own accord, with
no configuration changes on my part on the client PC, firewall (SSH host),
or DNS server I was querying against. Everything was fine without a
reverse IP map to my 10.x.x.x system one day, the next this just started
happening for no good reason. And given that this SSH host has been
running for months to this point with no issue, that pretty much rules out
any DNS cache problems and what not.
What also is growing more and more weird by the day are that multiple
people are reporting this behavior all of a sudden, with the "It was
working and now it's not" description. It almost sounds like a software
bug but then again I can't think of any reason why this issue would just
suddenly surface. Putting my IP in /etc/hosts was a temp fix for my
problem, but what happens when I switch my internal LAN to DHCP? I have
to make an entry for each possible address? And it still doesn't explain
why the problem surfaced to begin with...
-rf
On Tue, 5 Mar 2002, Nick wrote:
> I am pretty sure that this is due to failing reverse name lookup. (I wont
> swear to it though :-) ) I have the same problem if I SSH to a BSD box from
> a unamed host. But If I do it from a host that has a valid name on the net,
> it connects very quickly.
>
>
> At 02:27 PM 3/5/2002 -0800, you wrote:
> >Leopold Bloom wrote:
> >
> >>On Mon, Mar 04, 2002 at 09:22:13PM -0600, Ricardo Londono wrote:
> >>
> >>>I have been running an OBSD 3.0 server for 3+ months now. I love it! But
> >>>lately for some strange reason when I use Putty to connect to the server via
> >>>SSH it takes a good long 2 minutes or so to authenticate me. I also believe
> >>>it's affecting FTP? This problem started about 1 week ago and I have
> >>>not done
> >>>anything. It authenticates eventually and works fine but takes a long time.
> >>>Before I would type password in and connect instantly.
> >>>
> >>>any ideas
> >
> >
> >The same has happened to me with 3.0 -stable. From one day to the next;
> >POOF, it takes anywhere from seconds up to 1 minute to log into the machine. :|
>
> --
> Vides Credendo!
> Nick Gray
> Senior Network Engineer
> Bruzenak inc.
> nagray@bruzenak.com