From: Jeff Johnson <jjohnson@codeaurora.org>
To: James Prestwood <prestwoj@gmail.com>
Cc: linux-wireless@vger.kernel.org, linux-wireless-owner@vger.kernel.org
Subject: Re: [RFC 0/1] Allow MAC change on up interface
Date: Thu, 15 Aug 2019 13:48:47 -0700 [thread overview]
Message-ID: <46810d9dbb674fb8d8fb442f2418868a@codeaurora.org> (raw)
In-Reply-To: <20190815185702.30937-1-prestwoj@gmail.com>
On 2019-08-15 11:57, James Prestwood wrote:
> - Adds a new NL80211_ATTR for including a "random mac" to
> CMD_CONNECT. This MAC is passed down the stack and gets set to
> the net_device's address.
My initial reaction is that I'd avoid using the term "random". For some
use cases the address may truly be random, but for other use cases it
may be derived, perhaps in an AP-specific manner. Other terms which may
be more appropriate are "spoofed mac", "administered mac", etc.
It is a shame that due to backward compatibility we can't use
NL80211_ATTR_MAC while shifting the current usage over to using
NL80211_ATTR_BSSID.
next prev parent reply other threads:[~2019-08-15 20:48 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 18:57 [RFC 0/1] Allow MAC change on up interface James Prestwood
2019-08-15 18:57 ` [RFC 1/1] RFC: allow mac address change on up iface James Prestwood
2019-08-15 20:48 ` Jeff Johnson [this message]
2019-08-16 9:56 ` [RFC 0/1] Allow MAC change on up interface Toke Høiland-Jørgensen
2019-08-19 10:14 ` Johannes Berg
2019-08-19 15:55 ` James Prestwood
2019-08-19 20:20 ` Johannes Berg
2019-08-19 20:58 ` Denis Kenzior
2019-08-20 8:59 ` Johannes Berg
2019-08-20 15:40 ` Denis Kenzior
2019-08-20 17:53 ` Dan Williams
2019-08-20 18:21 ` Denis Kenzior
2019-08-20 18:54 ` Toke Høiland-Jørgensen
2019-08-20 19:32 ` Johannes Berg
2019-08-20 19:46 ` Denis Kenzior
2019-08-20 20:01 ` Johannes Berg
2019-08-19 21:14 ` James Prestwood
2019-08-20 6:59 ` Johannes Berg
2019-08-20 19:22 ` Denis Kenzior
2019-08-20 19:43 ` Johannes Berg
2019-08-20 19:58 ` Denis Kenzior
2019-08-20 20:15 ` Johannes Berg
2019-08-20 20:37 ` Denis Kenzior
2019-08-20 21:18 ` Dan Williams
2019-08-20 21:52 ` Denis Kenzior
2019-08-21 7:21 ` Johannes Berg
2019-08-20 19:53 ` James Prestwood
2019-08-20 20:06 ` 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=46810d9dbb674fb8d8fb442f2418868a@codeaurora.org \
--to=jjohnson@codeaurora.org \
--cc=linux-wireless-owner@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=prestwoj@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).