Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 224329 - NetworkManager removes all network access and fails on both wired and wireless network access
Summary: NetworkManager removes all network access and fails on both wired and wireles...
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 6
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Christopher Aillon
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2007-01-25 10:07 UTC by Xander D Harkness
Modified: 2016-06-07 22:45 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-01-25 10:17:20 UTC

Attachments (Terms of Use)

Description Xander D Harkness 2007-01-25 10:07:20 UTC
NetworkManager fails to obtain any network address.  If I start NetworkManager when the wired 
interface already has a dhcp address it removes the IP and never requests or obtains another address 
for that interface.

If I request access to a WEP wireless network I can enter the full hex password, I can enter the password 
or the password prefixed with s: and it will never join the network.  The password is correct for macosx 
and Windows are perfectly happy to join the same network using these credentials.

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

How reproducible:
Every single version of NetworkManager I have ever tried.

Steps to Reproduce:
1. Try to use NetworkManager
2.NetworkManager will strip any IP the computer has and refuse to provide any network access
Actual results:
NetworkManager removes network access.

Expected results:
NetworkManager should make accessing networks as seamless as macosx does

Additional info:

Comment 1 Xander D Harkness 2007-01-25 10:17:20 UTC
The dhcdbd service was not running. Why NetworkManager does not start this service if it is essential I 
have no idea...

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