Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <eac8596b51b7a6f7b02777e126c40cd76ef0f426.camel@gmail.com>
Subject: Re: MK7921K de-auths from AP every 5 minutes
From:   James Prestwood <prestwoj@gmail.com>
To:     Riccardo Paolo Bestetti <pbl@bestov.io>
Cc:     nbd@nbd.name, lorenzo.bianconi83@gmail.com, ryder.lee@mediatek.com,
        shayne.chen@mediatek.com, sean.wang@mediatek.com, kvalo@kernel.org,
        linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Date:   Tue, 15 Mar 2022 16:20:32 -0700
In-Reply-To: <CICSX6EXTZ6U.MYGFTUDU5ZKW@enhorning>
References: <CICSX6EXTZ6U.MYGFTUDU5ZKW@enhorning>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.40.4 (3.40.4-2.fc34) 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Precedence: bulk

Hi,

On Sun, 2022-03-06 at 14:00 +0100, Riccardo Paolo Bestetti wrote:
> 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.

Could you also post the IWD debug logs (running with -d).

> 
> 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@wlan2: disconnected, group key exchange timeout,
> signal strength -42
> 
> 12:24:21:
> BE:1A:C2:58:95:F0@wlan2: disconnected, group key exchange timeout,
> signal strength -42
> 
> 12:29:21:
> BE:1A:C2:58:95:F0@wlan2: 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
>