Bug 60469 - neat trashes rp3 settings
Summary: neat trashes rp3 settings
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-network
Version: 7.2
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Harald Hoyer
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: rcn-7.3
TreeView+ depends on / blocked
 
Reported: 2002-02-28 00:19 UTC by Eric Fallon
Modified: 2007-04-18 16:40 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-02-05 15:14:45 UTC
Embargoed:


Attachments (Terms of Use)
Requested wvdial.conf file (358 bytes, text/plain)
2002-04-22 21:54 UTC, Eric Fallon
no flags Details

Description Eric Fallon 2002-02-28 00:19:48 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2.1) Gecko/20010901

Description of problem:
After running rp3-config and creating a new internet dialup connection the
following occurs upon running neat.

The following message is displayed when opening neat:
Copying ifcfg-ppp0 to devices and putting it into the default profile.

If you press the apply button in neat and then open rp3 you will note that the
dial-up account you created using rp3-config has been replaced with an entry
called ppp0. If you try to start this interface it will not proceed to dial. 

At this point it is necessary to re-run rp3-config and re-create your internet
account.


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


How reproducible:
Always

Steps to Reproduce:
1.Create a dial-up modem account using rp3-config.
2.Open neat from command line and verify the following message:
Copying ifcfg-ppp0 to devices and putting it into the default profile.
3. Click the apply button in neat.
4. Open rp3 and note that the account created in step 1 has been replaced with a
ppp0 entry in the interface window.
5. Attempt to start the new ppp0 entry from rp3. Account is not dialed.
6. Re-run rp3-config and re-create the account you set up in step 1. 
	

Expected Results:  You should be able to change your eth0 settings etc. from
neat without destroying the account you created using rp3-config.

Additional info:

modem device: ttyS0

Comment 1 Harald Hoyer 2002-04-05 12:17:10 UTC
please attach /etc/wvdial.conf after rp3-config

Comment 2 Eric Fallon 2002-04-22 21:54:14 UTC
Created attachment 54905 [details]
Requested wvdial.conf file

Comment 3 diego.santacruz 2002-04-25 08:40:36 UTC
I did also experience the same problem.
The problem appears to be that redhat-config-network makes the file readable
only by root, and then rp3 (when executed as non-root) cannot read the
connection name from the file, nor its settings. If rp3 is executed as root
everything is OK (because the file can be read).

I changed the file permissions to readable by all and that solved the problem.

My RPM version is redhat-config-network-0.9.10-2 (RedHat 7.2)

I guess that interfaces that are marked as startable by normal users should have
their config files with mode 644.

Comment 4 Harald Hoyer 2002-10-23 09:55:06 UTC
first beta of erratum is available at:
ftp://people.redhat.com/harald/redhat-config-network/1.0.1-1/

Most of the bugs reported have been removed, but as in every software change,
there could be new bugs introduced.

Please report bugs against this with explicitly stating the 1.0.1 version... Thx
and please test.


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