Bug#641424: iwlagn: fails to reconnect to WPA2-enterprise (Reason: 23)
Hi Miguel, I have already built kernel 3.0.0-1-amd64 with the required debugging symbols. I've rebooted into the debug kernel, and loaded the iwlagn module with debugging symbols enabled. Or so I think. [MV] I don't see much iwlagn debugging information in the log you sent me. Can you please load the iwlagn module with the following parameters: modprobe iwlagn debug=0x43FFF Thanks, Meenakshi -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/c5a7fb31fd9aea42b600bdc3c74f8e0014ad3...@orsmsx511.amr.corp.intel.com
Bug#641424: iwlagn: fails to reconnect to WPA2-enterprise (Reason: 23)
I'm quite sure I loaded the module with debug information. It is not in the beginning of the debug log, since it connected to Eduroam before I rmmod'ed and modprobed iwlagn with the debug symbols enabled. Anyway, I'll try again tomorrow. -- Dr. Miguel Martinez Canales Department of Physics Astronomy University College London Gower Street, London, WC1E 6BT (UK) Fax: +44 207 679 0595 Tlf: +44 207 678 3476 If you have an apple and I have an apple and we exchange these apples then you and I will still each have one apple. But if you have an idea and I have an idea and we exchange these ideas, then each of us will have two ideas. George Bernard Shaw -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110926.17057.el.qu...@gmail.com
Bug#641424: iwlagn: fails to reconnect to WPA2-enterprise (Reason: 23)
Ok, here's some more info:
@Ben:
'wheezy' is the testing suite at the moment. Did you start from an
earlier installation of testing, or from stable ('squeeze')?
The original install is Squeeze (6.0.1a KDE media).
I don't think it's likely to be relevant, but could you test without the
'pcie_aspm=force' option?
I've done just this. Apparently, however, it doesn't change anything. I only
enabled this option to get better power savings, and since I don't exerience
lockups, it seemed to be safe.
@Meenakshi
The AP is, with 95% certainty, a Cisco Aironet 1200 series.
1) Enable debugging for the iwlwifi driver like so:
I've tried to do that after installing linux-image-3.0.0-1-amd64-dbg, but
modprobing with the debug option failed. Is there a lazy Debian way to get
the debug symbols without going all out compiling?
2) A wireless sniffer log would also be useful (not sure you're in a
position to gather this log).
I fear I have no experience with sniffers. Also, I wouldn't like to do
anything that could be interpreted as computer misuse, since this is my
workplace after all. Should this be okay, I'd need some guidance.
Regards,
Miguel
Bug#641424: iwlagn: fails to reconnect to WPA2-enterprise (Reason: 23)
Hi Miguel, 1) Enable debugging for the iwlwifi driver like so: I've tried to do that after installing linux-image-3.0.0-1-amd64-dbg, but modprobing with the debug option failed. Is there a lazy Debian way to get the debug symbols without going all out compiling? Check the kernel config file for the above kernel, and make sure that the following two options are set for the iwlwifi driver. # # Debugging Options # CONFIG_IWLWIFI_DEBUG=y CONFIG_IWLWIFI_DEBUGFS=y And that there is debugging for mac80211 as well. CONFIG_MAC80211_DEBUGFS=y CONFIG_MAC80211_DEBUG_MENU=y CONFIG_MAC80211_NOINLINE=y CONFIG_MAC80211_VERBOSE_DEBUG=y CONFIG_MAC80211_HT_DEBUG=y CONFIG_MAC80211_TKIP_DEBUG=y CONFIG_MAC80211_IBSS_DEBUG=y CONFIG_MAC80211_VERBOSE_PS_DEBUG=y CONFIG_MAC80211_DEBUG_COUNTERS=y CONFIG_MAC80211_DRIVER_API_TRACER=y If they're not set - you'll have to resort to compiling the kernel with debugging enabled. 2) A wireless sniffer log would also be useful (not sure you're in a position to gather this log). I fear I have no experience with sniffers. Also, I wouldn't like to do anything that could be interpreted as computer misuse, since this is my workplace after all. Should this be okay, I'd need some guidance. Don't worry about this for now. Try to get debugging information for the iwlwifi driver, mac80211, and network-manager (if possible). Also, what kernel version is your Ubuntu 10.10 system using? Thanks, Meenakshi
Bug#641424: iwlagn: fails to reconnect to WPA2-enterprise (Reason: 23)
OK, thanks for the tip. Debian kernel 3.0.0-1 doesn't have these options enabled, so I'll get to know how good the debian kernel build tools are. $ grep CONFIG_IWLWIFI /boot/config-3.0.0-1-amd64 | grep -i debug # CONFIG_IWLWIFI_DEBUG is not set # CONFIG_IWLWIFI_LEGACY_DEBUG is not set $ grep CONFIG_MAC80211 /boot/config-3.0.0-1-amd64 CONFIG_MAC80211=m CONFIG_MAC80211_HAS_RC=y CONFIG_MAC80211_RC_MINSTREL=y CONFIG_MAC80211_RC_MINSTREL_HT=y CONFIG_MAC80211_RC_DEFAULT_MINSTREL=y CONFIG_MAC80211_RC_DEFAULT=minstrel_ht CONFIG_MAC80211_MESH=y CONFIG_MAC80211_LEDS=y # CONFIG_MAC80211_DEBUGFS is not set # CONFIG_MAC80211_DEBUG_MENU is not set CONFIG_MAC80211_HWSIM=m Also, Ubuntu 10.10 has kernel 2.6.35, with some extra sauce and backports. I've seen some mentions of 2.6.38 in the changelogs. The iwlagn entries mention only some rfkill changes, though. Regards, Miguel -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201109142353.35030.el.qu...@gmail.com
Bug#641424: iwlagn: fails to reconnect to WPA2-enterprise (Reason: 23)
On Wed, Sep 14, 2011 at 11:53:34PM +0100, Miguel Martínez wrote: OK, thanks for the tip. Debian kernel 3.0.0-1 doesn't have these options enabled, so I'll get to know how good the debian kernel build tools are. [...] The kernel handbook should help you with this: http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110914233320.gn2...@decadent.org.uk
Bug#641424: iwlagn: fails to reconnect to WPA2-enterprise (Reason: 23)
Package: linux-2.6 Version: 3.0.0-3 Severity: normal Dear Maintainer, My laptop (T400, Intel WiFi Link 5300) is connected at university using Eduroam, an WPA2-enterprise network. After configuring the interface (either KDE or Gnome2 versions of network-manager), a connection will be established. After a while, however, the connection will be dropped (local reason 3), and will not be reestablished (Reason: 23) after an indefinite number of attempts. Apparently, nm is not able to renew the IP. From the dmesg output, it seems the wifi card is struggling to decide which of two AP it should connect to. Extract from dmesg right after the first disconnect: [ 817.555025] wlan0: deauthenticating from 00:16:9d:7c:97:02 by local choice (reason=3) [ 817.565665] cfg80211: Calling CRDA to update world regulatory domain [ 817.575513] wlan0: authenticate with 00:16:c7:71:a1:42 (try 1) [ 817.578148] wlan0: authenticated [ 817.579185] cfg80211: World regulatory domain updated: [ 817.579192] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 817.579200] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 817.579209] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [ 817.579216] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [ 817.579224] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 817.579232] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 817.580656] wlan0: associate with 00:16:c7:71:a1:42 (try 1) [ 817.583046] wlan0: RX AssocResp from 00:16:c7:71:a1:42 (capab=0x431 status=0 aid=78) [ 817.583049] wlan0: associated [ 818.626062] wlan0: deauthenticated from 00:16:c7:71:a1:42 (Reason: 23) [ 818.634705] cfg80211: Calling CRDA to update world regulatory domain [ 818.644952] cfg80211: World regulatory domain updated: [ 818.644960] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 818.644969] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 818.644977] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [ 818.644985] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [ 818.644993] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 818.645000] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 821.971502] wlan0: authenticate with 00:16:9d:7c:97:02 (try 1) [ 821.974151] wlan0: authenticated [ 821.977578] wlan0: associate with 00:16:9d:7c:97:02 (try 1) [ 821.979659] wlan0: RX AssocResp from 00:16:9d:7c:97:02 (capab=0x431 status=0 aid=205) [ 821.979668] wlan0: associated [ 823.018591] wlan0: deauthenticated from 00:16:9d:7c:97:02 (Reason: 23) Disabling and reenabling the network helps to reconnect to Eduroam, but will not last for long, repeating the pattern described above. I first thought it was an issue with knetwork-manager in Wheezy's KDE [1], so I upgraded to testing. The issue remains in all kernels I've tried. I've also tried installing Gnome 2.32 from testing and using nm-applet. Following suggestions in some bug reports [2], I've tried disabling 11n and/or disabling power management (seems to be off in any case), but it doesn't help. This is all more puzzling, since my Ubuntu 10.10 partition has no such problems with Eduroam. I should note that Ubuntu 10.10 does disable 11n, but it's reenabled for 11.04 and later. I will try OpenSUSE 11.4 from a live USB to see if the problem also exists there. Finally, it should be mentioned that WPA2 at home works without issues, and with 11n enabled (where I'm writing this from). Regards, Miguel [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594452 [2] https://bugs.launchpad.net/ubuntu/maverick/+source/linux-firmware/+bug/630748 -- Package-specific info: ** Version: Linux version 3.0.0-1-amd64 (Debian 3.0.0-3) (b...@decadent.org.uk) (gcc version 4.5.3 (Debian 4.5.3-8) ) #1 SMP Sat Aug 27 16:21:11 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.0.0-1-amd64 root=UUID=26d17817-1add-4b72-8386-1039a90eb83a ro quiet acpi_sleep=sci_force_enable intel_iommu=on pcie_aspm=force ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [8.266036] yenta_cardbus :15:00.0: CardBus bridge found [17aa:20c6] [8.392804] yenta_cardbus :15:00.0: ISA IRQ mask 0x0cb8, PCI irq 16 [8.392809] yenta_cardbus :15:00.0: Socket status: 3006 [8.392816] yenta_cardbus :15:00.0: pcmcia: parent PCI bridge window: [io 0x4000-0x7fff] [8.392819] yenta_cardbus :15:00.0: pcmcia: parent PCI bridge window: [mem 0xf480-0xf7ff] [8.392823] pcmcia_socket pcmcia_socket0: cs: memory probe 0xf480-0xf7ff: excluding 0xf480-0xf4b7 [8.392837] yenta_cardbus :15:00.0: pcmcia: parent PCI bridge window: [mem 0xf000-0xf3ff 64bit pref] [
Bug#641424: iwlagn: fails to reconnect to WPA2-enterprise (Reason: 23)
[The previous message is logged at http://bugs.debian.org/641424.]
On Tue, 2011-09-13 at 12:15 +0100, Miguel Martinez wrote:
Package: linux-2.6
Version: 3.0.0-3
Severity: normal
Dear Maintainer,
My laptop (T400, Intel WiFi Link 5300) is connected at university using
Eduroam, an WPA2-enterprise network. After configuring the interface
(either KDE or Gnome2 versions of network-manager), a connection will
be established. After a while, however, the connection will be dropped
(local reason 3), and will not be reestablished (Reason: 23) after an
indefinite number of attempts. Apparently, nm is not able to renew the
IP.
From the dmesg output, it seems the wifi card is struggling to decide
which of two AP it should connect to. Extract from dmesg right after the
first disconnect:
I think that's a symptom, not a cause of the failure.
[ 817.555025] wlan0: deauthenticating from 00:16:9d:7c:97:02 by local choice
(reason=3)
[ 817.565665] cfg80211: Calling CRDA to update world regulatory domain
[ 817.575513] wlan0: authenticate with 00:16:c7:71:a1:42 (try 1)
[ 817.578148] wlan0: authenticated
[ 817.579185] cfg80211: World regulatory domain updated:
[ 817.579192] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[ 817.579200] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300
mBi, 2000 mBm)
[ 817.579209] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300
mBi, 2000 mBm)
[ 817.579216] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300
mBi, 2000 mBm)
[ 817.579224] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300
mBi, 2000 mBm)
[ 817.579232] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300
mBi, 2000 mBm)
[ 817.580656] wlan0: associate with 00:16:c7:71:a1:42 (try 1)
[ 817.583046] wlan0: RX AssocResp from 00:16:c7:71:a1:42 (capab=0x431
status=0 aid=78)
[ 817.583049] wlan0: associated
[ 818.626062] wlan0: deauthenticated from 00:16:c7:71:a1:42 (Reason: 23)
[ 818.634705] cfg80211: Calling CRDA to update world regulatory domain
[ 818.644952] cfg80211: World regulatory domain updated:
[ 818.644960] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[ 818.644969] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300
mBi, 2000 mBm)
[ 818.644977] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300
mBi, 2000 mBm)
[ 818.644985] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300
mBi, 2000 mBm)
[ 818.644993] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300
mBi, 2000 mBm)
[ 818.645000] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300
mBi, 2000 mBm)
[ 821.971502] wlan0: authenticate with 00:16:9d:7c:97:02 (try 1)
[ 821.974151] wlan0: authenticated
[ 821.977578] wlan0: associate with 00:16:9d:7c:97:02 (try 1)
[ 821.979659] wlan0: RX AssocResp from 00:16:9d:7c:97:02 (capab=0x431
status=0 aid=205)
[ 821.979668] wlan0: associated
[ 823.018591] wlan0: deauthenticated from 00:16:9d:7c:97:02 (Reason: 23)
Disabling and reenabling the network helps to reconnect to Eduroam, but
will not last for long, repeating the pattern described above.
I first thought it was an issue with knetwork-manager in Wheezy's KDE
[1], so I upgraded to testing.
'wheezy' is the testing suite at the moment. Did you start from an
earlier installation of testing, or from stable ('squeeze')?
The issue remains in all kernels I've
tried. I've also tried installing Gnome 2.32 from testing and using
nm-applet.
Following suggestions in some bug reports [2], I've tried disabling 11n
and/or disabling power management (seems to be off in any case), but it
doesn't help. This is all more puzzling, since my Ubuntu 10.10 partition
has no such problems with Eduroam. I should note that Ubuntu 10.10 does
disable 11n, but it's reenabled for 11.04 and later. I will try OpenSUSE
11.4 from a live USB to see if the problem also exists there.
Finally, it should be mentioned that WPA2 at home works without issues,
and with 11n enabled (where I'm writing this from).
Regards,
Miguel
[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594452
[2]
https://bugs.launchpad.net/ubuntu/maverick/+source/linux-firmware/+bug/630748
-- Package-specific info:
** Version:
Linux version 3.0.0-1-amd64 (Debian 3.0.0-3) (b...@decadent.org.uk) (gcc
version 4.5.3 (Debian 4.5.3-8) ) #1 SMP Sat Aug 27 16:21:11 UTC 2011
** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.0.0-1-amd64
root=UUID=26d17817-1add-4b72-8386-1039a90eb83a ro quiet
acpi_sleep=sci_force_enable intel_iommu=on pcie_aspm=force
[...]
I don't think it's likely to be relevant, but could you test without the
'pcie_aspm=force' option?
Ben.
--
Ben Hutchings
To err is human; to really foul things up requires a computer.
signature.asc
Description: This is a digitally signed message part
Bug#641424: iwlagn: fails to reconnect to WPA2-enterprise (Reason: 23)
On Tue, 2011-09-13 at 16:33 -0700, Venkataraman, Meenakshi wrote: Hi Miguel, It looks like the AP you're connected to at the University is a Cisco AP. I'm not sure what reason code 23 is, will need to research it some. WLAN_REASON_IEEE8021X_FAILED = 23, In the meantime, can you do the following so we can see what's going on in the iwlwifi driver: 1) Enable debugging for the iwlwifi driver like so: modprobe iwlagn debug=0x47fff You'll need to enable debugging for iwlwifi while building the kernel. 2) A wireless sniffer log would also be useful (not sure you're in a position to gather this log). Please send me (only) the log. We can take this to bugzilla as well. [...] If you mean bugzilla.kernel.org, that is currently down along with much of the kernel.org infrastructure. Ben. -- Ben Hutchings All extremists should be taken out and shot. signature.asc Description: This is a digitally signed message part
Bug#641424: iwlagn: fails to reconnect to WPA2-enterprise (Reason: 23)
Thanks for the reason code info, Ben, I meant that we could continue on the Debian bugzilla. Or, you can post it to: http://bugzilla.intellinuxwireless.org/ -- the bugzilla for the iwlwifi driver + currently supported devices. Thanks, meenakshi -Original Message- From: Ben Hutchings [mailto:b...@decadent.org.uk] Sent: Tuesday, September 13, 2011 4:41 PM To: Venkataraman, Meenakshi Cc: Miguel Martinez; 641...@bugs.debian.org; linux-wireless Subject: RE: Bug#641424: iwlagn: fails to reconnect to WPA2-enterprise (Reason: 23) On Tue, 2011-09-13 at 16:33 -0700, Venkataraman, Meenakshi wrote: Hi Miguel, It looks like the AP you're connected to at the University is a Cisco AP. I'm not sure what reason code 23 is, will need to research it some. WLAN_REASON_IEEE8021X_FAILED = 23, In the meantime, can you do the following so we can see what's going on in the iwlwifi driver: 1) Enable debugging for the iwlwifi driver like so: modprobe iwlagn debug=0x47fff You'll need to enable debugging for iwlwifi while building the kernel. 2) A wireless sniffer log would also be useful (not sure you're in a position to gather this log). Please send me (only) the log. We can take this to bugzilla as well. [...] If you mean bugzilla.kernel.org, that is currently down along with much of the kernel.org infrastructure. Ben. -- Ben Hutchings All extremists should be taken out and shot.
Bug#641424: iwlagn: fails to reconnect to WPA2-enterprise (Reason: 23)
Hi Miguel,
It looks like the AP you're connected to at the University is a Cisco AP. I'm
not sure what reason code 23 is, will need to research it some.
In the meantime, can you do the following so we can see what's going on in the
iwlwifi driver:
1) Enable debugging for the iwlwifi driver like so:
modprobe iwlagn debug=0x47fff
You'll need to enable debugging for iwlwifi while building the kernel.
2) A wireless sniffer log would also be useful (not sure you're in a position
to gather this log).
Please send me (only) the log. We can take this to bugzilla as well.
Thanks,
Meenakshi
-Original Message-
From: linux-wireless-ow...@vger.kernel.org [mailto:linux-wireless-
ow...@vger.kernel.org] On Behalf Of Ben Hutchings
Sent: Tuesday, September 13, 2011 3:29 PM
To: Miguel Martinez
Cc: 641...@bugs.debian.org; linux-wireless
Subject: Re: Bug#641424: iwlagn: fails to reconnect to WPA2-enterprise
(Reason: 23)
[The previous message is logged at http://bugs.debian.org/641424.]
On Tue, 2011-09-13 at 12:15 +0100, Miguel Martinez wrote:
Package: linux-2.6
Version: 3.0.0-3
Severity: normal
Dear Maintainer,
My laptop (T400, Intel WiFi Link 5300) is connected at university
using Eduroam, an WPA2-enterprise network. After configuring the
interface (either KDE or Gnome2 versions of network-manager), a
connection will be established. After a while, however, the connection
will be dropped (local reason 3), and will not be reestablished
(Reason: 23) after an indefinite number of attempts. Apparently, nm is
not able to renew the IP.
From the dmesg output, it seems the wifi card is struggling to decide
which of two AP it should connect to. Extract from dmesg right after
the first disconnect:
I think that's a symptom, not a cause of the failure.
[ 817.555025] wlan0: deauthenticating from 00:16:9d:7c:97:02 by local
choice (reason=3) [ 817.565665] cfg80211: Calling CRDA to update
world regulatory domain [ 817.575513] wlan0: authenticate with
00:16:c7:71:a1:42 (try 1) [ 817.578148] wlan0: authenticated [
817.579185] cfg80211: World regulatory domain updated:
[ 817.579192] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[ 817.579200] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300
mBi, 2000 mBm)
[ 817.579209] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300
mBi, 2000 mBm)
[ 817.579216] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300
mBi, 2000 mBm)
[ 817.579224] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300
mBi, 2000 mBm)
[ 817.579232] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300
mBi, 2000 mBm)
[ 817.580656] wlan0: associate with 00:16:c7:71:a1:42 (try 1) [
817.583046] wlan0: RX AssocResp from 00:16:c7:71:a1:42 (capab=0x431
status=0 aid=78) [ 817.583049] wlan0: associated [ 818.626062]
wlan0: deauthenticated from 00:16:c7:71:a1:42 (Reason: 23) [
818.634705] cfg80211: Calling CRDA to update world regulatory domain [
818.644952] cfg80211: World regulatory domain updated:
[ 818.644960] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[ 818.644969] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300
mBi, 2000 mBm)
[ 818.644977] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300
mBi, 2000 mBm)
[ 818.644985] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300
mBi, 2000 mBm)
[ 818.644993] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300
mBi, 2000 mBm)
[ 818.645000] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300
mBi, 2000 mBm)
[ 821.971502] wlan0: authenticate with 00:16:9d:7c:97:02 (try 1) [
821.974151] wlan0: authenticated [ 821.977578] wlan0: associate with
00:16:9d:7c:97:02 (try 1) [ 821.979659] wlan0: RX AssocResp from
00:16:9d:7c:97:02 (capab=0x431 status=0 aid=205) [ 821.979668] wlan0:
associated [ 823.018591] wlan0: deauthenticated from
00:16:9d:7c:97:02 (Reason: 23)
Disabling and reenabling the network helps to reconnect to Eduroam,
but will not last for long, repeating the pattern described above.
I first thought it was an issue with knetwork-manager in Wheezy's KDE
[1], so I upgraded to testing.
'wheezy' is the testing suite at the moment. Did you start from an earlier
installation of testing, or from stable ('squeeze')?
The issue remains in all kernels I've
tried. I've also tried installing Gnome 2.32 from testing and using
nm-applet.
Following suggestions in some bug reports [2], I've tried disabling
11n and/or disabling power management (seems to be off in any case),
but it doesn't help. This is all more puzzling, since my Ubuntu 10.10
partition has no such problems with Eduroam. I should note that Ubuntu
10.10 does disable 11n, but it's reenabled for 11.04 and later. I will
try OpenSUSE
11.4 from a live USB to see if the problem also exists there.
Finally, it should be mentioned that WPA2 at home works without
issues, and with 11n
Bug#641424: iwlagn: fails to reconnect to WPA2-enterprise (Reason: 23)
On Tue, 2011-09-13 at 16:41 -0700, Ben Hutchings wrote: On Tue, 2011-09-13 at 16:33 -0700, Venkataraman, Meenakshi wrote: Hi Miguel, It looks like the AP you're connected to at the University is a Cisco AP. I'm not sure what reason code 23 is, will need to research it some. WLAN_REASON_IEEE8021X_FAILED = 23, In the meantime, can you do the following so we can see what's going on in the iwlwifi driver: 1) Enable debugging for the iwlwifi driver like so: modprobe iwlagn debug=0x47fff You'll need to enable debugging for iwlwifi while building the kernel. 2) A wireless sniffer log would also be useful (not sure you're in a position to gather this log). Please send me (only) the log. We can take this to bugzilla as well. [...] If you mean bugzilla.kernel.org, that is currently down along with much of the kernel.org infrastructure. please use http://bugzilla.intellinuxwireless.org Thanks Wey -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1315957121.2336.0.camel@wwguy-ubuntu
