Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 97027 - redhat-config-network discards entries in /etc/ppp/chap-secrets
redhat-config-network discards entries in /etc/ppp/chap-secrets
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-network (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Harald Hoyer
: 97029 (view as bug list)
Depends On:
Blocks: rcn-modem
  Show dependency treegraph
Reported: 2003-06-09 07:49 EDT by bastiaan
Modified: 2007-04-18 12:54 EDT (History)
0 users

See Also:
Fixed In Version: system-config-network-1.3.26-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-09-20 08:12:51 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description bastiaan 2003-06-09 07:49:31 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.7 (X11; Linux i686; U;) Gecko/20030131

Description of problem:
If you have entries in /etc/ppp/chap-secrets for connections
redhat-config-network does not know about, e.g. for pptp, these entries will be
lost upon a 'File/Save'. 
It does not matter whether these entries are inside the '####
redhat-config-network ....' demarked section or not.
Also it does not matter whether the changes to be saved have anything to do with
PPP / CHAP or not.

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

How reproducible:

Steps to Reproduce:
1. echo '"testclient" "testserver" "testpass"' >> /etc/ppp/chap-secrets
2. start redhat-config-network
3. edit a setting
4. choose 'File/Save'
5. cat /etc/ppp/chap-secrets

Actual Results:  The 'testclient' entry is gone.

Expected Results:  The 'testclient' entry should have stayed in place.

Additional info:
Comment 1 bastiaan 2003-06-09 08:17:07 EDT
Version-Release number of selected component (if applicable):
Comment 2 Harald Hoyer 2003-06-10 11:17:33 EDT
Please try:

and downgrade rhpl, if necessary with --force :)
Comment 3 Harald Hoyer 2003-06-10 11:18:09 EDT
*** Bug 97029 has been marked as a duplicate of this bug. ***
Comment 4 bastiaan 2003-06-10 15:35:34 EDT
OK, I up- and downgraded to 

Now redhat-config-network fails to startup. Traceback:

Component: redhat-config-network
Version: 1.2.9
Summary: TB NCDevADSL.py:33:load:NameError: global name 'ConfDevice' is not defined
Traceback (most recent call last):
  File "/usr/sbin/redhat-config-network-gui", line 156, in main
    window = mainDialog()
line 169, in __init__
line 238, in load
line 245, in loadDevices
line 263, in getDeviceList
line 117, in load
line 33, in load
NameError: global name 'ConfDevice' is not defined
Local variables in innermost frame:
self: Device.Type=xDSL
name: DePoort

Comment 5 Harald Hoyer 2003-06-11 03:41:04 EDT
ok, second try, same ftp location, version 1.2.9-2
Comment 6 bastiaan 2003-06-11 16:25:42 EDT
upgraded to redhatc-config-network-1.2.9-2 and rhpl-0.105.1-2.

This is much bettter:
* It does not crash on start
* It remembers the password for the xDSL connection

Some things are still broken:
* It still discards my PPTP passwords in /etc/ppp/chap-secrets. Surprisingly
enough it leaves the comments by pptp-php-gtk.php intact.
* If you change the login name of the xDSL connection, redhat-config-network,
does create a new entry with the name in /etc/ppp/chap-secrets, but does not
remove the old entry.

Something that may or not be intended behaviour:
redhat-config-network actually creates two lines in chap-secrets:
"username" <tab> "nickname" <tab> "password"
"username" <tab> * <tab> "password"

The second line will generate a conflict if you have another PPP connection with
the same username.

Also, at least in my case the server field should not contain the device
nickname but the AC-Name. (I've worked around this by choosing the nickname of
the device to equal the AC-Name, but this results in problems when trying to
enable the device at boot time, see bug #97030).

Note You need to log in before you can comment on or make changes to this bug.