* Re: duplicate authentications / excessive missing ACKs / deauth due to inactivity timer
@ 2020-07-22 14:18 Leon M. George
2020-07-22 14:27 ` Ben Greear
0 siblings, 1 reply; 8+ messages in thread
From: Leon M. George @ 2020-07-22 14:18 UTC (permalink / raw)
To: ath10k
Hi :-)
I've encountered connection issues that appear to be strongly related to the
problem in this thread [1] (found via the arch linux bug tracker [2]).
Symptoms:
ap: "disconnected due to excessive missing ACKs"
station: "No beacon heard and the time event is over already..."
Using a monitoring interface on the AP i was able to confirm that the beacon is
indeed not being sent at any time.
I've found a configuration that reliably produces this state
("error state" from here on):
If any number of mesh (or adhoc with ct) points are configured alongside any
number of ordinary APs, this issue starts appearing.
The mesh connections appear to be working correctly in the error state.
I tested various combinations of openwrt-19.xx and openwrt-trunk
with ath10k/ath10k-ct - all were affected.
Aligning with my vague memory, a user on the openwrt forum reports the issue isn't
present in openwrt-18.xx [3].
About the ruling out client issues:
My employer is operating installations with multiple hundreds of ath10k access
points.
We couldn't identify the source of the issue at first when we encountered it in
our live setup and received unsolicited reports from basically every
installation.
As far as we can tell, no client is able to connect in the error state.
We've had our users confirm the bug for
- Apple phones/tablets/macbooks
- Samsung phones, laptops
- computers with Intel/Realtek/AzureWave-hardware.
I hope this info is helpful.
kind regards,
Leon George
[1] https://www.mail-archive.com/ath10k@lists.infradead.org/msg11599.html
[2] https://bugs.archlinux.org/task/58457
[3] https://forum.openwrt.org/t/wifi-connectivity-issues-with-ath10k/67779
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: duplicate authentications / excessive missing ACKs / deauth due to inactivity timer
2020-07-22 14:18 duplicate authentications / excessive missing ACKs / deauth due to inactivity timer Leon M. George
@ 2020-07-22 14:27 ` Ben Greear
2020-07-22 16:04 ` Leon M. George
0 siblings, 1 reply; 8+ messages in thread
From: Ben Greear @ 2020-07-22 14:27 UTC (permalink / raw)
To: ath10k
On 7/22/20 7:18 AM, Leon M. George wrote:
> Hi :-)
>
> I've encountered connection issues that appear to be strongly related to the
> problem in this thread [1] (found via the arch linux bug tracker [2]).
If this is ath10k-ct only problem, plz don't bother this list and send to just me
and/or add to ath10k-ct bugtracker on github.
If it does affect upstream ath10k too, then that would be valid for this mailing
list.
Thanks,
Ben
>
> Symptoms:
> ap: "disconnected due to excessive missing ACKs"
> station: "No beacon heard and the time event is over already..."
>
> Using a monitoring interface on the AP i was able to confirm that the beacon is
> indeed not being sent at any time.
>
> I've found a configuration that reliably produces this state
> ("error state" from here on):
> If any number of mesh (or adhoc with ct) points are configured alongside any
> number of ordinary APs, this issue starts appearing.
> The mesh connections appear to be working correctly in the error state.
>
> I tested various combinations of openwrt-19.xx and openwrt-trunk
> with ath10k/ath10k-ct - all were affected.
> Aligning with my vague memory, a user on the openwrt forum reports the issue isn't
> present in openwrt-18.xx [3].
>
> About the ruling out client issues:
> My employer is operating installations with multiple hundreds of ath10k access
> points.
> We couldn't identify the source of the issue at first when we encountered it in
> our live setup and received unsolicited reports from basically every
> installation.
> As far as we can tell, no client is able to connect in the error state.
> We've had our users confirm the bug for
> - Apple phones/tablets/macbooks
> - Samsung phones, laptops
> - computers with Intel/Realtek/AzureWave-hardware.
>
> I hope this info is helpful.
>
> kind regards,
> Leon George
>
> [1] https://www.mail-archive.com/ath10k@lists.infradead.org/msg11599.html
> [2] https://bugs.archlinux.org/task/58457
> [3] https://forum.openwrt.org/t/wifi-connectivity-issues-with-ath10k/67779
>
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: duplicate authentications / excessive missing ACKs / deauth due to inactivity timer
2020-07-22 14:27 ` Ben Greear
@ 2020-07-22 16:04 ` Leon M. George
0 siblings, 0 replies; 8+ messages in thread
From: Leon M. George @ 2020-07-22 16:04 UTC (permalink / raw)
To: ath10k
Hi Ben,
I was unclear in my last email.
Re-phrasing from my openwrt forum post:
I've tested various combinations of openwrt-trunk (now and early March) / 19.07, ath10k stock / ct driver, and stock / ct firmware.
regards,
Leon
On Wed, 22 Jul 2020 07:27:16 -0700
Ben Greear <greearb@candelatech.com> wrote:
> On 7/22/20 7:18 AM, Leon M. George wrote:
> > Hi :-)
> >
> > I've encountered connection issues that appear to be strongly
> > related to the problem in this thread [1] (found via the arch linux
> > bug tracker [2]).
>
> If this is ath10k-ct only problem, plz don't bother this list and
> send to just me and/or add to ath10k-ct bugtracker on github.
>
> If it does affect upstream ath10k too, then that would be valid for
> this mailing list.
>
> Thanks,
> Ben
>
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: duplicate authentications / excessive missing ACKs / deauth due to inactivity timer
2019-12-01 17:21 ` Adrian Chadd
@ 2019-12-01 18:53 ` Justin Capella
0 siblings, 0 replies; 8+ messages in thread
From: Justin Capella @ 2019-12-01 18:53 UTC (permalink / raw)
To: Adrian Chadd; +Cc: ath10k
Just to note, some of the devices have not been updated, the AP
however has been, kernel upgrade coincides with start of issue.
Name : linux-lts
Install Date : Sat Nov 16 12:58:43 2019
Name : linux-firmware
Install Date : Thu Oct 17 05:27:14 2019
Name : hostapd
Install Date : Thu Sep 19 17:51:31 2019
Name : wpa_supplicant
Install Date : Tue Sep 3 07:06:51 2019
The linux package is built from:
https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/linux-lts&id=6d82129ac6719690fa5c0fd09d1ddb1883c292cf
Link to the 4.19.84 ath10k drivers tree:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/drivers/net/wireless/ath/ath10k?h=v4.19.84
Happy to provide any info but I'm sure this is an issue on the AP side
(where the ATH10k is the base station)
I'll enable debug logging, and see if upgrading/downgrading kernel
makes a difference, if there is any sort of tracepoints anyone is
aware of I can enable those
Client devices:
*Pixel 2 XL cell phone:
Snapdragon X16 LTE modem: mobile connectivity with LTE download speeds
up to 1 Gbps, multi-gigabit 802.11ad, and integrated 2x2 802.11ac
Wi-Fi with MU-MIMO
*Intel AC 9560
*Samsung TV... Unsure of wifi chipset
Station 84:d6:d0:xx:xx:fa (on wlp1s0)
inactive time: 1310 ms
rx bytes: 81380769
rx packets: 522284
tx bytes: 745819867
tx packets: 685665
tx retries: 0
tx failed: 0
rx drop misc: 64
signal: -54 [-60, -56, -62] dBm
signal avg: -59 [-64, -62, -66] dBm
tx bitrate: 468.0 MBit/s VHT-MCS 5 80MHz VHT-NSS 2
rx bitrate: 6.0 MBit/s
rx duration: 40567184 us
last ack signal:-95 dBm
authorized: yes
authenticated: yes
associated: yes
preamble: long
WMM/WME: yes
MFP: no
TDLS peer: no
DTIM period: 2
beacon interval:100
short slot time:yes
connected time: 1220604 seconds
Station 64:16:66:xx:xx:c6 (on wlp1s0)
inactive time: 8530 ms
rx bytes: 13854367
rx packets: 134992
tx bytes: 11651515
tx packets: 38495
tx retries: 0
tx failed: 15
rx drop misc: 110
signal: -60 [-71, -68, -61] dBm
signal avg: -59 [-71, -67, -60] dBm
tx bitrate: 72.2 MBit/s MCS 7 short GI
rx bitrate: 6.0 MBit/s
rx duration: 13006672 us
last ack signal:-95 dBm
authorized: yes
authenticated: yes
associated: yes
preamble: long
WMM/WME: yes
MFP: no
TDLS peer: no
DTIM period: 2
beacon interval:100
short slot time:yes
connected time: 522598 seconds
Station 18:b4:30:xx:xx:be (on wlp1s0) < "Nest"
inactive time: 8530 ms
rx bytes: 8920217
rx packets: 85624
tx bytes: 7452573
tx packets: 24475
tx retries: 0
tx failed: 29
rx drop misc: 1686
signal: -76 [-85, -85, -77] dBm
signal avg: -75 [-83, -83, -76] dBm
tx bitrate: 39.0 MBit/s MCS 4
rx bitrate: 6.0 MBit/s
rx duration: 9793456 us
last ack signal:-95 dBm
authorized: yes
authenticated: yes
associated: yes
preamble: long
WMM/WME: yes
MFP: no
TDLS peer: no
DTIM period: 2
beacon interval:100
short slot time:yes
connected time: 332504 seconds
Station 54:bd:79:xx:xx:9a (on wlp1s0)
inactive time: 22850 ms
rx bytes: 715096377
rx packets: 7165084
tx bytes: 40932559821
tx packets: 27114376
tx retries: 0
tx failed: 8764
rx drop misc: 58230
signal: -71 [-78, -77, -75] dBm
signal avg: -71 [-77, -77, -74] dBm
tx bitrate: 117.0 MBit/s VHT-MCS 3 80MHz VHT-NSS 1
rx bitrate: 6.0 MBit/s
rx duration: 224061996 us
last ack signal:-95 dBm
authorized: yes
authenticated: yes
associated: yes
preamble: long
WMM/WME: yes
MFP: no
TDLS peer: no
DTIM period: 2
beacon interval:100
short slot time:yes
connected time: 80393 seconds
Station 10:f1:f2:xx:xx:30 (on wlp1s0) < Android
inactive time: 42780 ms
rx bytes: 24355519
rx packets: 138402
tx bytes: 112776405
tx packets: 136049
tx retries: 0
tx failed: 163
rx drop misc: 6487
signal: -64 [-77, -75, -64] dBm
signal avg: -64 [-72, -70, -67] dBm
tx bitrate: 175.6 MBit/s VHT-MCS 2 80MHz VHT-NSS 2
rx bitrate: 6.0 MBit/s
rx duration: 11787408 us
last ack signal:-95 dBm
authorized: yes
authenticated: yes
associated: yes
preamble: long
WMM/WME: yes
MFP: no
TDLS peer: no
DTIM period: 2
beacon interval:100
short slot time:yes
connected time: 46408 seconds
Station 48:d6:d5:xx:xx:23 (on wlp1s0)
inactive time: 7940 ms
rx bytes: 2867427
rx packets: 19173
tx bytes: 3553640
tx packets: 13790
tx retries: 0
tx failed: 4
rx drop misc: 0
signal: -48 [-52, -50, -61] dBm
signal avg: -47 [-50, -49, -59] dBm
tx bitrate: 325.0 MBit/s VHT-MCS 7 80MHz short GI VHT-NSS 1
rx bitrate: 433.3 MBit/s VHT-MCS 9 80MHz short GI VHT-NSS 1
rx duration: 1589600 us
last ack signal:-95 dBm
authorized: yes
authenticated: yes
associated: yes
preamble: long
WMM/WME: yes
MFP: no
TDLS peer: no
DTIM period: 2
beacon interval:100
short slot time:yes
connected time: 24731 seconds
On Sun, Dec 1, 2019 at 9:21 AM Adrian Chadd <adrian@freebsd.org> wrote:
>
> It'd be good to at least post the client devices, with the
> kernel/firmware versions if you know them. That way people can check
> for regressions.
>
>
> -a
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: duplicate authentications / excessive missing ACKs / deauth due to inactivity timer
2019-12-01 17:18 ` Justin Capella
@ 2019-12-01 17:21 ` Adrian Chadd
2019-12-01 18:53 ` Justin Capella
0 siblings, 1 reply; 8+ messages in thread
From: Adrian Chadd @ 2019-12-01 17:21 UTC (permalink / raw)
To: Justin Capella; +Cc: ath10k
It'd be good to at least post the client devices, with the
kernel/firmware versions if you know them. That way people can check
for regressions.
-a
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: duplicate authentications / excessive missing ACKs / deauth due to inactivity timer
2019-12-01 17:01 ` Adrian Chadd
@ 2019-12-01 17:18 ` Justin Capella
2019-12-01 17:21 ` Adrian Chadd
0 siblings, 1 reply; 8+ messages in thread
From: Justin Capella @ 2019-12-01 17:18 UTC (permalink / raw)
To: Adrian Chadd; +Cc: ath10k
No Apply devices--- Android (BRCM?), and Linux iwlwifi. I guess I
could have left the OUI's in the MACs.... But it is a recent
regression and multiple clients (all my devices) seem to be impacted.
On Sun, Dec 1, 2019 at 9:01 AM Adrian Chadd <adrian@freebsd.org> wrote:
>
> Are these er, apple devices?
>
>
>
> -adrian
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: duplicate authentications / excessive missing ACKs / deauth due to inactivity timer
2019-12-01 16:30 Justin Capella
@ 2019-12-01 17:01 ` Adrian Chadd
2019-12-01 17:18 ` Justin Capella
0 siblings, 1 reply; 8+ messages in thread
From: Adrian Chadd @ 2019-12-01 17:01 UTC (permalink / raw)
To: Justin Capella; +Cc: ath10k
Are these er, apple devices?
-adrian
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 8+ messages in thread
* duplicate authentications / excessive missing ACKs / deauth due to inactivity timer
@ 2019-12-01 16:30 Justin Capella
2019-12-01 17:01 ` Adrian Chadd
0 siblings, 1 reply; 8+ messages in thread
From: Justin Capella @ 2019-12-01 16:30 UTC (permalink / raw)
To: ath10k
Frequent deauth/disconnections of clients more recently,
My interpretation of the logs makes me think perhaps the clients are
authenticating multiple times, and there may be some inactive/unused
sessions that cause a timeout because of this.
I can enable more verbose/debug output and provide packet captures,
debugfs tracepoints... anything that might help.
Highlights:
Dec 01 05:50:41 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
IEEE 802.11: associated (aid 6)
Dec 01 05:50:41 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
IEEE 802.11: authenticated
Dec 01 05:50:41 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
IEEE 802.11: associated (aid 6)
Dec 01 05:50:41 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
IEEE 802.11: authenticated
Dec 01 04:57:57 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Dec 01 04:57:57 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Dec 01 04:57:27 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
IEEE 802.11: disconnected due to excessive missing ACKs
[user@ap ~]$ pacman -Q linux-lts linux-firmware
linux-lts 4.19.84-1
linux-firmware 20190923.417a9c6-1
[user@ap ~]$ dmesg | grep ath10
[ 7.214732] ath10k_pci 0000:01:00.0: pci irq msi oper_irq_mode 2
irq_mode 0 reset_mode 0
[ 7.485097] ath10k_pci 0000:01:00.0: qca988x hw2.0 target 0x4100016c
chip_id 0x043202ff sub 0000:0000
[ 7.485103] ath10k_pci 0000:01:00.0: kconfig debug 1 debugfs 1 tracing
1 dfs 0 testmode 0
[ 7.485461] ath10k_pci 0000:01:00.0: firmware ver 10.2.4-1.0-00045 api
5 features no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 ccbd5104
[ 7.528393] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08
[ 8.948544] ath10k_pci 0000:01:00.0: htt-ver 2.1 wmi-op 5 htt-op 2 cal
otp max-sta 128 raw 0 hwcrypto 1
[ 9.101248] ath10k_pci 0000:01:00.0 wlp1s0: renamed from wlan0
[ 12.610504] ath10k_pci 0000:01:00.0: pdev param 0 not supported by firmware
[ 17.516191] ath10k_pci 0000:01:00.0: pdev param 0 not supported by firmware
[user@ap ~]$ modinfo ath10k_pci
filename: /lib/modules/4.19.84-1-lts/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko.xz
firmware: ath10k/QCA9377/hw1.0/board.bin
firmware: ath10k/QCA9377/hw1.0/firmware-5.bin
firmware: ath10k/QCA9377/hw1.0/firmware-6.bin
firmware: ath10k/QCA6174/hw3.0/board-2.bin
firmware: ath10k/QCA6174/hw3.0/board.bin
firmware: ath10k/QCA6174/hw3.0/firmware-6.bin
firmware: ath10k/QCA6174/hw3.0/firmware-5.bin
firmware: ath10k/QCA6174/hw3.0/firmware-4.bin
firmware: ath10k/QCA6174/hw2.1/board-2.bin
firmware: ath10k/QCA6174/hw2.1/board.bin
firmware: ath10k/QCA6174/hw2.1/firmware-5.bin
firmware: ath10k/QCA6174/hw2.1/firmware-4.bin
firmware: ath10k/QCA9887/hw1.0/board-2.bin
firmware: ath10k/QCA9887/hw1.0/board.bin
firmware: ath10k/QCA9887/hw1.0/firmware-5.bin
firmware: ath10k/QCA988X/hw2.0/board-2.bin
firmware: ath10k/QCA988X/hw2.0/board.bin
firmware: ath10k/QCA988X/hw2.0/firmware-5.bin
firmware: ath10k/QCA988X/hw2.0/firmware-4.bin
firmware: ath10k/QCA988X/hw2.0/firmware-3.bin
firmware: ath10k/QCA988X/hw2.0/firmware-2.bin
license: Dual BSD/GPL
description: Driver support for Qualcomm Atheros 802.11ac WLAN PCIe/AHB devices
author: Qualcomm Atheros
srcversion: 9FE0E3C9ABD99335286A872
alias: pci:v0000168Cd00000050sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000042sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000046sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000056sv*sd*bc*sc*i*
alias: pci:v0000168Cd00000040sv*sd*bc*sc*i*
alias: pci:v0000168Cd0000003Esv*sd*bc*sc*i*
alias: pci:v0000168Cd00000041sv*sd*bc*sc*i*
alias: pci:v0000168Cd0000003Csv*sd*bc*sc*i*
alias: pci:v00000777d000011ACsv*sd*bc*sc*i*
alias: of:N*T*Cqcom,ipq4019-wifiC*
alias: of:N*T*Cqcom,ipq4019-wifi
depends: ath10k_core
retpoline: Y
intree: Y
name: ath10k_pci
vermagic: 4.19.84-1-lts SMP mod_unload
sig_id: PKCS#7
signer: Build time autogenerated kernel key
sig_key: 51:6C:FF:48:E2:26:98:CC:24:DB:B4:41:9B:12:81:B3:7C:BC:86:FD
sig_hashalgo: sha512
signature: 21:22:D0:AC:13:AD:5E:65:0D:5D:3F:A3:16:5B:7E:D8:90:D3:AF:A9:
6F:A4:AE:B1:32:EF:9D:0F:FF:F8:76:43:B4:63:01:E9:DE:76:B8:CF:
B2:7B:AE:B4:A4:E9:EF:5F:72:6B:B6:96:B1:CC:45:E0:76:A0:AB:80:
A2:A6:0B:82:3D:CE:E2:7F:3B:BA:A9:61:3A:F1:1C:A5:66:A9:5E:1F:
AF:5C:BD:09:3F:27:5B:C8:82:53:3B:63:BB:80:92:A0:D8:85:D1:3A:
D2:CA:1D:C6:B0:E6:05:7E:05:5F:1E:32:0A:53:9E:2C:1B:84:CC:D9:
41:DD:98:D4:72:ED:9D:2D:A1:D3:5C:B8:C5:20:95:25:E6:39:FD:7A:
66:51:C4:FF:5D:A6:34:6B:F8:7A:12:25:0E:00:06:C4:9A:9D:7E:06:
28:D2:04:5C:4D:1B:D5:62:CA:F4:6A:24:82:22:C2:F3:76:8F:D9:FE:
73:16:0D:07:85:C0:7D:02:14:E7:8B:88:E3:CF:05:49:33:70:2E:9E:
62:93:9B:86:EE:56:73:B5:CB:D1:55:62:D5:3E:2C:72:0B:48:24:F8:
14:0B:EA:3A:37:FF:B1:9F:5E:5F:86:47:7F:6A:55:08:15:39:6C:FF:
4F:04:DB:7B:D7:0B:C6:BF:ED:CD:E4:29:8A:D5:AB:8A:E2:8B:10:78:
C7:F4:CF:1B:E8:1F:A1:20:B2:45:54:3D:17:BD:2F:BB:82:70:F8:EA:
B9:51:10:87:5C:AA:4D:FD:88:30:A7:76:72:8A:AC:3C:1E:96:6D:F5:
09:13:8D:8E:CE:F9:05:15:61:CB:95:6D:69:5E:F5:AF:56:CA:E9:AD:
99:B4:85:76:D1:1B:93:2F:A9:EC:B6:36:84:C8:59:3D:D7:A3:1D:73:
AF:E1:F0:04:60:1D:15:65:DA:62:6E:8C:3A:87:45:1D:B2:9E:F1:6E:
E1:0A:53:93:E7:96:41:D2:B8:3F:74:06:A6:8A:A2:B8:8E:6B:CC:04:
E9:17:75:D5:63:D2:3B:BA:19:87:BF:0D:5B:87:A5:67:42:BA:30:0E:
0A:00:F8:DF:C2:78:A7:52:8E:01:FD:01:3B:0E:43:70:7E:21:38:8D:
0D:E5:4E:1C:F5:8E:D9:C9:5D:3A:F3:C2:D3:FC:07:98:7C:EF:FE:94:
C9:F3:FA:AB:5F:6D:C1:24:7E:17:98:0F:A6:96:41:8D:C4:15:EA:D8:
66:C7:CC:41:62:4C:64:3A:BB:98:B5:31:54:57:92:6A:03:32:E5:B6:
25:8B:BD:E7:01:E4:5A:08:58:E1:F6:2B:B6:A3:8B:66:AF:0E:7A:5F:
14:90:AF:7F:F7:9C:8C:47:5F:5F:DB:E6
parm: irq_mode:0: auto, 1: legacy, 2: msi (default: 0) (uint)
parm: reset_mode:0: auto, 1: warm only (default: 0) (uint)
[user@ap ~]$ journalctl -b -0 -u hostapd@wlp1s0 -r | sed -r -e
's/([a-f0-9]{2}):([a-f0-9]{2}:){4,}/\1:XX:XX:XX:XX:/gi' -e
's/internet/ssid/g' -e 's/([A-F0-9]{2})[A-F0-9]{14}/\1XXXXXXXXXXX/g'
-e 's/ ap hostapd/ hostname hostapd/g' -e 's/wlp1s0/wlan0/g' | grep
"Dec 01"
Dec 01 11:51:59 hostname hostapd[322]: wlan0: STA 48:XX:XX:XX:XX:23
WPA: pairwise key handshake completed (RSN)
Dec 01 11:51:59 hostname hostapd[322]: wlan0: STA 48:XX:XX:XX:XX:23
RADIUS: starting accounting session 39XXXXXXXXXXX
Dec 01 11:51:59 hostname hostapd[322]: wlan0: STA 48:XX:XX:XX:XX:23
WPA: pairwise key handshake completed (RSN)
Dec 01 11:51:59 hostname hostapd[322]: wlan0: STA 48:XX:XX:XX:XX:23
RADIUS: starting accounting session 39XXXXXXXXXXX
Dec 01 11:51:59 hostname hostapd[322]: wlan0: AP-STA-CONNECTED 48:XX:XX:XX:XX:23
Dec 01 11:51:58 hostname hostapd[322]: wlan0: STA 48:XX:XX:XX:XX:23
IEEE 802.11: associated (aid 5)
Dec 01 11:51:58 hostname hostapd[322]: wlan0: STA 48:XX:XX:XX:XX:23
IEEE 802.11: authenticated
Dec 01 11:51:58 hostname hostapd[322]: wlan0: STA 48:XX:XX:XX:XX:23
IEEE 802.11: associated (aid 5)
Dec 01 11:51:58 hostname hostapd[322]: wlan0: STA 48:XX:XX:XX:XX:23
IEEE 802.11: authenticated
Dec 01 11:51:37 hostname hostapd[322]: wlan0: AP-STA-DISCONNECTED
48:XX:XX:XX:XX:23
Dec 01 05:50:41 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
WPA: pairwise key handshake completed (RSN)
Dec 01 05:50:41 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
RADIUS: starting accounting session 8AXXXXXXXXXXX
Dec 01 05:50:41 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
WPA: pairwise key handshake completed (RSN)
Dec 01 05:50:41 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
RADIUS: starting accounting session 8AXXXXXXXXXXX
Dec 01 05:50:41 hostname hostapd[322]: wlan0: AP-STA-CONNECTED 10:XX:XX:XX:XX:30
Dec 01 05:50:41 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
IEEE 802.11: associated (aid 6)
Dec 01 05:50:41 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
IEEE 802.11: authenticated
Dec 01 05:50:41 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
IEEE 802.11: associated (aid 6)
Dec 01 05:50:41 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
IEEE 802.11: authenticated
Dec 01 04:57:57 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Dec 01 04:57:57 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Dec 01 04:57:27 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
IEEE 802.11: disconnected due to excessive missing ACKs
Dec 01 04:57:27 hostname hostapd[322]: wlan0: AP-STA-DISCONNECTED
10:XX:XX:XX:XX:30
Dec 01 04:57:27 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
IEEE 802.11: disconnected due to excessive missing ACKs
Dec 01 04:34:50 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
WPA: pairwise key handshake completed (RSN)
Dec 01 04:34:50 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
RADIUS: starting accounting session 1CXXXXXXXXXXX
Dec 01 04:34:50 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
WPA: pairwise key handshake completed (RSN)
Dec 01 04:34:50 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
RADIUS: starting accounting session 1CXXXXXXXXXXX
Dec 01 04:34:50 hostname hostapd[322]: wlan0: AP-STA-CONNECTED 10:XX:XX:XX:XX:30
Dec 01 04:34:50 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
IEEE 802.11: associated (aid 6)
Dec 01 04:34:50 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
IEEE 802.11: authenticated
Dec 01 04:34:50 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
IEEE 802.11: associated (aid 6)
Dec 01 04:34:50 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
IEEE 802.11: authenticated
Dec 01 04:21:01 hostname hostapd[322]: wlan0: AP-STA-DISCONNECTED
10:XX:XX:XX:XX:30
Dec 01 04:19:55 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
WPA: pairwise key handshake completed (RSN)
Dec 01 04:19:55 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
RADIUS: starting accounting session F8XXXXXXXXXXX
Dec 01 04:19:55 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
WPA: pairwise key handshake completed (RSN)
Dec 01 04:19:55 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
RADIUS: starting accounting session F8XXXXXXXXXXX
Dec 01 04:19:55 hostname hostapd[322]: wlan0: AP-STA-CONNECTED 10:XX:XX:XX:XX:30
Dec 01 04:19:55 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
IEEE 802.11: associated (aid 6)
Dec 01 04:19:55 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
IEEE 802.11: associated (aid 6)
Dec 01 04:19:55 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
IEEE 802.11: authenticated
Dec 01 04:19:55 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
IEEE 802.11: authenticated
Dec 01 04:19:52 hostname hostapd[322]: wlan0: AP-STA-DISCONNECTED
10:XX:XX:XX:XX:30
Dec 01 03:30:20 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
WPA: pairwise key handshake completed (RSN)
Dec 01 03:30:20 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
RADIUS: starting accounting session 8EXXXXXXXXXXX
Dec 01 03:30:20 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
WPA: pairwise key handshake completed (RSN)
Dec 01 03:30:20 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
RADIUS: starting accounting session 8EXXXXXXXXXXX
Dec 01 03:30:20 hostname hostapd[322]: wlan0: AP-STA-CONNECTED 10:XX:XX:XX:XX:30
Dec 01 03:30:20 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
IEEE 802.11: associated (aid 6)
Dec 01 03:30:20 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
IEEE 802.11: associated (aid 6)
Dec 01 03:30:20 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
IEEE 802.11: authenticated
Dec 01 03:30:20 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
IEEE 802.11: authenticated
Dec 01 03:29:57 hostname hostapd[322]: wlan0: AP-STA-DISCONNECTED
10:XX:XX:XX:XX:30
Dec 01 02:53:18 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
WPA: pairwise key handshake completed (RSN)
Dec 01 02:53:18 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
RADIUS: starting accounting session 88XXXXXXXXXXX
Dec 01 02:53:18 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
WPA: pairwise key handshake completed (RSN)
Dec 01 02:53:18 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
RADIUS: starting accounting session 88XXXXXXXXXXX
Dec 01 02:53:18 hostname hostapd[322]: wlan0: AP-STA-CONNECTED 10:XX:XX:XX:XX:30
Dec 01 02:53:17 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
IEEE 802.11: associated (aid 6)
Dec 01 02:53:17 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
IEEE 802.11: authenticated
Dec 01 02:53:17 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
IEEE 802.11: associated (aid 6)
Dec 01 02:53:17 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
IEEE 802.11: authenticated
Dec 01 02:52:55 hostname hostapd[322]: wlan0: AP-STA-DISCONNECTED
10:XX:XX:XX:XX:30
Dec 01 01:15:22 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
WPA: pairwise key handshake completed (RSN)
Dec 01 01:15:22 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
RADIUS: starting accounting session 93XXXXXXXXXXX
Dec 01 01:15:22 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
WPA: pairwise key handshake completed (RSN)
Dec 01 01:15:22 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
RADIUS: starting accounting session 93XXXXXXXXXXX
Dec 01 01:15:22 hostname hostapd[322]: wlan0: AP-STA-CONNECTED 10:XX:XX:XX:XX:30
Dec 01 01:15:22 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
IEEE 802.11: associated (aid 6)
Dec 01 01:15:22 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
IEEE 802.11: authenticated
Dec 01 01:15:22 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
IEEE 802.11: associated (aid 6)
Dec 01 01:15:22 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
IEEE 802.11: authenticated
Dec 01 00:14:34 hostname hostapd[322]: wlan0: AP-STA-DISCONNECTED
10:XX:XX:XX:XX:30
Dec 01 00:04:59 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
WPA: pairwise key handshake completed (RSN)
Dec 01 00:04:59 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
RADIUS: starting accounting session 25XXXXXXXXXXX
Dec 01 00:04:59 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
WPA: pairwise key handshake completed (RSN)
Dec 01 00:04:59 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
RADIUS: starting accounting session 25XXXXXXXXXXX
Dec 01 00:04:59 hostname hostapd[322]: wlan0: AP-STA-CONNECTED 10:XX:XX:XX:XX:30
Dec 01 00:04:59 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
IEEE 802.11: associated (aid 6)
Dec 01 00:04:59 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
IEEE 802.11: associated (aid 6)
Dec 01 00:04:59 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
IEEE 802.11: authenticated
Dec 01 00:04:59 hostname hostapd[322]: wlan0: STA 10:XX:XX:XX:XX:30
IEEE 802.11: authenticated
Dec 01 00:04:58 hostname hostapd[322]: wlan0: AP-STA-DISCONNECTED
10:XX:XX:XX:XX:30
A particularly noise event:
Nov 27 22:22:36 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
WPA: pairwise key handshake completed (RSN)
Nov 27 22:22:36 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
RADIUS: starting accounting session 0BXXXXXXXXXXX
Nov 27 22:22:36 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
WPA: pairwise key handshake completed (RSN)
Nov 27 22:22:36 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
RADIUS: starting accounting session 0BXXXXXXXXXXX
Nov 27 22:22:36 hostname hostapd[322]: wlan0: AP-STA-CONNECTED 18:XX:XX:XX:XX:be
Nov 27 22:22:35 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: associated (aid 2)
Nov 27 22:22:35 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: associated (aid 2)
Nov 27 22:22:35 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: authenticated
Nov 27 22:22:35 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: authenticated
Nov 27 22:22:35 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:35 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:35 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:35 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:35 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:35 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:25 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:25 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:25 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:25 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:25 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Nov 27 22:22:25 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Nov 27 22:22:24 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:24 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:24 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:24 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:24 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:24 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:24 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:24 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:24 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:24 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:24 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:24 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:20 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:20 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:20 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: authenticated
Nov 27 22:22:20 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: authenticated
Nov 27 22:22:20 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: authenticated
Nov 27 22:22:20 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: authenticated
Nov 27 22:22:20 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:20 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:20 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:20 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:19 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:19 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:19 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:19 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:19 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:19 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:15 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:15 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:15 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:15 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:15 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:15 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:15 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:15 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:15 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:15 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:15 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: authenticated
Nov 27 22:22:15 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: authenticated
Nov 27 22:22:14 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:14 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: did not acknowledge authentication response
Nov 27 22:22:14 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: authenticated
Nov 27 22:22:14 hostname hostapd[322]: wlan0: STA 18:XX:XX:XX:XX:be
IEEE 802.11: authenticated
Nov 27 22:22:14 hostname hostapd[322]: wlan0: AP-STA-DISCONNECTED
18:XX:XX:XX:XX:be
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2020-07-22 16:04 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-07-22 14:18 duplicate authentications / excessive missing ACKs / deauth due to inactivity timer Leon M. George
2020-07-22 14:27 ` Ben Greear
2020-07-22 16:04 ` Leon M. George
-- strict thread matches above, loose matches on Subject: below --
2019-12-01 16:30 Justin Capella
2019-12-01 17:01 ` Adrian Chadd
2019-12-01 17:18 ` Justin Capella
2019-12-01 17:21 ` Adrian Chadd
2019-12-01 18:53 ` Justin Capella
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.