Hi,
On my laptop, when I boot and login, I have no connection.
I click on knetworkmanager's icon to select my wifi access point, I have
the progress bar going up to 100% and the "signal strength" staircase
icon appears. Looks good, but I don't actually have a connexion: after 4
or 5 seconds the icon updates back to "no connexion".
I click again on knetworkmanager's icon, and this time it works properly
and I have my connexion.
I have to do this little ritual at every boot, and I usually have similar
difficulties when I suspend/resume. It is quite annoying.
Here's my data:
* Dell D430 with an intel 3945ABG wifi card
* Fedora 7 up to date:
kernel-2.6.23.1-10.fc7
iwl3945-firmware-2.14.1.5-1
NetworkManager-0.6.5-7.fc7
knetworkmanager-0.2-0.1.svn20070815.fc8
(I tried the package in the development
repository, hence the fc8, but it didn't
change a thing. Anyway, it is exactly
the same version as in the fc7 repository.)
dhclient-3.0.5-40.fc7
dhcdbd-2.7-5.fc7
* Some excerpts of /var/log/messages:
First try, on login:
====================
[ tries first to activate eth0 before realizing there is no link]
NM: <info> SWITCH: no current connection, found better connection 'wlan0'.
...
NM: <info> Will activate connection 'wlan0/tudia'.
...
NM: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
NM: <info> Activation (wlan0/wireless): access point 'tudia' is encrypted, but NO valid key exists. New key needed.
NM: <info> Activation (wlan0) New wireless user key requested for network 'tudia'.
NM: <info> Old device 'wlan0' activating, won't change.
NM: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
NM: <WARN> nm_dbus_get_user_key_for_network_cb(): nm_dbus_get_user_key_for_network_cb(): dbus returned an error. (org.freedesktop.NetworkManagerInfo.GetKeyError) org.freedesktop.NetworkManagerInfo.GetKeyError
NM: <info> Activation (wlan0) failure scheduled...
NM: <info> Activation (wlan0) failed for access point (tudia)
...
Second try, when I select manually my AP (tudia):
=================================================
NM: <info> User Switch: /org/freedesktop/NetworkManager/Devices/wlan0 / tudia
...
NM: <info> Activation (wlan0/wireless): access point 'tudia' is encrypted, and a key exists. No new key needed.
...
NM: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to access point 'tudia'.
...
NM: <info> Activation (wlan0) Beginning DHCP transaction.
...
dhclient: DHCPACK from 192.168.1.1
dhcdbd: dhco_input_option: Value -1 cannot be converted to type L
dhcdbd: dhco_parse_option_settings: bad option setting: new_dhcp_lease_time = -1
...
10:15:21 dhclient: bound to 192.168.1.4 -- renewal in 953575126 seconds.
...
10:15:23 NM: <info> Activation (wlan0) successful, device activated.
10:15:27 NM: <info> SWITCH: terminating current connection 'wlan0' because it's no longer valid.
10:15:27 NM: <info> Deactivating device wlan0.
Third try, I select again manually my AP:
=========================================
[Basically, everything works fine. Only suspicious bit is:]
10:15:43 dhclient: DHCPACK from 192.168.1.1
10:15:43 dhcdbd: dhco_input_option: Value -1 cannot be converted to type L
10:15:43 dhcdbd: dhco_parse_option_settings: bad option setting: new_dhcp_lease_time = -1
10:15:43 dhcdbd: dhco_input_option: Value -1 cannot be converted to type L
10:15:43 dhcdbd: dhco_parse_option_settings: bad option setting: old_dhcp_lease_time = -1
10:15:43 dhclient: bound to 192.168.1.4 -- renewal in 953575104 seconds.
I didnt want to spam the mailing-list with my full log, so I tried to
select the relevant part and to edit it alittle bit (removed date,
hostname, etc.), but of course, the integrality of it is available
on request.
It looks that NM is able to communicate with knetworkmanager on boot, since
it retrieves the correct AP name, but requesting the key makes an error.
However, on the second try, it already has the key and doesn't issue a
request, as if it managed to get it on the first try anyway. Weird. Why it
fails on the second try is also mysterious. The dhcp server gives a lease
of -1, meaning infinity. Maybe NM takes it litteraly, establishes the
connection, realizes it is expired one second ago, and shut it down ? I
don't know.
Two other random pieces of information: knetworkmanager is configured to
store the keys unencrypted in the config file rather than in kwallet. My
log is full of the following message:
<info> Error getting killswitch power: org.freedesktop.Hal.Device.KillSwitch.NotSupported - Access type not supported
which appears, approximatively, every 6 seconds.
I have found on
http://websvn.kde.org/branches/extragear/kde3/network/knetworkmanager
that there exists a version 0.2.1 of knetworkmanager with, in the
changelog:
Avoid a race on the DBus which sometimes prevents connection to wireless networks
but, I haven't been able to find a .rpm or a .tar.gz of that version.
Should I try to install, understand and use the svn tools to recover that
version ? Would it fix one or both of my problems ?
Thanks for your help,
Eric Brunet