From owner-freebsd-isdn Thu Jan 6 0:29:25 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from mail-in-02.piro.net (mail-out-01.piro.net [194.64.31.11]) by hub.freebsd.org (Postfix) with ESMTP id F066615558 for ; Thu, 6 Jan 2000 00:29:22 -0800 (PST) (envelope-from pherman@piro.net) Received: from pums01.piro.net (pums01.piro.net [194.64.31.19]) by mail-in-02.piro.net (8.9.3/8.9.3/PN-991208) with ESMTP id JAA22521 for ; Thu, 6 Jan 2000 09:29:21 +0100 Received: from xhost.piro.net ([195.135.190.64]) by pums01.piro.net (Netscape Messaging Server 3.6) with ESMTP id AAA649; Thu, 6 Jan 2000 09:29:20 +0100 Date: Thu, 6 Jan 2000 09:29:20 +0100 (CET) From: Paul Herman To: David Wetzel Cc: ISDN-List Subject: Re: why does this take that long? In-Reply-To: <200001060018.BAA00489@cat.turbocat.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello David, On Thu, 6 Jan 2000, David Wetzel wrote: > This is an dailin from my box to my isp. > > Why is this *much* slower than with t-offline until the connection is established? > > [...isdnd debug output...] This looks amazingly like the LCP Loop Bug, but you seem to have it in the IPCP phase. This isn't surprising, because the same mechanism is used in both phases, but it might indeed be something else. The LCP Loop bug also depends on the provider. It may even depend on the Cisco IOS version of the terminal server, but that theory hasn't yet been tested thoroughly. The LCP bug is being worked on, and if you are interested in testing the bug fixes when we have them, just let me know. The LCP bugfix, when it comes, may or may not solve your problem. -Paul. ---------------------------------------------------- PIRONET AG Paul Herman - Consultant - SBU Providing Im Mediapark 5 - 50670 Cologne - Germany Tel.: +49 (0)221 454 3832 - Fax: +49 (0)221 454 3810 mailto:pherman@piro.net - http://www.piro.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message