From owner-freebsd-current Thu Sep 11 02:04:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA08722 for current-outgoing; Thu, 11 Sep 1997 02:04:25 -0700 (PDT) Received: from usr05.primenet.com (tlambert@usr05.primenet.com [206.165.6.205]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA08717 for ; Thu, 11 Sep 1997 02:04:22 -0700 (PDT) Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id CAA11829; Thu, 11 Sep 1997 02:03:45 -0700 (MST) From: Terry Lambert Message-Id: <199709110903.CAA11829@usr05.primenet.com> Subject: Re: PPP - why set CLOCAL for server ('-direct' mode) ? To: mike@smith.net.au (Mike Smith) Date: Thu, 11 Sep 1997 09:03:45 +0000 (GMT) Cc: Shimon@i-Connect.Net, tlambert@primenet.com, current@freebsd.org, nnd@itfs.nsk.su In-Reply-To: <199709110456.OAA06582@word.smith.net.au> from "Mike Smith" at Sep 11, 97 02:56:13 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > The solution is very simple; Upon open, you open anyway, ignoring but > > remembering DCD. If you get a change of state from inactive to active, you > > change the state, but ignore it. However, if the state transitions from > > ACTIVE to INACTIVE, you terminate the connection, close the port and > > generate SIGHUP. This is the simplest and most correct way to handle it. > > This is how a callout device works, although SIGHUP is only delivered > if the port is the controlling tty of the process. Note, however, that > user-mode ppp _doesn't_want_this_, which is the whole issue. Why doesn't user-nmode PPP want this? > It wants to poll for carrier status, hence CLOCAL. Even if it's a dial-*in* connection and it's acting as the PPP server? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.