From owner-freebsd-stable Wed Apr 19 2:25: 4 2000 Delivered-To: freebsd-stable@freebsd.org Received: from storm.FreeBSD.org.uk (storm.freebsd.org.uk [194.242.139.170]) by hub.freebsd.org (Postfix) with ESMTP id D8CA337B95B for ; Wed, 19 Apr 2000 02:24:58 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (hak.nat.Awfulhak.org [172.31.0.12]) by storm.FreeBSD.org.uk (8.9.3/8.9.3) with ESMTP id KAA96752; Wed, 19 Apr 2000 10:24:56 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id IAA00473; Wed, 19 Apr 2000 08:33:29 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200004190733.IAA00473@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: William Denton Cc: stable@FreeBSD.ORG Subject: Re: Serial port problems with 4.0 In-Reply-To: Message from William Denton of "Tue, 18 Apr 2000 19:50:55 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 19 Apr 2000 08:33:29 +0100 From: Brian Somers Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 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