Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 19 Apr 2000 08:33:29 +0100
From:      Brian Somers <brian@Awfulhak.org>
To:        William Denton <buff@pobox.com>
Cc:        stable@FreeBSD.ORG
Subject:   Re: Serial port problems with 4.0 
Message-ID:  <200004190733.IAA00473@hak.lan.Awfulhak.org>
In-Reply-To: Message from William Denton <buff@pobox.com>  of "Tue, 18 Apr 2000 19:50:55 EDT." <Pine.BSF.4.21.0004181927290.14156-100000@odin.egate.net> 

next in thread | previous in thread | raw e-mail | index | archive | help
I think there's something peculiar happening here - casting a quick 
eye at datalink.h, I've got the DATALINK_CARRIER and DATALINK_LOGIN 
states before the DATALINK_READY state.  DATALINK_READY is what you 
get when you ``term'', but it's possible that it's getting jammed 
waiting for carrier first :-(

  $ ppp
  Working in interactive mode
  Using interface: tun0
  ppp ON hak> set device "!telnet localhost"
  ppp ON hak> set log local phase
  ppp ON hak> term
  Phase: bundle: Establish
  Phase: deflink: closed -> opening
  Phase: deflink: Connected!
  deflink: Entering terminal mode on !telnet localhost
  Type `~?' for help
  Phase: deflink: opening -> carrier
  Phase: deflink: carrier -> ready
  Trying ::1...
               Connected to localhost.
                                      Escape character is '^]'.

  FreeBSD/i386 (hak.lan.Awfulhak.org) (ttyp2)

  login: 

I suspect on a real tty, this will have problems after ``opening -> 
carrier'' !  Does ``set cd off'' make any difference ?  If it does, 
that's a bug.


> On 13 April 2000, Marcin Cieslak wrote:
> 
> : Most ISPs today don't use a traditinal login "terminal" login scheme,
> : they instead allow ppp to put LCP packets on the wire and verify
> : authentication using PAP or CHAP instead.
> : 
> : I usually dial up manually, using "term" command and "ATDT" Hayes
> : string and see if login prompt is really "login:" or perhaps
> : "username:" or something else.
> 
> Using terminal mode with 4.0 on the box, I can connect to the ISP, it says
> CONNECT 115200, then nothing.  When 3.4 was on the box, and with the
> machine I'm on now (still 3.4 until I get this PPP thing figured out), I
> get the old-fashioned login: prompt.  So it seems there's something about
> 4.0-RELEASE and ppp on this machine that's causing PPP to freeze up early
> on so that the login prompt never arrives.  The racks do give up the
> prompt.
> 
> I checked out the FAQ, and took its advice on recompiling ppp with a
> couple of added options so I could run the debugger on it.  Doing a stack
> trace when it was sitting waiting, I got this:
> 
> #0  0x281c1c50 in select () from /usr/lib/libc.so.4
> #1  0x8068e71 in DoLoop (bundle=0x808a7e0) at main.c:534
> #2  0x8068d83 in main (argc=1, argv=0xbfbffbdc) at main.c:492
> #3  0x804af59 in _start ()
> 
> What's going on in usr.sbin/ppp/main.c is beyond me, though.
> 
> Bill
> -- 
> William Denton : Toronto, Canada : http://www.miskatonic.org/ : Caveat lector.

-- 
Brian <brian@Awfulhak.org>                        <brian@[uk.]FreeBSD.org>
      <http://www.Awfulhak.org>;                   <brian@[uk.]OpenBSD.org>
Don't _EVER_ lose your sense of humour !




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200004190733.IAA00473>