From owner-freebsd-questions Fri Jun 8 8:57:14 2001 Delivered-To: freebsd-questions@freebsd.org Received: from prox.centtech.com (moat2.centtech.com [206.196.95.21]) by hub.freebsd.org (Postfix) with ESMTP id F3EB137B408 for ; Fri, 8 Jun 2001 08:57:05 -0700 (PDT) (envelope-from anderson@centtech.com) Received: (from smap@localhost) by prox.centtech.com (8.9.3+Sun/8.9.3) id KAA18892; Fri, 8 Jun 2001 10:57:01 -0500 (CDT) Received: from sprint.centtech.com(10.177.173.31) by prox via smap (V2.1+anti-relay+anti-spam) id xma018884; Fri, 8 Jun 01 10:56:34 -0500 Received: from centtech.com (proton [10.177.173.77]) by sprint.centtech.com (8.9.3+Sun/8.9.3) with ESMTP id KAA10175; Fri, 8 Jun 2001 10:56:33 -0500 (CDT) Message-ID: <3B20F5B2.D0ADE31@centtech.com> Date: Fri, 08 Jun 2001 10:56:34 -0500 From: Eric Anderson Reply-To: anderson@centtech.com Organization: Centaur Technology X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.14-5.0smp i686) X-Accept-Language: en MIME-Version: 1.0 To: Scott Stoddard Cc: questions@freebsd.org Subject: Re: Delay bringing up telnet window References: <001001c0f033$155a1f40$671bd240@phx.api.gblx.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG That is most likely the problem. The patch won't work for that.. I'm not sure it was intended to fix this problem (for OpenSSH only of course) in the first place, it just did for my machines (about 10). Eric Scott Stoddard wrote: > > Ahhhh, hmmm would that have anything to do with the fact that I have a /29 > block from my isp and run my own dns (forwards)?? I know that I must setup > my reverses on my providers DNS machines for them to work right(I am > guessing that is because the block is not actually swipped or delegated to > me - just lent to me). Will the freebsd patch possibly work around this? > Thanx! > > --Scott > > "I hear and I forget. I see and I remember. > I do and I understand." -Confucius > > -----Original Message----- > From: anderson@centtech.com [mailto:anderson@centtech.com] > Sent: Friday, June 08, 2001 8:30 AM > To: Scott Stoddard > Cc: questions@freebsd.org > Subject: Re: Delay bringing up telnet window > > It's the remote side's reverse lookup that's causing it. When you > connect, it trys to do a reverse lookup on your IP, and times out. In > some cases with FreeBSD 4.2 and OpenSSH, you need to apply a patch (came > out several months ago), that seems to fix a similar problem. > > Eric Anderson > > Scott Stoddard wrote: > > > > I have this exact same problem, on free bsd and other linux > distributions I > > have run (redhat, slackware). It drives me nuts... I have had many people > > say it is due to dns but I am ssh'ing by IP (same problem by telnet) I am > > using a Petium 120... the wait is like 30-45 seconds before I get a login > > promp! Once logged in the rest of the seesion runs great... > > > > --Scott > > > > "I hear and I forget. I see and I remember. > > I do and I understand." -Confucius > > > > Date: Thu, 07 Jun 2001 14:56:08 -0700 > > From: Drew Tomlinson > > Subject: RE: Delay bringing up telnet window > > > > > -----Original Message----- > > > From: Bill Moran [mailto:wmoran@iowna.com] > > > Sent: Thursday, June 07, 2001 11:59 AM > > > To: Steve Leibel > > > Cc: freebsd-questions@FreeBSD.ORG > > > Subject: Re: Delay bringing up telnet window > > > > > > > > > Steve Leibel wrote: > > > > > > > > I've got this weird problem, maybe somebody can help. > > > > > > > > I run FreeBSD on a Pentium-133 on a local network along with my Mac. > > > > When I run my Mac telnet client and request a session on the FreeBSD > > > > box, the window comes up right away but there is usually a 20 or 30 > > > > second delay before I get a login prompt. > > > > > > > > In the past I've seen the problem where AFTER I enter my userid and > > > > password there is a long delay. But that's generally > > > caused by a DNS > > > > problem. That's not the problem I'm having. > > > > > > > > In my case, the login prompt itself takes a long time to come up. > > > > > > Interesting ... because any time I've seen the aforementioned DNS > > > problem, it's occurred before the login prompt. > > > > Bill - > > > > You are correct. DNS only comes into play when you connect via a > > hostname and the hostname needs to be resolved to an IP address. Once > > the login prompt is reached, this step has been completed. > > > > Steve - > > > > Try to connect using the IP address instead of the hostname. If there's > > no delay using the IP address, then you have a DNS issue. If there is a > > delay, then it's something else, possibly a routing problem. > > > > Good luck, > > > > Drew > > > > > Can you do a reverse lookup on the machine you're logging in from? For > > > example, if you login in from 192.168.0.7, once you're logged in, try > > > "nslookup 192.168.0.7" and see if you get a timeout. > > > > > > -Bill > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-questions" in the body of the message > > -- > ---------------------------------------------------------------------------- > --- > Eric Anderson anderson@centtech.com Centaur Technology (512) > 418-5792 > For every complex problem, there is a solution that is simple, neat, and > wrong. > ---------------------------------------------------------------------------- > --- -- ------------------------------------------------------------------------------- Eric Anderson anderson@centtech.com Centaur Technology (512) 418-5792 For every complex problem, there is a solution that is simple, neat, and wrong. ------------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message