I'm using Debian/sid with a custom-built kernel (version
2.6.25.4) and networkmanager 0.6.6 from the Debian repositories. My wireless network card is an Intel 3945ABG. I'm using the iwl3945 driver that is included with the kernel.
Setting up the internet connection using nm-applet to my wireless network with WPA encryption works seamlessly. Instead of shutting down my laptop I am normally just sending it to sleep in order to quickly have it back up when I need it. The only problem comes up right after waking up: Reconnecting to my wireless network takes usually more than one minute - a really annoying issue. Checking /var/log/syslog the output of NM shows the following:
Jul 18 19:32:29 Kati-PC NetworkManager: <info> Waking up from sleep.
Jul 18 19:32:29 Kati-PC NetworkManager: <info> Deactivating device eth1.
Jul 18 19:32:29 Kati-PC NetworkManager: <info> Deactivating device eth0.
Jul 18 19:32:29 Kati-PC kernel: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 18 19:32:29 Kati-PC NetworkManager: <info> eth1: Device is fully-supported using driver 'iwl3945'.
Jul 18 19:32:29 Kati-PC NetworkManager: <info> eth1: driver supports SSID scans (scan_capa 0x01).
Jul 18 19:32:29 Kati-PC NetworkManager: <info> nm_device_init(): waiting for device's worker thread to start
Jul 18 19:32:29 Kati-PC NetworkManager: <info> nm_device_init(): device's worker thread started, continuing.
Jul 18 19:32:29 Kati-PC NetworkManager: <info> Now managing wireless (802.11) device 'eth1'.
Jul 18 19:32:29 Kati-PC NetworkManager: <info> Deactivating device eth1.
Jul 18 19:32:29 Kati-PC kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 18 19:32:29 Kati-PC NetworkManager: <info> eth0: Device is fully-supported using driver 'e100'.
Jul 18 19:32:29 Kati-PC NetworkManager: <info> nm_device_init(): waiting for device's worker thread to start
Jul 18 19:32:29 Kati-PC NetworkManager: <info> nm_device_init(): device's worker thread started, continuing.
Jul 18 19:32:29 Kati-PC NetworkManager: <info> Now managing wired Ethernet (802.3) device 'eth0'.
Jul 18 19:32:29 Kati-PC NetworkManager: <info> Deactivating device eth0.
Jul 18 19:33:39 Kati-PC NetworkManager: <info> SWITCH: no current connection, found better connection 'eth1'.
Jul 18 19:33:39 Kati-PC NetworkManager: <info> Will activate connection 'eth1/WLAN-Caste'.
Jul 18 19:33:39 Kati-PC NetworkManager: <info> Device eth1 activation scheduled...
Jul 18 19:33:39 Kati-PC NetworkManager: <info> Activation (eth1) started...
Jul 18 19:33:39 Kati-PC NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Jul 18 19:33:39 Kati-PC NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Jul 18 19:33:39 Kati-PC NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Jul 18 19:33:39 Kati-PC NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Jul 18 19:33:39 Kati-PC NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Jul 18 19:33:39 Kati-PC NetworkManager: <info> Activation (eth1/wireless): access point 'WLAN-Caste' is encrypted, and a key exists. No new key needed.
..and so on. After this, a connection is successfully established. Note that between "Jul 18 19:32:29 Kati-PC NetworkManager: <info> Deactivating device eth0." and the next message "Jul 18 19:33:39 Kati-PC NetworkManager: <info> SWITCH: no current connection, found better connection 'eth1'." 1 minute and 10 seconds have passed (though this time period varies). Btw., when trying to scan for wireless networks within this time period using "iwlist eth1 scan", it shows me all available networks correctly. Trying to manually reconnect using the nm-applet is not possible as it does not show any wireless networks until it reconnects.
I have another laptop, though with an Intel 2200 wireless card, but the same kernel version and OS, and there this time period is usually down to only 10 seconds or so, making it reconnect much faster.
Is there any way, any setting to speed up reconnecting? This is really the only issue I encounter, otherwise NM works just great.
