[Gutsy] WPA2 connection drops with ipw3945

[Sebastian Bergmann]

I am using Ubuntu Gutsy on an IBM ThinkPad X60s which has an ipw3945 WLAN chip.

When connecting to a WLAN that uses no encryption or WEP encryption, everything is fine.

When connecting to a WLAN that uses WPA2 encryption, the connection drops after 5-10 seconds. The connection can then only be restored by running "/etc/init.d/network restart".

[Marco Rodrigues (gothicx)]

What version of Gutsy are you using ?

[Sebastian Bergmann (sb-sebastian-bergmann)]

I update my Gutsy installation daily (aptitude update && aptitude dist-upgrade) so I am using the latest packages.

[Sebastian Urban (surban)]

Same problem here on a ThinkPad R61i using WPA2. However the problem does only appear every 20 minutes or so. Difficult to reproduce.

It seems related to the regulatory daemon. dmesg shows the following messages after the connection has dropped:

[ 5496.324000] ipw3945: Error sending cmd #07 to daemon: time out after 500ms.
[ 5684.260000] ipw3945: Error sending cmd #07 to daemon: time out after 500ms.
[ 5702.880000] ipw3945: Error sending DAEMON: Already sending a synchronous daemon command
[ 5702.880000] ipw3945: Error sending DAEMON: Already sending a synchronous daemon command

Reconnection is possible after killing and restarting ipw3945d.

Running gutsy with latest updates. Problem seems related to high cpu/memory (pherhaps caused by swapping?) use.

[Marco Rodrigues (gothicx)]

You still have the same problem with Gutsy Beta ?

[Sebastian Urban (surban)]

For me it seems to be fixed. I will report back if it happens again.

[Sebastian Urban (surban)]

Sorry, that was too early.

Connection dropped after about ~4 hours of use. dmesg messages same as above.

However this time many programs stopped working after the disconnect, i.e. sudo, login, ifconfig, iwconfig, etc. hung. However shutdown by pressing CTRL+ALT+DEL in the text console was possible.

[Sark (steve-samson-solutions)]

I have the same problem, however it is not just limited to WPA. It also happens with no encryption and WEP.....however randomly.

This is the output from my syslog

Oct 19 20:18:46 Computer racoon: INFO: IPsec-SA expired: ESP/Tunnel <Modified for posting>[0]-><Modified for posting>[0] spi=31983423223(0xbafe4321)
Oct 19 20:44:48 Computer kernel: [34148.332000] ipw3945: Error sending DAEMON: Already sending a synchronous daemon command
Oct 19 20:44:49 Computer kernel: [34149.892000] ipw3945: Error sending DAEMON: Already sending a synchronous daemon command
Oct 19 20:46:52 Computer kernel: [34272.776000] ipw3945: Error sending DAEMON: Already sending a synchronous daemon command
Oct 19 20:46:52 Computer kernel: [34272.776000] ipw3945: Error sending DAEMON: Already sending a synchronous daemon command
Oct 19 20:49:53 Computer racoon: ERROR: KA: sendfromto failed: Network is unreachable
Oct 19 20:49:53 Computer NetworkManager: <debug> [1192841393.715228] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/net_00_1b_77_4b_e5_b8').
Oct 19 20:49:53 Computer NetworkManager: <info> Deactivating device eth1.

As you can see I have a site-to-site VPN setup with keep-alive enabled. Everything is working perfectly fine and then it just stops. I have a T61 with a IBM Intel 3945 card, running Gutsy from Tribe 1 to current today (19 Oct 07). I just removed NetworkManager hopefully that will fix it.

[Sark (steve-samson-solutions)]

This continues to occur. Not just with WPA, but WEP, and OPEN

Oct 30 13:45:54 Computer kernel: [ 8982.636000] ipw3945: Error sending cmd #07 to daemon: time out after 500ms.
Oct 30 13:45:55 Computer kernel: [ 8984.236000] ipw3945: Error sending SCAN_ABORT_CMD: time out after 500ms.
Oct 30 13:45:56 Computer kernel: [ 8984.736000] ipw3945: Error sending cmd #08 to daemon: time out after 500ms.
Oct 30 13:45:56 Computer kernel: [ 8985.236000] ipw3945: Error sending ADD_STA: time out after 500ms.
Oct 30 13:45:57 Computer kernel: [ 8985.736000] ipw3945: Error sending SCAN_ABORT_CMD: time out after 500ms.

Does anyone see the below in their logs?

Oct 30 13:44:59 Computer dhclient: DHCPREQUEST on eth1 to 66.34.23.123 port 67
Oct 30 13:45:48 Computer last message repeated 3 times

I see this all over the place as if my network card is continuously doing DHCP requests. My other cards do not do this.

[Andres Mujica (andres.mujica)]

This is a duplicate of Bug #109887 . Please provide any further comments to this bug. Thanks