Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 107816 - Interface status list not updated after activation of interface
Summary: Interface status list not updated after activation of interface
Keywords:
Status: CLOSED DUPLICATE of bug 106980
Alias: None
Product: Fedora
Classification: Fedora
Component: redhat-config-network
Version: rawhide
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Harald Hoyer
QA Contact:
URL:
Whiteboard:
: 106541 107794 (view as bug list)
Depends On:
Blocks: 111252 rcn-modem
TreeView+ depends on / blocked
 
Reported: 2003-10-23 12:23 UTC by Mikael Carneholm
Modified: 2007-11-30 22:10 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 18:59:20 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Mikael Carneholm 2003-10-23 12:23:38 UTC 
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:
Comment 1 Harald Hoyer 2003-10-24 15:19:24 UTC 
should be fixed in 1.3.8 appearing soon on rawhide
Comment 2 Harald Hoyer 2003-10-24 15:20:30 UTC 
*** Bug 107794 has been marked as a duplicate of this bug. ***
Comment 3 Harald Hoyer 2003-10-24 15:53:10 UTC 
*** Bug 106541 has been marked as a duplicate of this bug. ***
Comment 4 Andre Robatino 2003-10-26 19:24:28 UTC 
  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.
Comment 5 Andre Robatino 2003-11-10 05:54:58 UTC 
  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).
Comment 6 Norbert Breun 2003-12-01 15:28:00 UTC 
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
Comment 7 Norbert Breun 2003-12-01 15:29:33 UTC 
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
Comment 8 Brad Smith 2003-12-03 04:45:24 UTC 
This bug is present in RHEL 3 on my system.
Comment 9 Harald Hoyer 2004-06-04 13:31:10 UTC 

*** This bug has been marked as a duplicate of 106980 ***
Comment 10 Red Hat Bugzilla 2006-02-21 18:59:20 UTC 
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.
Note You need to log in before you can comment on or make changes to this bug.