[Bug 139812] Re: knetworkmanager can't acquire dhcp address on wep network

scoobymad555 benmacer at googlemail.com
Tue Jun 17 10:34:29 UTC 2008


can now confirm this as a problem on Hardy also ........ exact same
issues as above. Using Gnome, with nm-applet 0.6.6 and dhclient
connecting with an intel pro chipset to a bt voyager access point
running WEP 128bit.

Initial problem appears to be with the encryption key being sent since
nm-applet just repeatedly failed to connect to the access point and on
the rare occasion it did show a connection no traffic successfully
passed - couldn't even ping the access point when i forced my local
config to static address.

"iwconfig eth1 essid {network name} key s:{passphrase}"  (sudo)  was
good enough to get me connected to the access point.

at this point a static config then works fine but switching nm-applet to
dhcp fails to pull an address and defaults to 169. dhclient run at cli
seemed to be unable to pull an address aswell. Tried killing off the pid
files (backups made) but made no difference. Still got dhcp request
timeouts.

tried using ifup & ifdown and also tried using the script in etc/init.d
to restart networking but none seemed to make any difference on my
system.

Installed dhcpcd client to try out which worked.

"dhcpcd eth1" (also sudo)


will also try this / suitable variant on the xandros systems i've been
seeing trouble with aswell to see if it works.

-- 
knetworkmanager can't acquire dhcp address on wep network
https://bugs.launchpad.net/bugs/139812
You received this bug notification because you are a member of Kubuntu
Team, which is subscribed to knetworkmanager in ubuntu.




More information about the kubuntu-bugs mailing list