From: Martin Fuzzey <martin.fuzzey@flowbird.group>
To: Marek Vasut <marex@denx.de>, netdev@vger.kernel.org
Cc: Angus Ainslie <angus@akkea.ca>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Kalle Valo <kvalo@codeaurora.org>,
Lee Jones <lee.jones@linaro.org>,
Martin Kepplinger <martink@posteo.de>,
Sebastian Krzyszkowiak <sebastian.krzyszkowiak@puri.sm>,
Siva Rebbagondla <siva8118@gmail.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] rsi: Fix TX EAPOL packet handling against iwlwifi AP
Date: Thu, 27 May 2021 18:52:32 +0200 [thread overview]
Message-ID: <ba9013a8-38e4-f1ee-05a7-c3cf668bf449@flowbird.group> (raw)
In-Reply-To: <20201015111616.429220-1-marex@denx.de>
Hi Marek,
I've just run into the same problem (on -5.4) and found your (now
merged) patch
On 15/10/2020 13:16, Marek Vasut wrote:
> In case RSI9116 SDIO WiFi operates in STA mode against Intel 9260 in AP mode,
> the association fails. The former is using wpa_supplicant during association,
> the later is set up using hostapd:
>
> iwl$ cat hostapd.conf
> interface=wlp1s0
> ssid=test
> country_code=DE
> hw_mode=g
> channel=1
> wpa=2
> wpa_passphrase=test
> wpa_key_mgmt=WPA-PSK
> iwl$ hostapd -d hostapd.conf
>
> rsi$ wpa_supplicant -i wlan0 -c <(wpa_passphrase test test)
>
> The problem is that the TX EAPOL data descriptor RSI_DESC_REQUIRE_CFM_TO_HOST
> flag and extended descriptor EAPOL4_CONFIRM frame type are not set in case the
> AP is iwlwifi, because in that case the TX EAPOL packet is 2 bytes shorter.
>
> The downstream vendor driver has this change in place already [1], however
> there is no explanation for it, neither is there any commit history from which
> such explanation could be obtained.
>
I get this using 2 RSI9116 s, for both AP and STA using hostapd.
Comparing packet captures in the working and non working (without your
patch) case shows that
the working case has a 802.11 QOS header whereas the non working case
does not, hence the 2 byte difference.
The size of the EAPOL data is the same, it's the previous header that
causes the problem...
This whole use the message size to determine the messages to ACK seems
very fragile...
Regards,
Martin
next prev parent reply other threads:[~2021-05-27 16:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 11:16 [PATCH] rsi: Fix TX EAPOL packet handling against iwlwifi AP Marek Vasut
2020-11-07 11:32 ` Kalle Valo
2021-05-27 16:52 ` Martin Fuzzey [this message]
2021-05-27 17:07 ` Marek Vasut
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ba9013a8-38e4-f1ee-05a7-c3cf668bf449@flowbird.group \
--to=martin.fuzzey@flowbird.group \
--cc=angus@akkea.ca \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=kvalo@codeaurora.org \
--cc=lee.jones@linaro.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marex@denx.de \
--cc=martink@posteo.de \
--cc=netdev@vger.kernel.org \
--cc=sebastian.krzyszkowiak@puri.sm \
--cc=siva8118@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).