From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ben Greear Date: Fri, 20 Sep 2013 20:40:56 -0700 Subject: [ath9k-devel] ath9k WPA2-PEAP MSCHAPV2 Connectivity issue In-Reply-To: <523D12BC.4060604@gmail.com> 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> <523B11E0.4070504@gmail.com> <523B1CD1.1050207@rempel-privat.de> <523D12BC.4060604@gmail.com> Message-ID: <523D1548.6070301@candelatech.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org On 09/20/2013 08:30 PM, James Hogan wrote: > I am up to try anything, but, at least in my case, this is not an error > in the drive itself but is an error with the network. The schools' > wireless network is rather old and needs to be updated, so I found a > patch that was never implemented into ath9k and modified my own ath9k > driver. I know that it is probably not the correct way to go about > attacking the issue, but for school purposes, I need to at least have a > working computer. My desktop has not been edited and I would like to > continue using that to test and find a proper way of attacking the > issue. As for now, here are my diffs > > *** drivers/net/wireless/ath/ath9k/init.c.bak~ 2013-09-20 > 22:35:20.982551676 -0400 > --- drivers/net/wireless/ath/ath9k/init.c 2013-09-20 > 22:43:16.322997704 -0400 > *************** > *** 57,62 **** > --- 57,66 ---- > module_param_named(enable_diversity, ath9k_enable_diversity, int, 0444); > MODULE_PARM_DESC(enable_diversity, "Enable Antenna diversity for > AR9565"); > > + int ath9k_modparam_disable_11n; > + module_param_named(11n_disable, ath9k_modparam_disable_11n, int, 0444); > + MODULE_PARM_DESC(11n_disable, "disable 11n functionality"); If you are using ath9k rate control, please try disabling that and use the minstrel-ht rate control instead. With a modern wpa_supplicant and kernel you can just disable HT in the supplicant config, by the way. # disable_ht: Whether HT (802.11n) should be disabled. # 0 = HT enabled (if AP supports it) # 1 = HT disabled # # disable_ht40: Whether HT-40 (802.11n) should be disabled. # 0 = HT-40 enabled (if AP supports it) # 1 = HT-40 disabled # # disable_sgi: Whether SGI (short guard interval) should be disabled. # 0 = SGI enabled (if AP supports it) # 1 = SGI disabled # # ht_mcs: Configure allowed MCS rates. # Parsed as an array of bytes, in base-16 (ascii-hex) # ht_mcs="" // Use all available (default) # ht_mcs="0xff 00 00 00 00 00 00 00 00 00 " // Use MCS 0-7 only # ht_mcs="0xff ff 00 00 00 00 00 00 00 00 " // Use MCS 0-15 only # # disable_max_amsdu: Whether MAX_AMSDU should be disabled. # -1 = Do not make any changes. # 0 = Enable MAX-AMSDU if hardware supports it. # 1 = Disable AMSDU # # ampdu_density: Allow overriding AMPDU density configuration. # Treated as hint by the kernel. # -1 = Do not make any changes. # 0-3 = Set AMPDU density (aka factor) to specified value. # disable_vht: Whether VHT should be disabled. # 0 = VHT enabled (if AP supports it) # 1 = VHT disabled # # vht_capa: VHT capabilities to set in the override # vht_capa_mask: mask of VHT capabilities # # vht_rx_mcs_nss_1/2/3/4/5/6/7/8: override the MCS set for RX NSS 1-8 # vht_tx_mcs_nss_1/2/3/4/5/6/7/8: override the MCS set for TX NSS 1-8 # 0: MCS 0-7 # 1: MCS 0-8 # 2: MCS 0-9 # 3: not supported -- Ben Greear Candela Technologies Inc http://www.candelatech.com