From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Hogan Date: Thu, 19 Sep 2013 11:01:52 -0400 Subject: [ath9k-devel] ath9k WPA2-PEAP MSCHAPV2 Connectivity issue In-Reply-To: <21039.52508.810448.90944@gargle.gargle.HOWL> References: <522B7D97.2010409@gmail.com> <21035.64671.831349.345777@gargle.gargle.HOWL> <522CAF8E.8000006@gmail.com> <21037.48871.472273.313308@gargle.gargle.HOWL> <522FC154.10100@gmail.com> <21039.52508.810448.90944@gargle.gargle.HOWL> Message-ID: <523B11E0.4070504@gmail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org I think I have stumbled on to the real issue. I'm sorry if I have been wasting your time at all. Apparently, the network is having problems with all wireless-n mode cards. The network doesn't like how wireless-n is roaming to the different AP's and is registering as me disconnecting when the wireless card tries to connect to roam to the other AP. It's not just ath9k though, Ra-Link and other cards are having these issues as well. Is there a way to disable or to make it possible to disable the wireless-n mode of the card and just use wireless abg? On a note, I noticed when I passed to the command line "iw event -r" that at about the time my card would scan, that is when I would stop receiving service even though my cards never registered as being disconnected. After the scan, the card just continues to reissue scans. Sometimes however, it will try to reconnect me to the network. I was talking to one of the IT employees in my class today and he said that they have been having this issue with all of the newer higher-end cards. This is the scan output: wlan0 (phy #0): scan started wlan0 (phy #0): scan finished: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 2467 2472 5180 5200 5220 5240 5260 5280 5300 5320 5745 5765 5785 5805 5825, ""