Bug 70200

Summary: ifdown-post removes ppp peers' config
Product: [Retired] Red Hat Linux Reporter: Matthew Melvin <matthewmelvin>
Component: initscriptsAssignee: Bill Nottingham <notting>
Status: CLOSED DEFERRED QA Contact: Brock Organ <borgan>
Severity: low Docs Contact:
Priority: medium    
Version: 7.3CC: dgunchev, michael, msterret, rvokal, than
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-09-29 20:10:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 78984    
Attachments:
Description Flags
sample /etc/ppp/peers/ppp0 for pptp connection
none
sample /etc/sysconfig/network-scripts/ifcfg-ppp0 file for pptp none

Description Matthew Melvin 2002-07-31 01:12:19 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.5 (X11; Linux i686; U;) Gecko/0

Description of problem:
After a ppp interface is taken down the ifdown-post script unconditionally
removes /etc/ppp/peers/${DEVICE} file.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Create customer peers config like /etc/ppp/peers/ppp0
2. ifup ppp0
3. ifdown ppp0

Actual Results:  The /etc/ppp/peers/ppp0 config file is gone.

Expected Results:  The /etc/ppp/peers/ppp0 config file should still be there.
ifup-ppp will create a peers config if one doesn't already exist which contains
just the chat command pointing at the chat-${$DEVICE} file.  ifdown-post should
either not delete the config file at all or only delete it if it knows it
created it in the first place.

Additional info:

Having a custom peers config makes it very easy to create a pptp tunnel that can
be manipulated with ifup/ifdown ect just like any other ordinary ppp connection.
 Since getting pptp to work at all requires installing a custom pptp and kernel
package anyway making a small mod to the init scripts is hardly a chore.  Still
it'd be nice it worked as expected.

Comment 1 Matthew Melvin 2002-07-31 01:15:20 UTC
Created attachment 67804 [details]
sample /etc/ppp/peers/ppp0 for pptp connection

Comment 2 Matthew Melvin 2002-07-31 01:16:25 UTC
Created attachment 67805 [details]
sample /etc/sysconfig/network-scripts/ifcfg-ppp0 file for pptp

Comment 3 Bill Nottingham 2002-08-14 01:41:38 UTC
Than, do you recall why we remove the peer config?

Comment 4 Ngo Than 2002-08-14 13:51:15 UTC
if i'm not wrong, it was a problem by changing of nickname.

If the user changes the nickname (not device name), the ppp peers' config still
has the old nickname there. It will fail by next ifup with old argument --chat
NICKNAME.


Comment 5 MIchael Kolmodin 2002-12-04 13:53:06 UTC
My workaround has been to use the ifup-pre-local script (a hook in ifup) to 
copy a fresh copy of the configuration to /etc/ppp/peers. Clumsy, bit it works
without patching existing scripts.

Note: removing the file is just plain wrong. The peers file is well documented
in pppd, and removing these files violates whats described there

Comment 6 Bill Nottingham 2005-09-29 20:10:30 UTC
Closing bugs on older, no longer supported, releases. Apologies for any lack of
response.

If this persists on a current release, such as Fedora Core 4, please open a new bug.