From: Ben Greear <greearb@candelatech.com>
To: "Adam R. Welle" <arwelle@cert.org>,
Johannes Berg <johannes@sipsolutions.net>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Bob Copeland <me@bobcopeland.com>
Subject: Re: question on "mac80211_hwsim: support any address in userspace"
Date: Wed, 16 Dec 2015 15:20:18 -0800 [thread overview]
Message-ID: <5671F1B2.2010503@candelatech.com> (raw)
In-Reply-To: <2DE9F46DD36D2A458CD6347950113F2535CA6D@marathon>
On 12/16/2015 02:56 PM, Adam R. Welle wrote:
>>> Could somebody provide background information on why the decision was
>>> made to use a second address for the netlink frames instead of the
>>> same address as was used for the non-netlink frames?
>>
>> I would be fine with always using the first address instead of the
>> second, in case that helps someone.
>>
>> We could also set the address at creation time easily enough. Then it
>> could still be unique across many machines if you managed it.
>
> I actually apply a patch for that. I have added a module parameter which
> is used as the MAC address for the first radio, and I increment the final
> octet for each additional radio. This is so that my users do not have
> to manually reset the MAC address to get a unique one. I apply the address
> to both addresses mentioned above though I only use the netlink datapath.
>
> If there is interest in this I can submit it as an RFC patch tomorrow.
I'd rather see support for specifying an arbitrary MAC upon creation
with a netlink attribute than a module parameter...
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2015-12-16 23:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-16 3:29 question on "mac80211_hwsim: support any address in userspace" Ben Greear
2015-12-16 9:17 ` Johannes Berg
2015-12-16 13:13 ` Ben Greear
2015-12-16 13:25 ` Johannes Berg
2015-12-16 13:35 ` Ben Greear
2015-12-16 13:42 ` Johannes Berg
2015-12-16 14:11 ` Ben Greear
2015-12-16 14:14 ` Johannes Berg
2015-12-16 14:15 ` Johannes Berg
2015-12-16 14:59 ` Bob Copeland
2015-12-16 15:52 ` Ben Greear
2015-12-16 17:30 ` Adam R. Welle
2015-12-16 17:46 ` Bob Copeland
2015-12-16 18:57 ` Adam R. Welle
2015-12-16 22:14 ` Ben Greear
2015-12-16 22:56 ` Adam R. Welle
2015-12-16 23:20 ` Ben Greear [this message]
2015-12-16 23:56 ` Adam R. Welle
2015-12-17 13:26 ` Bob Copeland
2015-12-16 13:21 ` me@bobcopeland.com >> Bob Copeland
2015-12-16 13:27 ` Ben Greear
2015-12-16 13:57 ` me@bobcopeland.com >> Bob Copeland
2015-12-16 14:16 ` Ben Greear
2015-12-16 14:33 ` me@bobcopeland.com >> Bob Copeland
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=5671F1B2.2010503@candelatech.com \
--to=greearb@candelatech.com \
--cc=arwelle@cert.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=me@bobcopeland.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).