You are not logged in.
Hello,
I am asking for help with a strange problem I have connecting to my mobile hotspot. It is one of those devices which connect you to the 3G/4G network by acting as an AP; the model is a Onda PN51T. It used to work fine with my pc, running Arch Linux perfectly updated as of this writing, and it does work fine when used by a Debian pc, or even a Windows 7 box. But now, on Arch, it loops forever, asking for the password over and over again.
I have the following perplexing output:
dmesg -T | tail -n 20
[Fri May 17 00:55:15 2013] wlan0: send auth to 00:24:6f:06:af:53 (try 1/3)
[Fri May 17 00:55:15 2013] wlan0: send auth to 00:24:6f:06:af:53 (try 2/3)
[Fri May 17 00:55:15 2013] wlan0: authenticated
[Fri May 17 00:55:15 2013] wlan0: associate with 00:24:6f:06:af:53 (try 1/3)
[Fri May 17 00:55:15 2013] wlan0: RX AssocResp from 00:24:6f:06:af:53 (capab=0x431 status=0 aid=1)
[Fri May 17 00:55:15 2013] wlan0: HT AP is missing WMM params or HT capability/operation in AssocResp
[Fri May 17 00:55:19 2013] wlan0: authenticate with 00:24:6f:06:af:53
[Fri May 17 00:55:19 2013] wlan0: send auth to 00:24:6f:06:af:53 (try 1/3)
[Fri May 17 00:55:19 2013] wlan0: send auth to 00:24:6f:06:af:53 (try 2/3)
[Fri May 17 00:55:19 2013] wlan0: authenticated
[Fri May 17 00:55:19 2013] wlan0: associate with 00:24:6f:06:af:53 (try 1/3)
[Fri May 17 00:55:19 2013] wlan0: RX AssocResp from 00:24:6f:06:af:53 (capab=0x431 status=0 aid=1)
[Fri May 17 00:55:19 2013] wlan0: HT AP is missing WMM params or HT capability/operation in AssocResp
[Fri May 17 00:55:23 2013] wlan0: authenticate with 00:24:6f:06:af:53
[Fri May 17 00:55:23 2013] wlan0: send auth to 00:24:6f:06:af:53 (try 1/3)
[Fri May 17 00:55:23 2013] wlan0: send auth to 00:24:6f:06:af:53 (try 2/3)
[Fri May 17 00:55:23 2013] wlan0: authenticated
[Fri May 17 00:55:23 2013] wlan0: associate with 00:24:6f:06:af:53 (try 1/3)
[Fri May 17 00:55:24 2013] wlan0: RX AssocResp from 00:24:6f:06:af:53 (capab=0x431 status=0 aid=1)
[Fri May 17 00:55:24 2013] wlan0: HT AP is missing WMM params or HT capability/operation in AssocResp
A search for the output :
HT AP is missing WMM params or HT capability/operation in AssocResp
in Google yielded nothing. On the other hand, this output
sudo iw dev wlan0 scan
.......
BSS 00:24:6f:06:af:53(on wlan0)
TSF: 407199934 usec (0d, 00:06:47)
freq: 2457
beacon interval: 100 TUs
capability: ESS Privacy ShortPreamble ShortSlotTime (0x0431)
signal: -17.00 dBm
last seen: 5503 ms ago
Information elements from Probe Response frame:
SSID: TIM_PN51T_AF53
Supported rates: 1.0* 2.0* 5.5* 6.0 9.0 11.0* 12.0 18.0
DS Parameter set: channel 10
Country: IT Environment: bogus
Channels [1 - 13] @ 20 dBm
ERP: <no flags>
Extended supported rates: 24.0 36.0 48.0 54.0
HT capabilities:
Capabilities: 0x2c
HT20
SM Power Save disabled
RX HT20 SGI
No RX STBC
Max AMSDU length: 3839 bytes
No DSSS/CCK HT40
Maximum RX AMPDU length 8191 bytes (exponent: 0x000)
Minimum RX AMPDU time spacing: No restriction (0x00)
HT RX MCS rate indexes supported: 0-7
HT TX MCS rate indexes are undefined
HT operation:
* primary channel: 10
* secondary channel offset: no secondary
* STA channel width: 20 MHz
* RIFS: 0
* HT protection: no
* non-GF present: 0
* OBSS non-GF present: 0
* dual beacon: 0
* dual CTS protection: 0
* STBC beacon: 0
* L-SIG TXOP Prot: 0
* PCO active: 0
* PCO phase: 0
WPA: * Version: 1
* Group cipher: TKIP
* Pairwise ciphers: CCMP TKIP
* Authentication suites: PSK
RSN: * Version: 1
* Group cipher: TKIP
* Pairwise ciphers: CCMP TKIP
* Authentication suites: PSK
* Capabilities: (0x0000)
WMM: * Parameter version 1
* BE: CW 15-1023, AIFSN 3
* BK: CW 15-1023, AIFSN 7
* VI: CW 7-15, AIFSN 2, TXOP 3008 usec
* VO: CW 3-7, AIFSN 2, TXOP 1504 usec
WPS: * Version: 1.0
* Wi-Fi Protected Setup State: 2 (Configured)
* Response Type: 3 (AP)
* UUID: 3f5944ac-e38d-525b-8d12-f3bae828a69d
* Manufacturer: ZTE
* Model: AR6003
* Model Number:
* Serial Number:
* Primary Device Type: 6-0050f204-1
* Device name: ZTE-AP
* Config methods: Label, Display, PBC, Keypad
* RF Bands: 0x1
shows clearly that both HT capabilities and WMM parameters are correctly returned by the AP upon probing.
Just for the sake of completeness, this is the output of
sudo lshw -C network
........
*-network
description: Wireless interface
product: WiFi Link 5100
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:01:00.0
logical name: wlan0
version: 00
serial: 00:22:fa:ef:32:42
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=iwlwifi driverversion=3.9.2-1-ARCH firmware=8.83.5.1 build 33692 ip=192.168.73.57 latency=0 link=yes multicast=yes wireless=IEEE 802.11abgn
resources: irq:45 memory:c0100000-c0101fff
and of
sudo lspci -vnn | grep -A 12 -i Net
.........
01:00.0 Network controller [0280]: Intel Corporation WiFi Link 5100 [8086:4232]
Subsystem: Intel Corporation WiFi Link 5100 AGN [8086:1201]
Flags: bus master, fast devsel, latency 0, IRQ 45
Memory at c0100000 (64-bit, non-prefetchable) [size=8K]
Capabilities: [c8] Power Management version 3
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [e0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number 00-22-fa-ff-ff-ef-32-42
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi
The module iwlwifi is loaded at boot without any special param setting (i.e., all defaults). Apart from this specific case, the wifi connection works flawlessly, I have tested it since the appearance of this new problem on several networks, with/without encryption.
I have tried switching to a different network manager (wicd), changing the AP settings to leave it open (i.e., without WPA/PSK security), I have tried rebooting and reloading the firmware, all to no avail. I have also tried to gain more insight by turning off network manager, and connecting manually. With the network set to open, I could see dhclient being offered no IP leases; I tried setting a static IP, then connecting, but I was just told: Network Unreachable. WIth WPA/PSK enabled, wpa_supplicant never returns, it just hangs on and on.
I am now in irons; any gentle soul out there willing to lend a hand?
EDIT:
with Linux kernel 3.10, the problem does not exist any longer: the correction to the mac80211 stack trickled down to the kernel.
Last edited by MariusMatutiae (2013-08-09 09:39:05)
Offline
got the same issue with iwlwifi when connecting to a T-mobile mobile 3G hotspot..
anyone any idea?
Offline
Same here on a Vodafone PocketWiFi 2.
Tried NetworkManager, wicd, wifi-menu but all have the same issue.
I recently installed Aptosid on another machine and it has the same problem... It also has kernel version 3.9.
All the live CDs I've tried work, even an Arch CD from May works, though a current install does not.
I have no problems connecting to another (wpa2 enterprise) network yet can't on this 3G modem.
I'm hoping this isn't a permanent issue and perhaps an update very soon will fix this.
It seems the only way to fix this for now is to use an old version of Linux. I'm currently running a virtual machine only for the purpose of Internet sharing, very annoying.
Offline
I'm having exactly the same problem when I try to connect to mobile WiFi hotspot. My device is Huawei E586. The problem starts with kernel 3.9, so I'm forced to use older version 3.8.11.
I'm also hoping it's only temporaty issue, cause I don't want to be stuck using older kernel.
Offline
No answer at all?
Offline
An update: I had to buy a different hotspot, a Huawei E5331. With this device the connection works flawlessly, while the very same problem persists with the Onda PN51T to this day (kernel 3.9.4-1). I am unable to determine which characteristics of the two devices account for the difference in behaviour. Should anyone have any idea about this, I would be happy to post the output of iw list.
As it stands now, I have been setback by 59.99 euros.
Offline
Here's the kernel bug:
https://bugzilla.kernel.org/show_bug.cgi?id=58881
Looks like it was a bug in the mac80211 module. Hopefully the fix makes it's way down to Arch soon.
Last edited by comeandtakeit (2013-06-12 21:22:17)
Offline
Finally some hope for me, and other having the same problem. I've felt like now one knows about the issue or nobody cares enough to say anything about it. Well I guess we just have to wait for the fix now and thanks for good news
Offline
Finally some hope for me, and other having the same problem. I've felt like now one knows about the issue or nobody cares enough to say anything about it. Well I guess we just have to wait for the fix now and thanks for good news
Looks like the fix has already been committed. We're just waiting for a bug fix release I guess. You could try to apply that patch and re-compile if you need the fix now.
Offline
You're right, probably I could try to apply that patch and recompile, but I'm no Linux guru... I haven't done this before. I'm quite patient, so I can stick with kernel 3.8 for now.
Offline
Well, I have waited two weeks, but the 3.9.8 version still doesn't work... So today I applied the patch myself and re-compiled the kernel and it finally works. My question is, will I have to do it manually every time to get the kernel upgraded, or will it eventually get fixed in the "official" kernel?
Offline
Anyone?
Offline
Alright now, problem seems to be solved for me with kernel 3.9.9. Grand thanks for help.
Offline