From owner-freebsd-isdn Wed Jun 3 13:45:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA28438 for freebsd-isdn-outgoing; Wed, 3 Jun 1998 13:45:55 -0700 (PDT) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from peedub.muc.de (newpc.muc.ditec.de [194.120.126.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA28409 for ; Wed, 3 Jun 1998 13:45:39 -0700 (PDT) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.8.8/8.6.9) with ESMTP id WAA20581 for ; Wed, 3 Jun 1998 22:45:39 +0200 (CEST) Message-Id: <199806032045.WAA20581@peedub.muc.de> X-Mailer: exmh version 2.0.1 12/23/97 To: freebsd-isdn@FreeBSD.ORG Subject: Re: Problem oder normal ? Reply-To: Gary Jennejohn In-reply-to: Your message of "Wed, 03 Jun 1998 10:12:39 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 03 Jun 1998 22:45:38 +0200 From: Gary Jennejohn Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hellmuth Michaelis writes: >>From the keyboard of Gary Jennejohn: > >> >> some minutes ago, when I was closing my open internet-connetion, I got >> >> a somhow strage looking message from the FreeBSD (2.2.5) kernel >> >> ("i4b-L3-next_l3state").I don't know if this is a problem. >> > >> >This is an indication of a problem. The isppp driver instructs layer 4 >> >to disconnect 2 times which is not appropriate. Perhaps Gary or Joerg >> >know more why this happens. >> >> that was my first thought when I saw this report. I took a quick look >> at the code (both i4b_isppp.c and if_spppsubr.c) but didn't see anything >> obvious. > >I did not look at i4b_isppp.c and if_spppsubr.c but at the layer 3 fsm. The >bug report says, that the layer 3 is already in the disconnect state and >gets a second EV_DISCRQ. > >A workaround were to ignore the second EV_DISCRQ in l3, but according to >Q.931 (03/93) it is illegal to do that. > my first suspicion was that something changed in the sppp related code so that it was doing 2 disconnects istead of only 1. This was the situation in the early days before I noticed it and fixed it :-) Anyway, I've done some testing with isppp including doing ``ifconfig down'' and haven't seen any errors. The one thing I didn't try was hanging up using isdnd. I also have not seen any problems with automatic hangups using isppp. The kernel time outs work just fine and the connection is closed just like it's supposed to be. --- Gary Jennejohn Home - garyj@muc.de Work - garyj@fkr.dec.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message