From Bugzilla Helper:
User-Agent: Mozilla/4.75 [en] (X11; U; Linux 2.4.7 i686)
Description of problem:
System is compiled Kernel 2.4.7 on an initially RH7.0 distro, various
packages upgraded as required from 7.1 distro.
My problem is that with the configuration for the ppp0 interface set
for demand dialing (DEMAND=yes, in
/etc/sysconfig/network-scripts/ifcfg-ppp0 as I have attached) if I call
'ifup ppp0' and then if the 'ifdown ppp0' is run prior to an actual dial
and connection the ppp0 device does not seem to be shutdown properly. Some
defunct processes are listed in the 'ps -ax' list.
Note this also occurs when I start the device using rp3 through the Gnome
Subsequent 'ifup ppp0' requests seem to work ok but since ppp0 was not
shut down properly the new connections are on new devices ppp1, ppp2 or
more. Rerunning 'ifdown ppp0' will not flush the spurious devices from
I have also seen a similar effect when the connection has failed due
for example to the modum having been switched off to break a connection.
Running ifconfig or checking /proc/sys/net/ipv4/conf/ shows these spurious
On the other hand, if there was an intervening connection to the internet,
ifdown cleans everything up nicely.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. setup for demand dialling
2. /sbin/ifup ppp0 then shortly after...
3. /sbin/ifdown ppp0
Expected Results: all pppX devices closed
Forgot to mention: initscripts-5.83-1 in use
I had a similar problem: my ADSL link didn't go down properly, and that caused
problems with the remote server (15 minutes before re-connexion, ...).
I think that's because ifdown-ppp doesn't read the ifcfg-pppX file. I added
'need_config' to have ifdown-ppp reading that file and now it runs well;
here is the diff:
[boris@arthemisia network-scripts]$ diff ifdown-ppp-new ifdown-ppp
Created attachment 51432 [details]
patched ifdown-ppp (read my comment). NOTE: I don't know if it's good.
There has been work on demand dialing PPP lines. It works for me with the most
recent releases. Does anybody else still have this problem? Otherwise maybe we
(reporter or Red Hat I guess) could do resolve/currentrelease?
Please do try with current releases; there's definitely been fixes since 7.0.