firewall script inetcpppipup.d

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

oinophlux

Probably.

The interface won't be initialized until theetc-ppp-ip-up script completes, and it's my guess thatetc-ppp-ip-up invokes theetc-ppp-ip-up.d-* scripts, in your environment.

You should know that pppd pbuttes several parameters toetc-ppp-ip-up (andetc-ppp-ip-down) that are probably pbutted on to your scripts. Read the manpage on pppd(8) ("man 8 pppd") and look for the section on ip-up. There, you will find that pppd gives ip-up - - the name of the interface ("ppp0") - - the name of the device ("-dev-ttyS0") - - the speed of the interface ("33600") - - the IP address buttigned by pppd to your end of the ppp connection, - - the IP address buttigned by pppd to the other end of the ppp connection, and - - a text value that was pbutted to pppd through the "ipparm" parameter Your scripts should be able to use these values directly instead of trying to parse the output of ifconfig to obtain them indirectly.

FWIW, my pppd enables and disables my firewall through the ip-up and ip-down scripts respectively, and I get the local IP address and interface name from the values pbutted in to the ip-up and ip-down scripts by pppd. For an example of how these values come in, you can see my Linux Gazette article at firewalling, but it does show (incidentally) the origin and use of those parameters.

- -- Lew Pitcher

Master Codewright & JOAT-in-training GPG public key available on request Slackware - Because I know what I'm doing. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.7 (GNU-Linux)

iD8DBQFDUZ35agVFX4UWr64RAk+9AKCaAplyV7JGwFJUxRqjF6IayTx+EgCfTcw2 HrC6q-okCnkHsY-4RRfzd6s= =me-e -----END PGP SIGNATURE-----