From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031009 Epiphany/1.0.1 Description of problem: After activating an interface (in my case: a ppp interface), the status of the interface isn't updated in the list of interfaces (status column still says inactive). Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Start redhat-config-network 2. Choose an interface in the list of interfaces 3. Click "Activate" [interface is activated] 4. Done Actual Results: The IF is still listed as inactive. Expected Results: The IF should be listed as active, and the "Inactivate" button should be enabled. Additional info:
should be fixed in 1.3.8 appearing soon on rawhide
*** Bug 107794 has been marked as a duplicate of this bug. ***
*** Bug 106541 has been marked as a duplicate of this bug. ***
I am using redhat-config-network-1.3.8-1. When I bring up my DSL connection with PPPoE, the ethernet interface is activated automatically (verified using ifconfig). However, redhat-config-network still shows eth0 is being inactive. This has been broken since test2. It worked in test1. See bug #105748.
After a clean install of FC1, my problem with eth0 still existed. I found that I could simply delete the eth0 interface in redhat-config-network, which removes the ifcfg-eth0 file. Despite this, the connection comes up fine and ifconfig shows eth0 active. Since I rely on the xDSL interface to bring up eth0 and never do it manually, all is now well. This may be related to the fact that there appears to be no way to configure an IP-less configuration for eth0. During the install, the only two choices are use DHCP (which is wrong) and manually entering an IP address and netmask (which aren't needed).
this was NEVER an issue for me. My eth0 was ever and in all versions of fedora working and shown correctly. Even I was able do deactivate it and it was shown deactivated when doing so. All works well for me. So I removed me from CC... good luck + farewell Norbert
This bug is present in RHEL 3 on my system.
*** This bug has been marked as a duplicate of 106980 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.