From owner-freebsd-hackers  Tue Sep  9 17:21:16 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id RAA18439
          for hackers-outgoing; Tue, 9 Sep 1997 17:21:16 -0700 (PDT)
Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA18376
          for <freebsd-hackers@FreeBSD.ORG>; Tue, 9 Sep 1997 17:20:07 -0700 (PDT)
Received: from gate.lan.awfulhak.org (localhost [127.0.0.1])
	by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id BAA19331;
	Wed, 10 Sep 1997 01:18:04 +0100 (BST)
Message-Id: <199709100018.BAA19331@awfulhak.demon.co.uk>
X-Mailer: exmh version 2.0zeta 7/24/97
To: Archie Cobbs <archie@whistle.com>
cc: grog@lemis.com (Greg Lehey), doconnor@ist.flinders.edu.au,
        freebsd-hackers@FreeBSD.ORG
Subject: Re: Divert sockets.. 
In-reply-to: Your message of "Mon, 08 Sep 1997 20:53:34 PDT."
             <199709090353.UAA26952@bubba.whistle.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 10 Sep 1997 01:18:04 +0100
From: Brian Somers <brian@awfulhak.org>
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> 
> > >> IMHO, the proper way to do this is to let the PPP daemon handle it
> > >> by installing a route first (so you let the routing code determine
> > >> whether packets are supposed to go over the WAN link or not, as it
> > >> should) and then checking each outgoing packet for suitability as
> > >> "demand" (not all are, e.g., NTP packets). When "demand" is seen,
> > >> it should start dialing, etc. The same "demand" test can also apply
> > >> to idle timeout calculations. This is how mpd does it, anyway.
> > >
> > > Yeah, same with ijppp, but it means you can only use those packages to
> > > do a connection, ie its not very general...
> > 
> > I don't understand.  Which packets do you want to use?  If they're not
> > destined for that interface, they shouldn't cause a dialup.
> > 
> > > (So its too bad if you have dialon demand ISDN :)
> > 
> > I don't understand this statement, either.
> 
> I think what he's saying is that it would be nice to divorce the
> "dial-on-demand" functionality from the thing that is actually
> doing the dialing... you could do this with divert sockets, but
> it would require some sort of "api" to the PPP process not only
> to tell it to connect (eg, send SIGUSR1), but also to be able to
> determine whether the link is already up (to avoid a flood of
> such signals).

The "ask it to dial" bit is functional now (as of a few minutes ago) 
with the following:

  pppctl -v -t 120 -p xxx 3000 dial

The "is the line up" bit has been there for some time:

  pppctl -v -p xxx 3000 show log | grep ^PPP >/dev/null && echo UP

> -Archie
> 
> ___________________________________________________________________________
> Archie Cobbs   *   Whistle Communications, Inc.  *   http://www.whistle.com

-- 
Brian <brian@awfulhak.org>, <brian@freebsd.org>
      <http://www.awfulhak.org>
Don't _EVER_ lose your sense of humour....