From: "Sathishkumar Muruganandam" <murugana@codeaurora.org>
To: "'Luca Coelho'" <luciano.coelho@intel.com>,
"'Johannes Berg'" <johannes@sipsolutions.net>
Cc: <linux-wireless@vger.kernel.org>
Subject: 4addr NDP in HE mode
Date: Tue, 18 Feb 2020 11:39:09 +0530 [thread overview]
Message-ID: <006501d5e621$f21f3b60$d65db220$@codeaurora.org> (raw)
Hi Luca, Johannes,
We see that HE STA in 4addr mode is not able to pass traffic since 4addr NDP
frame after successful association is blocked in below commit. There is no
AP/VLAN interface created on the 4addr AP side as well.
commit 41cbb0f5a29592874355 "mac80211: add support for HE"
@@ -929,6 +1020,10 @@ static void ieee80211_send_4addr_nullfunc(struct
ieee80211_local *local,
if (WARN_ON(sdata->vif.type != NL80211_IFTYPE_STATION))
return;
+ /* Don't send NDPs when connected HE */
+ if (!(sdata->u.mgd.flags & IEEE80211_STA_DISABLE_HE))
+ return;
+
skb = dev_alloc_skb(local->hw.extra_tx_headroom + 30);
if (!skb)
return;
Since ieee80211_send_4addr_nullfunc() is only called for successful
association of 4addr STA, shall we allow below case alone for HE ?
static bool ieee80211_assoc_success(struct ieee80211_sub_if_data *sdata,
struct cfg80211_bss *cbss,
struct ieee80211_mgmt *mgmt, size_t len,
struct ieee802_11_elems *elems)
{
..
/*
* If we're using 4-addr mode, let the AP know that we're
* doing so, so that it can create the STA VLAN on its side
*/
if (ifmgd->use_4addr)
ieee80211_send_4addr_nullfunc(local, sdata);
..
Whether this 4addr NDP in HE mode will affect any UL-MIMO from the 4addr STA
? Please comment.
Thanks,
Sathishkumar
next reply other threads:[~2020-02-18 6:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 6:09 Sathishkumar Muruganandam [this message]
2020-03-20 12:58 ` 4addr NDP in HE mode Johannes Berg
2020-04-13 10:41 ` Sathishkumar Muruganandam
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='006501d5e621$f21f3b60$d65db220$@codeaurora.org' \
--to=murugana@codeaurora.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=luciano.coelho@intel.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).