From: Johannes Berg <johannes@sipsolutions.net>
To: Aloka Dixit <alokad@codeaurora.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH V7 0/4] mac80211: add multiple bssid support
Date: Fri, 12 Feb 2021 10:59:02 +0100 [thread overview]
Message-ID: <c3b48c141c763e0cc1beb74482cd0bb4fbc546aa.camel@sipsolutions.net> (raw)
In-Reply-To: <20210120005120.32424-1-alokad@codeaurora.org> (sfid-20210120_015542_749517_52354F67)
Hi,
> John Crispin (4):
> nl80211: add basic multiple bssid support
> mac80211: add multiple bssid support to interface handling
> mac80211: add multiple bssid/EMA support to beacon handling
> mac80211: CSA on non-transmitting interfaces
As much as I hate to send this back to you ...
I don't understand how you can not have an nl80211 feature flag for AP-
side multi-BSSID support, yet have a mac80211-level feature flag?
For STA side we could get away with it because we present all the BSSes
in cfg80211's scan results, and even a version of wpa_supplicant that's
not aware of multi-BSSID should be able to pick one of the non-
transmitting BSSes and connect to it.
But here? I don't understand how that'd be possible.
Also, are the interface limits (# of AP interfaces) even sufficient, or
should there be different limits for non-transmitting? I could imagine
that it'd be easier to have more interfaces if they're non-transmitting,
since then you don't have to deal with more beacons but only more MAC
addresses.
So from that POV this seems rather lacking the necessary bits to be able
to confidently use it from userspace?
johannes
next prev parent reply other threads:[~2021-02-12 9:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 0:51 [PATCH V7 0/4] mac80211: add multiple bssid support Aloka Dixit
2021-01-20 0:51 ` [PATCH V7 1/4] nl80211: add basic " Aloka Dixit
2021-01-20 0:51 ` [PATCH V7 2/4] mac80211: add multiple bssid support to interface handling Aloka Dixit
2021-01-20 0:51 ` [PATCH V7 3/4] mac80211: add multiple bssid/EMA support to beacon handling Aloka Dixit
2021-01-20 0:51 ` [PATCH V7 4/4] mac80211: CSA on non-transmitting interfaces Aloka Dixit
2021-02-12 9:59 ` Johannes Berg [this message]
2021-02-12 9:59 ` [PATCH V7 0/4] mac80211: add multiple bssid support Johannes Berg
2021-02-22 22:41 ` Aloka Dixit
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=c3b48c141c763e0cc1beb74482cd0bb4fbc546aa.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=alokad@codeaurora.org \
--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 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).