>
> > beczuse it runs rc.firewall and if you use dynamic ip then the ip addr
> > can only be defined in rc.firewall (something like ifconfig | grep 'inet
> > addr' | sed ...etc), so when you run rc.firewall for ppp* devices + not
> > on boot then it will bail out with errors. rc.firewall should ONLY be
> > run on boot IF we are running eth* devices and not ppp devices.
>
> i don't catch the point, rc.firewall is generally here to set
> ipchains rules or enable/disable /proc/sysctl features, what's wrong
> with this ?
>
that's the very pb, when you set it fro dhcp ppp0 it will fail because ppp0
has not even been activated. the ip masq howto tell you to put rc.firewall
in /etc/rc.d/rc.firewall so when you use mdk, it will fail.
or should i be doing my custom rc.firewall in ip-up.local for ppp0 ?
> > alos when you ahlt the system with shutdown -r now then it brings down
> > ppp* ok, but it still says failed. pls fix.
>
> we try to bring down all interfaces even the one who are not
> setup with ONBOOT=yes (because the user can do some ifup
> interface). I don't see why he say failed.
>
> --
i'm not sure either :((( this bug is reproducable on my machine. the strange
pb is that i am using ppp 2.3.11 and the newest initscripts and eth0 work
fine. but when ifup ppp0 but when you issue shutdown -r now && ppp0 is not
down yet then it says it fails ([FAILED]) even though it seems to shutdown
properly.
> MandrakeSoft Inc http://www.mandrakesoft.com
> San-Diego, CA USA. --Chmouel
>
