network-manager doesn't set WLAN-Config at all
Bug #37069 reported by
Kai F. Lahmann
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
Fix Released
|
Medium
|
Scott James Remnant (Canonical) |
Bug Description
situation here: a rt2500 serving as an Ad-Hoc-WLAN-Gateway (including working DHCP, secured with WEP). (only) Client is an intel ipw2100. Manual connecting works.
now, if I try to connect to that WLAN over network-manager it fails: I get asked for the WEP-Key, so normally the network-manager should now have all values to configure iwconfig, but it doesn't connect. If I check iwconfig afterwards, ALL values (including the essid) are resetted to default or empty - so it's quite obvious, why it can't work - only question: why doesn't it set the values, as it should?!?
To post a comment you must log in.
I might have the same bug here. I'm using a laptop with intel ipw2200 chipset. The wireless network is not encrypted (but does not broadcast SSID). I supply the SSID, the nm-applet seems to activate but takes ages. After a while, I get the 'wireless link monitor' icon, but the 4 levels are grey and not blue.
If I take a look at iwconfig : it's all blank, as if it was not configured by NetworkManager. If I manually fill in the appropriate settings using iwconfig, the icon directly goes to all blue, and then the connection works fine.
Looking at /var/log/ daemon. log, during the activation of the connection dhclient does not manage to get an ip, because of unreachable network. Then NM acquire a private IP using autoip.
I'm running dapper flight 6, and I have no software nor hardware radio switch.
Apr 19 09:11:30 asus NetworkManager: <information> ^Istarting. .. ^Ieth0: Device is fully-supported using driver '8139too'. ^Inm_device_ init(): waiting for device's worker thread to start ^Inm_device_ init(): device's worker thread started, continuing. ^Ieth1: Device is fully-supported using driver 'ipw2200'. ^Inm_device_ init(): waiting for device's worker thread to start ^Inm_device_ init(): device's worker thread started, continuing. ^IUpdating allowed wireless network lists. ^ISWITCH: no current connection, found better connection 'eth1'. ^IDevice eth1 activation scheduled... ^IActivation (eth1) started... ^IActivation (eth1) Stage 1 of 5 (Device Prepare) scheduled... ^IActivation (eth1) Stage 1 of 5 (Device Prepare) started... ^IActivation (eth1) Stage 2 of 5 (Device Configure) scheduled... ^IActivation (eth1) Stage 1 of 5 (Device Prepare) complete. ^IActivation (eth1) Stage 2 of 5 (Device Configure) starting... ^IWireless network benbarb for interface eth1 is not encrypted, not starting wpasupplicant ^IActivation (eth1) Stage 2 of 5 (Device Configure) successful.
Apr 19 09:11:30 asus NetworkManager: <WARNING>^I main (): nm_data_new: Setting up dbus filter
Apr 19 09:11:31 asus NetworkManager: <information>
Apr 19 09:11:31 asus NetworkManager: <information>
Apr 19 09:11:31 asus NetworkManager: <information>
Apr 19 09:11:31 asus NetworkManager: <information>^INow managing wired Ethernet (802.3) device 'eth0'.
Apr 19 09:11:31 asus NetworkManager: <information>
Apr 19 09:11:31 asus NetworkManager: <information>
Apr 19 09:11:31 asus NetworkManager: <information>
Apr 19 09:11:31 asus NetworkManager: <information>^INow managing wireless (802.11) device 'eth1'.
Apr 19 09:12:07 asus NetworkManager: <information>
Apr 19 09:12:07 asus NetworkManager: <information>
Apr 19 09:12:07 asus NetworkManager: <information>^IWill activate connection 'eth1/benbarb'.
Apr 19 09:12:07 asus NetworkManager: <information>
Apr 19 09:12:07 asus NetworkManager: <information>
Apr 19 09:12:07 asus NetworkManager: <information>
Apr 19 09:12:07 asus NetworkManager: <information>
Apr 19 09:12:07 asus NetworkManager: <information>
Apr 19 09:12:07 asus NetworkManager: <information>
Apr 19 09:12:07 asus NetworkManager: <information>
Apr 19 09:12:07 asus NetworkManager: <information>
Apr 19 09:12:07 asus NetworkManager: <information>
Apr 19 09:12:07 asus NetworkManager: <infor...