From owner-freebsd-isdn Wed Jan 5 0: 3:48 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with SMTP id 06CAF14BF6 for ; Wed, 5 Jan 2000 00:03:42 -0800 (PST) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (2405 bytes) by hcshh.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Wed, 5 Jan 2000 09:03:41 +0100 (CET) (Smail-3.2.0.104 1998-Nov-20 #1 built 1998-Dec-11) Received: by hcswork.hcs.de (Postfix, from userid 200) id 6287E4829; Wed, 5 Jan 2000 09:03:35 +0100 (MET) Subject: Re: Sigh, I'm caught by the LCP loop bug... In-Reply-To: <14450.11211.664248.592583@hinken.sparud.net> from Jan Sparud at "Jan 4, 0 06:20:11 pm" To: jan@sparud.net (Jan Sparud) Date: Wed, 5 Jan 2000 09:03:35 +0100 (MET) Cc: freebsd-isdn@FreeBSD.ORG Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1552 Message-Id: <20000105080335.6287E4829@hcswork.hcs.de> From: hm@hcs.de (Hellmuth Michaelis) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From the keyboard of Jan Sparud: > Last week I suddenly got caught by the infamous LCP loop bug. [...] > So, can any of you reading the list shed any light on what is > happening when the loop occurs? I really want to fix this > problem. From what I understand, none of the developers have > experienced this problem, and that's why it hasn't been fixed. I'll > try to fix the problem myself, but it would be good if some of you > ISDN experts could have a look at the logs below, to see if something > obvious is wrong. The problem is completely reproducible here, so if > other information is needed, please ask. Just some remarks: - i don't use PPP in any of my i4b setups (yet), i only use it for testing this and that. In my test setups, i cannot reproduce this bug. - i have no idea when this occurs or what might be the cause. - the ISDN parts of i4b seem to have nothing to do with this bug, it seems to be a failure inside either i4b_isppp.c or if_spppsubr.c or both. IMHO, what you are trying to do is the only way to solve this problem, as someone who is _able_ to reproduce the problem should become a PPP expert, understand why what is happening and then fix the problem in the best possible way. hellmuth -- Hellmuth Michaelis Tel +49 40 559747-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 559747-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de 22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message