From owner-freebsd-isdn Sun Aug 2 02:56:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA20051 for freebsd-isdn-outgoing; Sun, 2 Aug 1998 02:56:33 -0700 (PDT) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from news.IAEhv.nl (news.IAEhv.nl [194.151.64.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA20046 for ; Sun, 2 Aug 1998 02:56:30 -0700 (PDT) (envelope-from marc@bowtie.nl) Received: from LOCAL (uucp@localhost) by news.IAEhv.nl (8.8.8/1.63) with IAEhv.nl; pid 9519 on Sun, 2 Aug 1998 09:56:21 GMT; id JAA09519 efrom: marc@bowtie.nl; eto: UNKNOWN Received: from localhost (localhost [127.0.0.1]) by bowtie.nl (8.8.8/8.8.8) with ESMTP id LAA22639; Sun, 2 Aug 1998 11:51:42 +0200 (CEST) (envelope-from marc@bowtie.nl) Message-Id: <199808020951.LAA22639@bowtie.nl> To: Martin Husemann Cc: freebsd-isdn@FreeBSD.ORG Subject: Re: Tracing Kernel code (isppp) & possible isdnd bug In-reply-to: martin's message of Sun, 02 Aug 1998 11:07:36 +0200. <199808020907.LAA02461@rumolt.teuto.de> Reply-to: marc@bowtie.nl Date: Sun, 02 Aug 1998 11:51:41 +0200 From: Marc van Kempen Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [..] > > >This is no ISDN level bug. The connection is coming up, but the lcp state >machine decides to go to state "close" when ipcp goes to "open". This is >wrong. The rest shows the normal way of disconnecting after lcp enters "close" >state. So: the bug is on our side (there is no "lcp input..." logged that >would cause a change to "close"), and it's not in the ISDN related stuff. > >Looks like an isppp bug to me. Time to hunt... > If you need more specific debug info, just tell me what to do when it occurs again. Marc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message