From owner-freebsd-isdn  Sun Aug  2 02:36:00 1998
Return-Path: <owner-freebsd-isdn@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id CAA18446
          for freebsd-isdn-outgoing; Sun, 2 Aug 1998 02:36:00 -0700 (PDT)
          (envelope-from owner-freebsd-isdn@FreeBSD.ORG)
Received: from linteuto.teuto.de (linteuto.teuto.de [194.77.23.26])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA18441
          for <freebsd-isdn@FreeBSD.ORG>; Sun, 2 Aug 1998 02:35:56 -0700 (PDT)
          (envelope-from martin@rumolt.teuto.de)
Received: from rumolt.teuto.de (root@rumolt.teuto.de [194.77.23.161])
	by linteuto.teuto.de (8.8.7/8.8.7) with ESMTP id LAA08430;
	Sun, 2 Aug 1998 11:35:41 +0200
Received: (from martin@localhost)
	by rumolt.teuto.de (8.8.8/8.8.7) id LAA02461;
	Sun, 2 Aug 1998 11:07:37 +0200 (MEST)
From: Martin Husemann <martin@rumolt.teuto.de>
Message-Id: <199808020907.LAA02461@rumolt.teuto.de>
Subject: Re: Tracing Kernel code (isppp) & possible isdnd bug
To: marc@bowtie.nl
Date: Sun, 2 Aug 1998 11:07:36 +0200 (MEST)
Cc: hm@hcs.de, freebsd-isdn@FreeBSD.ORG
In-Reply-To: <199808010825.KAA17791@bowtie.nl> from "Marc van Kempen" at Aug 1, 98 10:25:17 am
Organization: Crusaders Catering Services Inc.
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-isdn@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> This sounds an awful lot like my problem, I was just going to ask here how to
> trace a problem like this. I'll include my sppp debug output for starters,
[..]
> Aug  1 10:01:05 schopenhauer /kernel: isppp0: phase network
> Aug  1 10:01:05 schopenhauer /kernel: isppp0: ipcp open(stopped)
> Aug  1 10:01:05 schopenhauer /kernel: isppp0: lcp close(opened)
> Aug  1 10:01:05 schopenhauer /kernel: isppp0: phase terminate
> Aug  1 10:01:05 schopenhauer /kernel: isppp0: lcp output <term-req id=0x32 len=4>
> Aug  1 10:01:05 schopenhauer /kernel: isppp0: lcp input(closing): <term-ack id=0x2 len=4>
> Aug  1 10:01:05 schopenhauer /kernel: isppp0: phase dead
> Aug  1 10:01:05 schopenhauer /kernel: isppp0: lcp down(closed)
> Aug  1 10:01:05 schopenhauer /kernel: isppp0: Down event (carrier loss)                                       

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...


Martin

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