Date: Mon, 7 Feb 2000 18:46:34 +0100 (CET) From: Christoph Kukulies <kuku@gilberto.physik.RWTH-Aachen.DE> To: freebsd-isdn@freebsd.org Subject: synchronized Message-ID: <200002071746.SAA47282@gil.physik.rwth-aachen.de>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200002071746.SAA47282>