From owner-freebsd-isdn Wed Jan 12 3: 0: 6 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from nets5.rz.rwth-aachen.de (nets5.rz.RWTH-Aachen.DE [137.226.144.13]) by hub.freebsd.org (Postfix) with ESMTP id 51D14154CA for ; Wed, 12 Jan 2000 03:00:01 -0800 (PST) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: from campino.informatik.rwth-aachen.de (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by nets5.rz.rwth-aachen.de (8.9.1a/8.9.1/10) with ESMTP id MAA07248 for ; Wed, 12 Jan 2000 12:00:00 +0100 (MET) Received: from gil.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.30.2]) by campino.informatik.rwth-aachen.de (8.9.1a/8.9.1/3) with ESMTP id MAA01804 for ; Wed, 12 Jan 2000 12:00:10 +0100 (MET) Received: (from kuku@localhost) by gil.physik.rwth-aachen.de (8.9.3/8.6.9) id MAA98816 for freebsd-isdn@freebsd.org; Wed, 12 Jan 2000 12:00:03 +0100 (CET) Date: Wed, 12 Jan 2000 12:00:03 +0100 (CET) From: Christoph Kukulies Message-Id: <200001121100.MAA98816@gil.physik.rwth-aachen.de> To: freebsd-isdn@freebsd.org Subject: i4bisppp - timing when connecting Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org When I'm dialing out with i4bisppp (isp0) it takes a while until isdnd has dialed and set up the interface. It happens regularly that the upper layer times out with an error (either netscape cannot connect or ssh returns with an error saying it cannot connect or no route to host). Then I hear the beep and the next try after the beep succeeds. Is this necessary? I mean, is there a way to adjust some parameters that prolongs the timing out of the upper layer applications? -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message