From: Johannes Berg <johannes@sipsolutions.net>
To: IgorMitsyanko <igor.mitsyanko.os@quantenna.com>, jouni@qca.qualcomm.com
Cc: linux-wireless@vger.kernel.org, vamsin@qti.qualcomm.com
Subject: Re: [PATCH] cfg80211: Random local address for Public Action frame exchange
Date: Mon, 02 Jan 2017 15:33:27 +0100 [thread overview]
Message-ID: <1483367607.21014.9.camel@sipsolutions.net> (raw)
In-Reply-To: <c7eaea82-a5be-d047-c67a-ce9e58b4b65f@quantenna.com>
> Acknowledgment is done for transmitter<->receiver addresses,
> not for source<->destination?
Well, these are management frames, there either are no SA/DA or they're
identical to RA/TA, depending on how you want to look at it. Typically
it does get called SA/DA too then.
> Patch talks about source address randomization, but I guess it
> actually
> meant transmitter address (basically dynamic BSSID config?). Maybe
> naming should be changed in the patch.
Yes, I suppose TA might be a tad more accurate.
BSSID is another (unrelated) address.
> For NL80211_EXT_FEATURE_MGMT_TX_RANDOM_SA_CONNECTED case,
> I wonder if HW can be configured to not filter-out multiple BSSIDs
> or
> the idea
> is that while random_sa frame is pending for ACK, HW will drop all
> frames destined
> for initially configured BSSID?
Again, BSSID is unrelated (unless you're restricting yourself to the AP
STA case where BSSID == local MAC address).
And no, traffic would not be permitted to be dropped in this case, IMO
johannes
next prev parent reply other threads:[~2017-01-02 14:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-20 20:39 [PATCH] cfg80211: Random local address for Public Action frame exchange Jouni Malinen
2016-12-30 19:55 ` IgorMitsyanko
2017-01-02 11:28 ` Johannes Berg
2017-01-02 14:29 ` IgorMitsyanko
2017-01-02 14:33 ` Johannes Berg [this message]
2017-01-02 11:34 ` Johannes Berg
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=1483367607.21014.9.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=igor.mitsyanko.os@quantenna.com \
--cc=jouni@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=vamsin@qti.qualcomm.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 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.