Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 18 Sep 1997 13:23:57 -0700 (PDT)
From:      dburr@POBoxes.com
To:        FreeBSD-gnats-submit@FreeBSD.ORG
Subject:   bin/4575: user-ppp (iij-ppp) should use /etc/ppp/ip-{up,down}
Message-ID:  <199709182023.NAA03202@DonaldBurr.dyn.ml.org>
Resent-Message-ID: <199709182030.NAA04221@hub.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         4575
>Category:       bin
>Synopsis:       user-ppp (iij-ppp) should use /etc/ppp/ip-{up,down}
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Thu Sep 18 13:30:00 PDT 1997
>Last-Modified:
>Originator:     Donald Burr
>Organization:
Starfleet Command
>Release:        FreeBSD 2.2.2-RELEASE i386
>Environment:

	any properly-installed FreeBSD system

>Description:

	iij-ppp (aka userland PPP) should use the /etc/ppp/ip-up and
	/etc/ppp/ip-down scripts when the link goes up and down.  It
	should give these scripts the exact same argument list as pppd
	does.  (for compatibility -- I use both pppd and iij-ppp on the
	same system, and switch whenever it suits me.  Or think of the
	guy who wants to switch FROM pppd TO iij-ppp without having to
	rewrite his scripts!)

	The reason why the ip-up/down script arguments are important is
	that some programs you may want to run in these scripts require
	arguments.  An example (one that I actually use) is with the
	Monolith DYNDNS service (http://www.ml.org/), which allows users
	with dynamically-assigned IP addresses (i.e. a PPP account with
	a ISP) to have their own domain name (e.g. mydom.dyn.ml.org).
	You need to run a client every time you dial in, so that the
	Monolith nameserver knows about what IP address you're using now.
	This client requires, among other data, the IP address of the
	PPP connection to be passed in as the argument.

	Other useful uses for the /etc/ppp/ip-{up,down} script are (some
	of which I actually use): writing all users (wall) when the
	connection goes up and down, starting SUCK (to grab nntp news),
	running 'ping <some_ip>' to keep the connection up all the time,
	etc.

>How-To-Repeat:

	IRRELEVANT.  (RESISTANCE IS FUTILE.)

>Fix:
	
	Don't ask me -- I'm a doctor, not a programmer! :)

>Audit-Trail:
>Unformatted:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199709182023.NAA03202>