On Thu, Mar 30, 2017 at 9:22 AM, Tim Harvey wrote:
> On Wed, Mar 29, 2017 at 10:54 PM, Janusz Dziedzic
> wrote:
>> On 29 March 2017 at 19:03, Tim Harvey wrote:
>>> Greetings,
>>>
>>> (resending plaintext - oops)
>>>
>>> I'm seeing failures to authenticate with a WPA2 secured AP using ath9k
>>> b
On Wed, Mar 29, 2017 at 10:54 PM, Janusz Dziedzic
wrote:
> On 29 March 2017 at 19:03, Tim Harvey wrote:
>> Greetings,
>>
>> (resending plaintext - oops)
>>
>> I'm seeing failures to authenticate with a WPA2 secured AP using ath9k
>> based cards on wireless-next:
>>
>> root@xenial-armhf:~# wpa_pas
* Janusz Dziedzic [30.03.2017 08:26]:
> On 29 March 2017 at 19:03, Tim Harvey wrote:
> > I don't know when ath9k last worked honestly. I usually use them under
> > OpenWrt which has its own patches against periodic updates of linux
> > backports. I noticed this first with Ubuntu 16.04 with the Ub
On 29 March 2017 at 19:03, Tim Harvey wrote:
> Greetings,
>
> (resending plaintext - oops)
>
> I'm seeing failures to authenticate with a WPA2 secured AP using ath9k
> based cards on wireless-next:
>
> root@xenial-armhf:~# wpa_passphrase testssid testpass >
> /etc/wpa_supplicant/wpa_supplicant.con
Greetings,
(resending plaintext - oops)
I'm seeing failures to authenticate with a WPA2 secured AP using ath9k
based cards on wireless-next:
root@xenial-armhf:~# wpa_passphrase testssid testpass >
/etc/wpa_supplicant/wpa_supplicant.conf
root@xenial-armhf:~# iw reg get
country US: DFS-FCC
