From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"me@bobcopeland.com >> Bob Copeland" <me@bobcopeland.com>
Subject: Re: question on "mac80211_hwsim: support any address in userspace"
Date: Wed, 16 Dec 2015 10:17:44 +0100 [thread overview]
Message-ID: <1450257464.3159.1.camel@sipsolutions.net> (raw)
In-Reply-To: <5670DA9A.4010102@candelatech.com> (sfid-20151216_042934_976896_DCE1A2B3)
On Tue, 2015-12-15 at 19:29 -0800, Ben Greear wrote:
> This patch below was added to the kernel around 2/24/2015
>
> I am curious mostly about the first change: I thought the
> transmitter-addr relates to the radio device, not the vdev (sta, ap,
> etc).
It doesn't, even on real hardware.
> But, wouldn't using data from the header break that assumption?
>
>
> Is there any actual advantage to having more than one address per
> hwsim radio? It seems it complicates things for no particular
> reason as far as I can tell?
>
??
You can do this with any regular hardware that supports multiple
virtual interfaces - each one of them gets its own address.
I think you might be confused by how ath*k implements the address
matching - as I understand it there it's a common address (which may or
may not match the programmed hardware address) along with a mask.
That's not true in general though.
The hwsim commit here just makes wmediumd able to behave properly when
the user changed the vif interface address.
johannes
next prev parent reply other threads:[~2015-12-16 9:17 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 [this message]
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
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=1450257464.3159.1.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=greearb@candelatech.com \
--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).