netdev - MK7921K de-auths from AP every 5 minutes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <CICSX6EXTZ6U.MYGFTUDU5ZKW@enhorning>
Date:   Sun, 06 Mar 2022 14:00:08 +0100
From:   "Riccardo Paolo Bestetti" <pbl@...tov.io>
To:     <pbl@...tov.io>
Cc:     <nbd@....name>, <lorenzo.bianconi83@...il.com>,
        <ryder.lee@...iatek.com>, <shayne.chen@...iatek.com>,
        <sean.wang@...iatek.com>, <kvalo@...nel.org>,
        <linux-wireless@...r.kernel.org>, <netdev@...r.kernel.org>
Subject: MK7921K de-auths from AP every 5 minutes

Hi,

I have recently installed an AMD RZ608 Wi-Fi card in my laptop. The card
uses the MT7921K chipset from MediaTek. I'm running Arch Linux, using
kernel 5.16.12-arch1-1. I'm using iwd 1.25-1 as my wireless daemon.

I'm experiencing de-auths every 5 minutes from my AP, which is a MikroTik
RB962UiGS-5HacT2HnT running the latest firmware. This has a AR9888 wireless
chip. It is indeed configured to update group keys every 5 minutes.

All the de-auths happen with excellent signal and SNR (consistently 50dB
or better as reported by the router, which is only a few meters apart
form the laptop). My router is set up on a fixed channel, with fixed
channel width 20MHz. The almost perfect periodicity also suggests that
bad signal is not an issue at play.

The kernel log does not report any messages from the driver. Only:

Mar 06 12:19:21 enhorning kernel: wlan0: deauthenticated from 08:55:31:cc:23:c3 (Reason: 16=GROUP_KEY_HANDSHAKE_TIMEOUT)
Mar 06 12:19:23 enhorning kernel: wlan0: authenticate with 08:55:31:cc:23:c3
Mar 06 12:19:23 enhorning kernel: wlan0: send auth to 08:55:31:cc:23:c3 (try 1/3)
Mar 06 12:19:23 enhorning kernel: wlan0: authenticated
Mar 06 12:19:23 enhorning kernel: wlan0: associate with 08:55:31:cc:23:c3 (try 1/3)
Mar 06 12:19:23 enhorning kernel: wlan0: RX AssocResp from 08:55:31:cc:23:c3 (capab=0x431 status=0 aid=2)
Mar 06 12:19:24 enhorning kernel: wlan0: associated
Mar 06 12:24:21 enhorning kernel: wlan0: deauthenticated from 08:55:31:cc:23:c3 (Reason: 16=GROUP_KEY_HANDSHAKE_TIMEOUT)
Mar 06 12:24:23 enhorning kernel: wlan0: authenticate with 08:55:31:cc:23:c3
Mar 06 12:24:23 enhorning kernel: wlan0: send auth to 08:55:31:cc:23:c3 (try 1/3)
Mar 06 12:24:23 enhorning kernel: wlan0: authenticated
Mar 06 12:24:23 enhorning kernel: wlan0: associate with 08:55:31:cc:23:c3 (try 1/3)
Mar 06 12:24:23 enhorning kernel: wlan0: RX AssocResp from 08:55:31:cc:23:c3 (capab=0x431 status=0 aid=2)
Mar 06 12:24:24 enhorning kernel: wlan0: associated
Mar 06 12:29:21 enhorning kernel: wlan0: deauthenticated from 08:55:31:cc:23:c3 (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
Mar 06 12:29:28 enhorning kernel: wlan0: authenticate with 08:55:31:cc:23:c3
Mar 06 12:29:28 enhorning kernel: wlan0: send auth to 08:55:31:cc:23:c3 (try 1/3)
Mar 06 12:29:28 enhorning kernel: wlan0: authenticated
Mar 06 12:29:28 enhorning kernel: wlan0: associate with 08:55:31:cc:23:c3 (try 1/3)
Mar 06 12:29:28 enhorning kernel: wlan0: RX AssocResp from 08:55:31:cc:23:c3 (capab=0x431 status=0 aid=2)
Mar 06 12:29:28 enhorning kernel: wlan0: associated

Pretty much the same from the router:

12:19:21:
BE:1A:C2:58:95:F0@...n2: disconnected, group key exchange timeout, signal strength -42

12:24:21:
BE:1A:C2:58:95:F0@...n2: disconnected, group key exchange timeout, signal strength -42

12:29:21:
BE:1A:C2:58:95:F0@...n2: disconnected, group key exchange timeout, signal strength -42

I have other devices connected to the same access point without issue,
and I can connect to other access points without issue. So I'm figuring
this is an issue specific to the combination of this chip and the
particular access point.

I am not able to say whether the issue is in this driver, or with the
access point. How might I go about finding out?

Best regards,
Riccardo P. Bestetti