From owner-freebsd-isdn Mon Feb 7 11: 1:54 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from nets5.rz.rwth-aachen.de (nets5.rz.RWTH-Aachen.DE [137.226.144.13]) by builder.freebsd.org (Postfix) with ESMTP id 2F1B541D1 for ; Mon, 7 Feb 2000 11:01:37 -0800 (PST) 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 SAA06965 for ; Mon, 7 Feb 2000 18:46:28 +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 SAA26398 for ; Mon, 7 Feb 2000 18:46:57 +0100 (MET) Received: (from kuku@localhost) by gil.physik.rwth-aachen.de (8.9.3/8.6.9) id SAA47282 for freebsd-isdn@freebsd.org; Mon, 7 Feb 2000 18:46:34 +0100 (CET) Date: Mon, 7 Feb 2000 18:46:34 +0100 (CET) From: Christoph Kukulies Message-Id: <200002071746.SAA47282@gil.physik.rwth-aachen.de> To: freebsd-isdn@freebsd.org Subject: synchronized Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ack, I thought the overinstall.sh script would also copy the i4b userland stuff into /usr/src/usr.sbin and I was always compiling/installing from there wondering why my kernel isdnd version went up and up and my userland version stayed at 80. Now I'm synchronized to i4b-00.90.00, 3.4 RELEASE and isdnd stays up now. You may know that I mentioned that our campus provider (university computing center) ceased the fixed (raw ip) connection for a while (they will probably resurrect it) but for now I'm bound to use this weird sppp access (by means of i4bisppp). One ugly thing is the following: The university accepts every ISDN call since they have a far larger number of free incoming ISDN connections than they have free Acend router simultaneous connection 'slots'. Now what happens on my side when they are busy with their ascend router, is that isdnd dials in, doesn't get a route and the line is dropped again. Now, isdnd is sturdy, it dials again as soon as he can and everyone can imagine that this way my charges can pile up to an extent that is only limited by the number of seconds until I finally get in, so to say, a minute has 60 seconds, isdnd redials every third second so I get 20 units charged per minute (!). Odd, isdn't it? What can I do against this behaviour? -- 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