Public bug reported: First, a disclaimer: I'm using a build of vpnc with OpenSSL enabled. I also don't know if it's a fault of vpn, the kernel or what.
In order to connect to one of the WiFi networks at my current workplace I need to use SSL-enabled vpnc. However, after a while (this shortens if I use skype), the connection will drop and I won't be able to resume it. Output of dmesg gets spammed with these lines: [18019.050761] iwlagn 0000:03:00.0: No space for Tx [18019.050764] iwlagn 0000:03:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -28 [18019.050767] iwlagn 0000:03:00.0: Error setting new RXON (-28) [18019.050771] iwlagn 0000:03:00.0: No space for Tx [18019.050773] iwlagn 0000:03:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -28 [18019.050776] iwlagn 0000:03:00.0: Error setting new RXON (-28) [18019.050782] iwlagn 0000:03:00.0: No space for Tx [18019.050785] iwlagn 0000:03:00.0: Error sending REPLY_TX_POWER_DBM_CMD: enqueue_hcmd failed: -28 The only way to resume the connection is: # vpnc-disconnect # modprobe -r iwlagn # sudo modprobe iwlagn [wait for n-m to connect] # vpnc-connect This is on a ThinkPad T400 with the Intel WiFi link 5300. Well, that's what I bought, and that's what windows detects, although linux seems to detect the WiFi lin 5100 (identical except in the number of antennae, IIR). ProblemType: Bug Architecture: amd64 Date: Fri Feb 19 15:02:29 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) Package: vpnc 0.5.3-1 ProcEnviron: PATH=(custom, user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-19.56-generic SourcePackage: vpnc Uname: Linux 2.6.31-19-generic x86_64 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- iwlagn corrupts after using vpnc for a while https://bugs.launchpad.net/bugs/524471 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs