[Bug 924082] Re: Intel Centrino 6300 Cannot connect direct probe timed out
** Description changed: The iwlwifi drivers give exceptional performance on all APs I have connected to, be they WEP, WPA or open. The only time this system lets - me down is when connecting to my campus wireless network. Newtwork - manager will only sometimes connect, and even manually configuring with - iwconfig does not always work. + me down is when connecting to my campus wireless network. NetworkManager + will only sometimes connect, and even manually configuring with iwconfig + does not always work. The error usually given is either: + Jan 30 01:07:51 Beast kernel: [ 8777.748471] wlan0: direct probe to 00:1a:1e:a0:3b:c0 (try 1/3) Jan 30 01:07:51 Beast kernel: [ 8777.945384] wlan0: direct probe to 00:1a:1e:a0:3b:c0 (try 2/3) Jan 30 01:07:51 Beast kernel: [ 8778.144952] wlan0: direct probe to 00:1a:1e:a0:3b:c0 (try 3/3) Jan 30 01:07:52 Beast kernel: [ 8778.344474] wlan0: direct probe to 00:1a:1e:a0:3b:c0 timed out or: + Nov 30 19:01:27 Beast kernel: [ 1924.850725] wlan0: authenticate with 00:24:6c:60:d0:00 (try 1) Nov 30 19:01:27 Beast kernel: [ 1924.852183] wlan0: 00:24:6c:60:d0:00 denied authentication (status 17) - Other people report that this error may be linked to MAC filtering by the AP, but this should not be the case - my old computer with a Broadcom BCM4312 had no trouble. - This bug is also different to several bugs that complain of limited speed or packet loss - when I can connect, the connection is flawless. But very often I cannot. The connection is generally worse in crowded areas, or areas with many access points. + Other people report that this error may be linked to MAC filtering by + the AP, but this should not be the case: my old computer with a Broadcom + BCM4312 had no trouble. + + This bug is also different from several bug reports that complain of + limited speed or packet loss: when I can connect, the connection is + flawless. But very often I cannot connecct. The connection is generally + worse in crowded areas, or areas with many access points. lspci: Network controller [0280]: Intel Corporation Centrino Ultimate-N 6300 [8086:4238] (rev 3e) ifconfig wlan0: - wlan0 Link encap:Ethernet HWaddr 24:77:03:26:e8:50 - inet addr:130.64.153.137 Bcast:130.64.153.255 Mask:255.255.255.0 - inet6 addr: fe80::2677:3ff:fe26:e850/64 Scope:Link - UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 - RX packets:1288307 errors:0 dropped:0 overruns:0 frame:0 - TX packets:296448 errors:0 dropped:0 overruns:0 carrier:0 - collisions:0 txqueuelen:1000 - RX bytes:1016044127 (1.0 GB) TX bytes:27674773 (27.6 MB) - - iwconfig wlan0: - wlan0 IEEE 802.11abgn ESSID:"tuftswireless" - Mode:Managed Frequency:5.785 GHz Access Point: 00:24:6C:60:D0:10 - Bit Rate=300 Mb/s Tx-Power=15 dBm - Retry long limit:7 RTS thr:off Fragment thr:off - Power Management:off - Link Quality=61/70 Signal level=-49 dBm - Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 - Tx excessive retries:2749 Invalid misc:7 Missed beacon:0 + wlan0 Link encap:Ethernet HWaddr 24:77:03:26:e8:50 + inet addr:130.64.153.137 Bcast:130.64.153.255 Mask:255.255.255.0 + inet6 addr: fe80::2677:3ff:fe26:e850/64 Scope:Link + UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 + RX packets:1288307 errors:0 dropped:0 overruns:0 frame:0 + TX packets:296448 errors:0 dropped:0 overruns:0 carrier:0 + collisions:0 txqueuelen:1000 + RX bytes:1016044127 (1.0 GB) TX bytes:27674773 (27.6 MB) + + iwconfig wlan0: + wlan0 IEEE 802.11abgn ESSID:"tuftswireless" + Mode:Managed Frequency:5.785 GHz Access Point: 00:24:6C:60:D0:10 + Bit Rate=300 Mb/s Tx-Power=15 dBm + Retry long limit:7 RTS thr:off Fragment thr:off + Power Management:off + Link Quality=61/70 Signal level=-49 dBm + Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 + Tx excessive retries:2749 Invalid misc:7 Missed beacon:0 lsmod | grep iw: - iwlwifi 320164 0 + iwlwifi 320164 0 mac80211 506154 1 iwlwifi cfg80211 209294 2 iwlwifi,mac80211 - dmesg | grep wlan: [ 12.059405] wlan0: direct probe to 00:24:6c:60:d0:00 (try 1/3) [ 12.258109] wlan0: direct probe to 00:24:6c:60:d0:00 (try 2/3) [ 12.457695] wlan0: direct probe to 00:24:6c:60:d0:00 (try 3/3) [ 12.657205] wlan0: direct probe to 00:24:6c:60:d0:00 timed out [ 20.624778] wlan0: direct probe to 00:24:6c:60:d0:00 (try 1/3) [ 20.822683] wlan0: direct probe to 00:24:6c:60:d0:00 (try 2/3) [ 21.022217] wlan0: direct probe to 00:24:6c:60:d0:00 (try 3/3) [ 21.221788] wlan0: direct probe to 00:24:6c:60:d0:00 timed out [ 29.105117] wlan0: direct prob
[Bug 924082] Re: Intel Centrino 6300 Cannot connect direct probe timed out
I've been experiencing this same problem on my campus network for a while, and switching to WICD seems to have fixed it for me, too! I think it's worth noting that the access points on my campus are Aruba Networks access points, and we use the SafeConnect system for network authentication. We actually run two networks: the campus network, and a guest network. The guest network bypasses authentication through SafeConnect to allow guests to hop on the campus wireless (with some access restrictions). I have never had any trouble connecting to the guest network with NetworkManager, but almost always got the "Status 17" error when connecting to the campus network. I've attempted to research this issue before, and seem to recall something about this being specific to Aruba Networks access points. http://ubuntuforums.org/showthread.php?t=1889157 seems to make that connection, and points to a bug filed with the intel wireless drivers: http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2346 . In any case, WICD does seem to work as a workaround! ** Bug watch added: bugzilla.intellinuxwireless.org/ #2346 http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2346 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/924082 Title: Intel Centrino 6300 Cannot connect direct probe timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/924082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 924082] Re: Intel Centrino 6300 Cannot connect direct probe timed out
I can confirm that switching to WICD fixes the problem for me partially - I see a large number of APs for the same SSID, and can always connect to at least one of them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/924082 Title: Intel Centrino 6300 Cannot connect direct probe timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/924082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 924082] Re: Intel Centrino 6300 Cannot connect direct probe timed out
This bug affects me too. Can anybody confirm that wicd solves the problem? Cheers, S. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/924082 Title: Intel Centrino 6300 Cannot connect direct probe timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/924082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 924082] Re: Intel Centrino 6300 Cannot connect direct probe timed out
I can confirm this bug. I have an intel advanced N 6320 card and I get the same direct probe failure messages on my campus wifi. The network works fine in windows and on my phone/tablet, but I cannot connect when using network-manager. I'll try wicd as suggested to confirm the issue is in network-manager. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/924082 Title: Intel Centrino 6300 Cannot connect direct probe timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/924082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 924082] Re: Intel Centrino 6300 Cannot connect direct probe timed out
** Changed in: network-manager (Ubuntu) Status: Incomplete => Confirmed ** Changed in: network-manager (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/924082 Title: Intel Centrino 6300 Cannot connect direct probe timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/924082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 924082] Re: Intel Centrino 6300 Cannot connect direct probe timed out
When I was using network-manager, I could connect fine to every network except the campus network, which is composed of a ton of APs everywhere. When trying to connect to the campus network I would usually get the following: [ 12.059405] wlan0: direct probe to 00:24:6c:60:d0:00 (try 1/3) [ 12.258109] wlan0: direct probe to 00:24:6c:60:d0:00 (try 2/3) [ 12.457695] wlan0: direct probe to 00:24:6c:60:d0:00 (try 3/3) [ 12.657205] wlan0: direct probe to 00:24:6c:60:d0:00 timed out This was a much more common error than status 17. After displaying this message, nm-applet would show the connecting icon until something timed out. Periodically it could connect, but would usually drop the connection. The fact that after replacing nm with wicd completely resolved the problem leads me to believe that it was a bug in nm, and not a hardware problem - under Win7 and now with wicd, there are zero connection issues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/924082 Title: Intel Centrino 6300 Cannot connect direct probe timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/924082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 924082] Re: Intel Centrino 6300 Cannot connect direct probe timed out
Sorry -- there's just really nothing in that bug report that supports this. If you can, please test with a different card or whatnot, but there's still no reason to believe a success might then be because it's the different card. Didn't you mention you sometimes successfully connect? Stating the description: "when I can connect, the connection is flawless. But very often I cannot. The connection is generally worse in crowded areas, or areas with many access points." With the additional information that it's usually worse in crowded areas or when there are many access points (many access points is generally indicative that the area may be crowded to a point that multiple APs are required to support all the clients), it's further evidence that this is just contention on the AP side. There are however known problems with N on this kind of card, so I guess it's technically possible you'd be seeing a different side-effect of the performance issues with N -- but you also mentioned this was different from the other performance-related bug reports. Finally, this being the only network where you reportedly encounter this particular issue, there is again then no evidence to suggest it's not environment-related. I'm willing to consider this might be a bug in NM, but those would normally affect all wireless networks indiscriminately considering NM only asks the kernel via wpasupplicant to establish connections and does minimal house-keeping for the connection. Everything else is done by the kernel. I'll reset this to Incomplete. Please see if you can provide further information that would point this clearly in the direction of a software bug. ** Changed in: network-manager (Ubuntu) Status: Invalid => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/924082 Title: Intel Centrino 6300 Cannot connect direct probe timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/924082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 924082] Re: Intel Centrino 6300 Cannot connect direct probe timed out
The only thing is - this is a problem in network-manager. My previous network card had no trouble, and having installed wicd I have never seen this problem. I don't think that this is an overcrowding issue, and that there is still an issue with network-manager. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/924082 Title: Intel Centrino 6300 Cannot connect direct probe timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/924082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 924082] Re: Intel Centrino 6300 Cannot connect direct probe timed out
Thank you for filing this bug report and helping to make Ubuntu better. Your syslog excerpt explains precisely why the connection times out and authentication is denied while trying to connect: there's an error response from the accesspoint, in the form of the "status 17" message. I understand this is quite cryptic. Status 17 is defined as "Association denied because AP is unable to handle additional associated STAs" in the IEEE 802.11-2007 standard. I basically means that the authentication was denied because the accesspoint cannot handle additional "stations" to be connected to it. Stations are any wireless client that might try to connect. As a solution, the best I can offer is to suggest you contact your network's administrators and point to this bug report as an additional indication that the network is crowded. Closing as Invalid since it's not a bug in Ubuntu. Please, don't hesitate to report bugs for any further issues you may find! :) ** Changed in: network-manager (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/924082 Title: Intel Centrino 6300 Cannot connect direct probe timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/924082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
