Very Computer

I am running the latest version of pppd (2.4.0)
when pppd connects to my isp it doesn't run the ip-up script in /etc/ppp
yes, it has x permissions.

what can it be?

Quote:>I am running the latest version of pppd (2.4.0)
>when pppd connects to my isp it doesn't run the ip-up script in /etc/ppp
>yes, it has x permissions.

How do you know it is not running ip-up? Where is it located? Is it a
valid script(what happens if you run it on its own). What does the debug
log say?

Quote:> >I am running the latest version of pppd (2.4.0)
> >when pppd connects to my isp it doesn't run the ip-up script in /etc/ppp
> >yes, it has x permissions.

> How do you know it is not running ip-up? Where is it located? Is it a
> valid script(what happens if you run it on its own). What does the debug
> log say?

In /etc/ppp/ip-up i have 1 command:
/etc/rc.d/rc.firewall

but that script never gets called. When the interface comes up, i can use
the internet on the server, but not on the LAN clients. this is because the
firewall rules are never added because the rc.firewall is never called. If i
manually run the file, then the rules are added and the LAN can make friends
with the internet.

pppd debugging doesn't even mension anything about ip-up or any other
scripts being executed.

if i run the script on its own then it runs good and does what its supposed
to.

# ./ip-up
lalala adding firewall rules... lalala
ok lan works now
incoming message from computer: haha, i didnt call your ip-up script
# oh yah? take this!
# deltree /

]> >I am running the latest version of pppd (2.4.0)
]> >when pppd connects to my isp it doesn't run the ip-up script in /etc/ppp
]> >yes, it has x permissions.
]>
]> How do you know it is not running ip-up? Where is it located? Is it a
]> valid script(what happens if you run it on its own). What does the debug
]> log say?

]In /etc/ppp/ip-up i have 1 command:
]/etc/rc.d/rc.firewall

]but that script never gets called. When the interface comes up, i can use

Publishing the script might help. Remember that it is a shell script
which is executed, not sourced. Ie, it must start with
#!/bin/bash
(ip-up that is)

Works for me.  Check that you specify full path names for the programs
you try to execute.  Messages  with "echo" require special attention.
You must say what it is that indicates that "it doesn't run the ip-up
script."

--

/* Those who can't write, write manuals. */

Does this mean that there is no mention in the logs even when you
use the pppd debug option?  If that's so then it *is* strange,
but, as Bill Unruh suggested, the first line of the ip-up script
must be "#!/bin/bash" or the equivalent.

--

/* Recipe for a unified PPP debug log file:  Add the line
   " local2.*;*.=debug;*.=notice   /var/log/ppp-log "
   (may need Tab separators) to the /etc/syslog.conf file, and then do
   " kill -HUP `pidof syslogd` " to make syslogd reread it. */