From owner-freebsd-isdn Wed Jul 19 11:56:40 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id 7D92C37B5EE for ; Wed, 19 Jul 2000 11:56:30 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.9.3/8.9.3) with ESMTP id TAA03227; Wed, 19 Jul 2000 19:46:51 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id TAA01101; Wed, 19 Jul 2000 19:12:41 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200007191812.TAA01101@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Martin Husemann Cc: drt@ailis.de (Doobee R . Tzeck), freebsd-isdn@FreeBSD.org, brian@Awfulhak.org Subject: Re: Calling a programm *before* the line is taken down. In-Reply-To: Message from Martin Husemann of "Fri, 14 Jul 2000 16:06:33 +0200." <200007141406.e6EE6XO00380@rumolt.teuto.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 19 Jul 2000 19:12:39 +0100 From: Brian Somers Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The correct way (or one of them anyway) to handle this sort of thing is with the time-remaining stuff specified for ppp in rfc1570. It's been on my todo list for a long time.... > > It seems to me, I have to find all calls to N_DISCONNECT_REQUEST in i4bdrv.c > > and i4bl4.c and chage them to sending a special Message like > > WILL_DISCONECT_IND to userland, wait 5 seconds and then disconnect. > > I'm not sure this will work at this level: think of sudden ISDN disconnects > (i.e. the famous cleaning woman pulling the line) > > What you need is a notification from ispp before it changes IPCP state to down, > but that may be too late too. > > If you are just concernd about isdnd's idle timeout: simple add another > timer triggering an adjustable time before the idle timeout occurs and set > a special flag noting that the connection is going to drop now (idle timeout > will not fire, because you are causing network traffic again). > > Or add an external program that is queried on idle timeout, returning either > 0 (we may shut down the connection) or some error code (no, let's stay online). > > > Martin -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message