From owner-freebsd-isp Wed Dec 2 15:19:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA18293 for freebsd-isp-outgoing; Wed, 2 Dec 1998 15:19:31 -0800 (PST) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from gina.swimsuit.internet.dk (mail.swimsuit.internet.dk [194.255.12.232]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA18279 for ; Wed, 2 Dec 1998 15:19:26 -0800 (PST) (envelope-from leifn@swimsuit.internet.dk) Received: from localhost (localhost.swimsuit.internet.dk [127.0.0.1]) by gina.swimsuit.internet.dk (8.9.1/8.9.1) with ESMTP id AAA03403; Thu, 3 Dec 1998 00:18:36 +0100 (CET) (envelope-from leifn@swimsuit.internet.dk) Date: Thu, 3 Dec 1998 00:18:36 +0100 (CET) From: Leif Neland To: Brian Somers cc: freebsd-isp@FreeBSD.ORG Subject: unknown protocol, was: freebsd-current: user-ppp broken since a few days ago? In-Reply-To: <199812022223.WAA17289@dev.lan.awfulhak.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 2 Dec 1998, Brian Somers wrote: > > > > > > 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: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 > > > > 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.... > Sorry to spin off, but as it works most of the time on the machine, both from windows and FreeBSD, could it mean that one of the ports on the Livingston Portmaster is configured not to use tcp? > 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 > > -- > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message