It means there's a replay / out of order thing going on with the received
frames that are TKIP encrypted.
-adrian
On Wed, 17 Apr 2019 at 12:18, Yuri wrote:
> I use wpa_gui, and sometimes it fails to connect with the "Last message"
> field alternating between "Associating ..." and "TKIP count
I use wpa_gui, and sometimes it fails to connect with the "Last message"
field alternating between "Associating ..." and "TKIP countermeasures
started".
What does the latter message mean, and why does it prevent connectivity?
if_run driver is in use.
Yuri
_
Try loading firmware, see if it can do a bt scan.
Try also bringing up the 2g wifi and connect to a 2g station; see if that
also allows a bt scan to work.
-a
On Wed, 17 Apr 2019 at 11:17, Matthias Apitz wrote:
> Am Mittwoch, 17. April 2019 19:59:17 CEST schrieb Adrian Chadd
> :
> > no flashi
Am Mittwoch, 17. April 2019 19:59:17 CEST schrieb Adrian Chadd
:
no flashing occurs. it's running out of ram on the chip.
-a
So, what do you want me to test exactly?
ma
--
Sent from my Ubuntu phone
http://www.unixarea.de/
___
freebsd-wireless@fr
no flashing occurs. it's running out of ram on the chip.
-a
On Wed, 17 Apr 2019 at 10:56, Matthias Apitz wrote:
> Am Mittwoch, 17. April 2019 18:59:08 CEST schrieb Adrian Chadd
> :
> > Did you copy it into /usr/share/ or did you pass the command line arg in
> to
> > set the base directory? :)
Am Mittwoch, 17. April 2019 18:59:08 CEST schrieb Adrian Chadd
:
Did you copy it into /usr/share/ or did you pass the command line arg in to
set the base directory? :)
I was aware of the flag -f to specify the dir or file of the
firmware to use. I did not set this by intention to *not* flash
t
Did you copy it into /usr/share/ or did you pass the command line arg in to
set the base directory? :)
-a
On Wed, 17 Apr 2019 at 09:57, Matthias Apitz wrote:
> El día Wednesday, April 17, 2019 a las 02:35:51PM +, Alexey Dokuchaev
> escribió:
>
> > On Tue, Apr 16, 2019 at 12:34:12PM +0200,
El día Wednesday, April 17, 2019 a las 02:35:51PM +, Alexey Dokuchaev
escribió:
> On Tue, Apr 16, 2019 at 12:34:12PM +0200, Matthias Apitz wrote:
> > # ./ath3kfw -D -d ugen0.3 -I
> > ath3kfw: opening dev 0.3
> > ath3k_is_3012: found AR3012
> > main: state=0x0e
> > ROM version: 285343744, buil
On Tue, Apr 16, 2019 at 12:34:12PM +0200, Matthias Apitz wrote:
> # ./ath3kfw -D -d ugen0.3 -I
> ath3kfw: opening dev 0.3
> ath3k_is_3012: found AR3012
> main: state=0x0e
> ROM version: 285343744, build version: 155, ram version: 155, ref clock=1
> ath3kfw: ath3k_fw_read: open:
> /usr/share/firmwa
