From owner-freebsd-isdn Tue Jan 4 9:20:21 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from mail.sparud.net (hinken.sparud.net [193.12.107.26]) by hub.freebsd.org (Postfix) with ESMTP id 9A1BD1518D for ; Tue, 4 Jan 2000 09:20:15 -0800 (PST) (envelope-from jan@sparud.net) Received: by mail.sparud.net (Postfix, from userid 10) id C0FA53E24; Tue, 4 Jan 2000 18:20:12 +0100 (CET) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14450.11211.664248.592583@hinken.sparud.net> Date: Tue, 4 Jan 2000 18:20:11 +0100 (CET) To: freebsd-isdn@freebsd.org Subject: Sigh, I'm caught by the LCP loop bug... X-Mailer: VM 6.75 under Emacs 20.3.1 From: jan@sparud.net (Jan Sparud) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi there! Last week I suddenly got caught by the infamous LCP loop bug. It appeared all of a sudden; I hadn't done any changes, nor had the ISP at work. After figuring out that I had the same problem as some others have had, I applied the patch that Marc van Woerkom posted to the list (subject: "Infinite loop (sppp/lcp)"). After that, I can connect alright, but it takes about ten seconds instead of the normal 1-2 seconds. Since I am about to install i4b on some ten boxes for colleagues at work, I'd thought it would be nice to kill this bug. I want BSD (I use NetBSD) to look as good as possible, and this ten second connect delay is then hard to explain. I use NetBSD-current (i386) and i4b-0.90. The ISDN card I'm using is the AVM Fritz! PCI card. Now to the problem. Below are transcripts from /var/log/messages (produced by the isp0 device after setting the debug flag), from isdntrace (on the same connection attempt), and from tcpdump* (from another connection attempt). *I have modified the print-ppp.c in the sppp directory to work with the NetBSD tcpdump. I can send patches if anyone is interested.