From owner-freebsd-current Wed Dec 2 14:47:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA14944 for freebsd-current-outgoing; Wed, 2 Dec 1998 14:47:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA14938 for ; Wed, 2 Dec 1998 14:47:54 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from dev.lan.awfulhak.org (dev.lan.awfulhak.org [172.16.0.5]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id WAA00205; Wed, 2 Dec 1998 22:23:20 GMT (envelope-from brian@Awfulhak.org) Received: from dev.lan.awfulhak.org (localhost [127.0.0.1]) by dev.lan.awfulhak.org (8.9.1/8.9.1) with ESMTP id WAA17289; Wed, 2 Dec 1998 22:23:19 GMT (envelope-from brian@dev.lan.awfulhak.org) Message-Id: <199812022223.WAA17289@dev.lan.awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Leif Neland cc: Brian Somers , freebsd-current@FreeBSD.ORG Subject: Re: user-ppp broken since a few days ago? In-reply-to: Your message of "Sat, 28 Nov 1998 22:23:34 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Dec 1998 22:23:19 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > On Fri, 27 Nov 1998, Brian Somers wrote: > > > Hi, > > > > What happens if you ``set openmode active 2'' ? > > > > Also, you may want to enable async logging to see what that initial > > data is - 0801 doesn't make much sense (is this consistent?). > > > > Nov 28 22:14:42 gina ppp[11867]: tun0: Chat: deflink: Dial attempt 1 of 1 > Nov 28 22:14:42 gina ppp[11867]: tun0: Chat: Send: AT^M > Nov 28 22:14:42 gina ppp[11867]: tun0: Chat: Expect(5): OK > Nov 28 22:14:42 gina ppp[11867]: tun0: Chat: Received: AT^M^M > Nov 28 22:14:42 gina ppp[11867]: tun0: Chat: Received: OK^M > Nov 28 22:14:42 gina ppp[11867]: tun0: Chat: Send: ATE1Q0^M > Nov 28 22:14:42 gina ppp[11867]: tun0: Chat: Expect(5): OK > Nov 28 22:14:42 gina ppp[11867]: tun0: Chat: Received: ATE1Q0^M^M > Nov 28 22:14:42 gina ppp[11867]: tun0: Chat: Received: OK^M > Nov 28 22:14:42 gina ppp[11867]: tun0: Chat: Send: ATDI1001-xxxxxxxx^M > Nov 28 22:14:47 gina ppp[11867]: tun0: Chat: Expect(40): CONNECT > Nov 28 22:14:47 gina ppp[11867]: tun0: Chat: Received: ATDI1001-xxxxxxxx^M^M > Nov 28 22:14:47 gina ppp[11867]: tun0: Chat: Received: CONNECT 115200/PPP 64000/NONE^M > Nov 28 22:14:47 gina ppp[11867]: tun0: Phase: deflink: dial -> login > Nov 28 22:14:47 gina ppp[11867]: tun0: Phase: deflink: login -> lcp > Nov 28 22:14:47 gina ppp[11867]: tun0: LCP: FSM: Using "deflink" as a transport > Nov 28 22:14:47 gina ppp[11867]: tun0: LCP: deflink: State change Initial --> Closed > Nov 28 22:14:47 gina ppp[11867]: tun0: Phase: deflink: Entering STOPPED state for 2 seconds > Nov 28 22:14:47 gina ppp[11867]: tun0: LCP: deflink: State change Closed --> Stopped > Nov 28 22:14:48 gina ppp[11867]: tun0: Async: ReadFromModem > Nov 28 22:14:48 gina ppp[11867]: tun0: Async: 7e 7d 28 7d 21 7f a6 92 7e > Nov 28 22:14:48 gina ppp[11867]: tun0: Phase: Unknown protocol 0x0801 (unrecognised protocol) > Nov 28 22:14:48 gina ppp[11867]: tun0: LCP: deflink: SendProtocolRej(1) state = Stopped > Nov 28 22:14:48 gina ppp[11867]: tun0: Async: WriteModem > Nov 28 22:14:48 gina ppp[11867]: tun0: Async: 7e ff 7d 23 c0 21 7d 28 7d 21 7d 20 7d 27 7d 28 > Nov 28 22:14:48 gina ppp[11867]: tun0: Async: 7d 21 7f 57 67 7e > Nov 28 22:14:49 gina ppp[11867]: tun0: Async: ReadFromModem > Nov 28 22:14:49 gina ppp[11867]: tun0: Async: 0d 0a 4e 4f 20 43 41 52 52 49 45 52 0d 0a > Nov 28 22:14:49 gina ppp[11867]: tun0: Phase: deflink: Carrier lost > Nov 28 22:14:49 gina ppp[11867]: tun0: LCP: deflink: State change Stopped --> Closed > > Unknown protocol? Is that the same as the windows message "Dialup network > couldn't find a supported protocol. Check the servertype settings and the > settings in control panel" ? > Sometimes I and clients get this message when calling by isdn to the > portmaster 2e. It's roughly the same thing. Ppp sends configure requests for each supported protocol. If the peer doesn't support that protocol, it'll reject it. If all protocols are rejected, windows will give you this message. I would think that most of the time this means that they haven't configured a TCP stack on their machine.... The above log shows that the remote end hangs up (the line above ``Carrier lost'' says ``\r\nNO CARRIER\r\n''). This looks like a result of us rejecting whatever 0x0801 is - probably NetBUI or something like that :-/ > Leif Neland -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message