From owner-freebsd-isdn Wed Apr 7 14: 5:27 1999 Delivered-To: freebsd-isdn@freebsd.org Received: from custos.callcenter.systemhaus.net (unknown [62.152.9.34]) by hub.freebsd.org (Postfix) with ESMTP id 565FE14CFD for ; Wed, 7 Apr 1999 14:05:06 -0700 (PDT) (envelope-from listmail@helena.callcenter.systemhaus.net) Received: (from smap@localhost) by custos.callcenter.systemhaus.net (8.8.5/8.8.5) id XAA03151 for ; Wed, 7 Apr 1999 23:03:06 +0200 (CEST) Received: from helena.otelo-call.de(194.233.120.14) by custos.otelo-call.de via smap (V2.1) id xma003149; Wed, 7 Apr 99 23:03:01 +0200 Received: (from listmail@localhost) by helena.otelo-call.de (8.8.5/8.8.5) id XAA05230 for freebsd-isdn@freebsd.org; Wed, 7 Apr 1999 23:03:01 +0200 (MET DST) From: Christoph Weber-Fahr Message-Id: <199904072103.XAA05230@helena.otelo-call.de> Subject: Re: vanishing isdnd - whats that ? In-Reply-To: <199904071941.VAA00755@peedub.muc.de> from Gary Jennejohn at "Apr 7, 99 09:41:35 pm" To: garyj@muc.de Date: Wed, 7 Apr 1999 23:02:22 +0200 (MET DST) X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, > Christoph Weber-Fahr writes: > >> > you have to set idletime-outgoing to a non-zero value. I use 30, but _any_ > >> > value other than 0 is OK. Perhaps the code for I4B_TIMEOUT_UPD should use > >> > a default if a value of 0 is passed in ? > >> > >> Should we allow for an "infinite" value, or is this just to prone of pilot > >> errors? > > > >actually, this value in my config had precisely this purpose, is there > >this way since 0.63, and although I don't find that anywhere in > >the documentation I seem to remember having read somewhere (here ?), > >that a 0 timeout meant no timeout. > > > >If that's not 'the way', what can I use to acchieve a completely > >manually controlled link ? Would be a timeout of say, maxint, possible ? > >(Hm... and how long is this actually ? :-) > > > > this behavior is AFAIK new since 0.63. If you want to manually control your > timeout then don't specify a rates value. See the isdnd man page, it's all > explained there. Hm... I have seen it (actually, it's in the isdnd.rc man page, but anyway, I've read both.). There are the numerous ways explained you can cause the connection dropped. But I don't want it dropped at all - I only want it drop when I tell it to be dropped (currently, by ifconfig interface down. The question if that's a sufficient interface has been discussed here in the past.). I didn't find that explained. Is it possible ? Regards Christoph Weber-Fahr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message