All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC] mac80211_hwsim: notify user-space about channel change.
Date: Tue, 24 Feb 2015 06:36:13 -0800	[thread overview]
Message-ID: <54EC8C5D.5090400@candelatech.com> (raw)
In-Reply-To: <1424772714.2192.16.camel@sipsolutions.net>



On 02/24/2015 02:11 AM, Johannes Berg wrote:
> On Mon, 2015-02-23 at 09:43 -0800, Ben Greear wrote:
>
>>> This seems a bit strange - don't we already tag packets with the
>>> frequency? Why would you need the channel change separately? What does
>>> that even mean? Depending on how you use this it could entirely break
>>> off-channel operation, for example.
>>
>> I was thinking about passive scans.  In that case, we would not always get a packet transmitted
>> when the channel changes?
>
> Ah, well, ok. However, hwsim doesn't actually really have a concept of
> the 'current channel', for example in the offchannel code it just
> temporarily listens on two channels ... so that's not very good for a
> more realistic implementation :)
>
>> I was thinking user-space would mimic a real radio that can only listen on
>> one channel at once (can any real radios actually listen on two channels at once?)
>
> No, real radios cannot do that (not really anyway - I guess if it was
> VHT80 it's really already listening on 4 channels but ...)
>
>> So, if we are off-channel, and pkt arrives for the 'main' channel, then
>> a real radio should drop it, right?
>
> Yes.
>
>> Of course, if user-space does not care, then it can simply ignore the channel-change
>> logic so I think this would be backwards compat with existing hwsim user-space apps.
>
> Sure. But given the murky concept of channel change, and not going to PS
> for off-channel in hwsim etc. I think this would need a bit more design
> rather than just exposing the mac80211 channel change. Additionally,
> with chanctx support that won't even be invoked for example.

We could push more and more of this to user-space and let it decide whether and
how to forward or accept frames for particular radios.

But, to do that, we need the low-level settings sent to user-space
(such as current channel).  Encryption keys could be a future enhancement
here, so that we can do 'hardware' encryption in hwsim (and handle encrypt/decrypt
logic however we want in user-space).

For in-kernel testing (ie, no user-space hwsim tool), then other methods can be used,
or we can just ignore the trickier details.  My interest is primarily in user-space
hwsim tool at the moment.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

  reply	other threads:[~2015-02-24 14:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-17 23:59 [RFC] mac80211_hwsim: notify user-space about channel change greearb
2015-02-23 11:49 ` Johannes Berg
2015-02-23 17:43   ` Ben Greear
2015-02-24 10:11     ` Johannes Berg
2015-02-24 14:36       ` Ben Greear [this message]
2015-02-24 14:40         ` Johannes Berg
2015-03-11 21:05           ` Ben Greear
2015-03-31 14:27             ` Johannes Berg
2015-03-31 15:56               ` Ben Greear
2015-04-14  8:13                 ` Johannes Berg
2015-04-14 14:56                   ` Ben Greear
2015-04-14 15:06                     ` Johannes Berg
2015-04-14 15:55                       ` Ben Greear
2015-04-15  9:33                         ` Johannes Berg
2015-04-15 15:06                           ` Ben Greear
2015-04-17 11:25                             ` 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=54EC8C5D.5090400@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    /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.