Bug 88690 - Can't get into network configuration
Summary: Can't get into network configuration
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: netcfg
Version: 9
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-04-11 22:07 UTC by Derek Donnelly
Modified: 2007-04-18 16:52 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-01-02 18:27:44 UTC
Embargoed:


Attachments (Terms of Use)
File generated upon launching "network" (1.29 KB, text/plain)
2003-04-11 22:08 UTC, Derek Donnelly
no flags Details
dump created when network configuration crashed when opening utility was attempted (1.41 KB, text/plain)
2003-05-01 14:40 UTC, Paige Gabhart
no flags Details

Description Derek Donnelly 2003-04-11 22:07:02 UTC
Description of problem:  Setting up wireless network card WPC11 on DELL C600
running Redhat 9.  


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


How reproducible:  Select "Sytem Settings" --> "Network"


Steps to Reproduce:
1.
2.
3.
    
Actual results:


Expected results:


Additional info:  The wireless card appears to be working, however, I also use
the xircom cardbus ethernet card 10/100 at work.  I'd like to get into network
configuration and setup eth0 and eth1, one for each card.  I can't seem to get
into network configuration.

Comment 1 Derek Donnelly 2003-04-11 22:08:56 UTC
Created attachment 91086 [details]
File generated upon launching "network"

Comment 2 Paige Gabhart 2003-05-01 14:40:27 UTC
Created attachment 91440 [details]
dump created when network configuration crashed when opening utility was attempted

Comment 3 Paige Gabhart 2003-05-01 14:46:25 UTC
I was attempting to configure a pc to pc network using two new D-Link 10/100
Mbps Fast ethernet PCI adaptors (Model DFE-530TX).  The inability to configure
the network has also left me unable to open an internet connection unless I go
to root.

Comment 4 Bill Nottingham 2006-08-05 03:07:37 UTC
Red Hat apologizes that these issues have not been resolved yet. We do want to
make sure that no important bugs slip through the cracks.

Red Hat Linux 7.3 and Red Hat Linux 9 are no longer supported by Red Hat, Inc.
They are maintained by the Fedora Legacy project (http://www.fedoralegacy.org/)
for security updates only. If this is a security issue, please reassign to the
'Fedora Legacy' product in bugzilla. Please note that Legacy security update
support for these products will stop on December 31st, 2006.

If this is not a security issue, please check if this issue is still present
in a current Fedora Core release. If so, please change the product and version
to match, and check the box indicating that the requested information has been
provided.

If you are currently still running Red Hat Linux 7.3 or 9, please note that
Fedora Legacy security update support for these products will stop on December
31st, 2006. You are strongly advised to upgrade to a current Fedora Core release
or Red Hat Enterprise Linux or comparable. Some information on which option may
be right for you is available at http://www.redhat.com/rhel/migrate/redhatlinux/.

Any bug still open against Red Hat Linux 7.3 or 9 at the end of 2006 will be
closed 'CANTFIX'. Again, if this bug still exists in a current release, or is a
security issue, please change the product as necessary. We thank you for your
help, and apologize again that we haven't handled these issues to this point.


Comment 6 Bill Nottingham 2007-01-02 18:27:44 UTC
Red Hat Linux 7.3 and Red Hat Linux 9 are no longer supported by Red Hat, Inc.
f you are currently still running Red Hat Linux 7.3 or 9, you are strongly
advised to upgrade to a current Fedora Core release or Red Hat Enterprise Linux
or comparable. Some information on which option may be right for you is
available at http://www.redhat.com/rhel/migrate/redhatlinux/.

Closing as CANTFIX.


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