Bug 15086

Summary: editing advanced connection properties corrupts connection
Product: [Retired] Red Hat Linux Reporter: Joe Bowman <rhml>
Component: rp3Assignee: Nalin Dahyabhai <nalin>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-08-01 23:35:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Joe Bowman 2000-08-01 23:35:44 UTC
When creating a ppp connection using rp3, if you edit the connection and
change any of the advanced settings, the connection. It appears to grab
settings from somewhere other than /etc/sysconfig/network-scripts or

Jul 31 22:01:24 merlin pppd[3902]: pppd 2.3.11 started by root, uid 0
Jul 31 22:01:24 merlin pppd[3902]: Using interface ppp1
Jul 31 22:01:24 merlin pppd[3902]: local  IP address
Jul 31 22:01:24 merlin pppd[3902]: remote IP address
Jul 31 22:01:29 merlin pppd[3902]: Terminating on signal 2.
Jul 31 22:01:29 merlin pppd[3902]: Exit.

It never talks to the modem once you edit the connection settings, however,
if you select the connection and use 'debug' mode, it connects properly.
I'm unable to find where it's grabbing the 10.x.x.x ip addresses from in
any of the configuration files in /etc.

If you create the connection and then edit the connection settings by hand
instead of using rp3 to edit them, rp3 will be able to dial in and connect
fine with the changed settings.

Comment 1 Nalin Dahyabhai 2000-08-07 09:38:25 UTC
This is a buglet in the hooks initscripts provides to do demand-dialing,
triggered by an rp3 bug.  Both are now fixed (rp3-1.1.3-3, initscripts-5.40).