From: Johannes Berg <johannes@sipsolutions.net>
To: Xuebing Wang <xbing6@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: [linux-wireless] [mac80211] Does IEEE80211_IBSS_MAX_STA_ENTRIES (in net/mac80211/ibss.c) work?
Date: Fri, 09 Jun 2017 10:59:09 +0200 [thread overview]
Message-ID: <1496998749.2424.3.camel@sipsolutions.net> (raw)
In-Reply-To: <0d40c0dc-4476-0567-6cb9-149a3fcc83e4@gmail.com> (sfid-20170608_065026_486259_DBDF5F58)
On Thu, 2017-06-08 at 12:50 +0800, Xuebing Wang wrote:
> Hi community,
>
> Does IEEE80211_IBSS_MAX_STA_ENTRIES (in net/mac80211/ibss.c) work?
Yes, as far as it's supposed to :)
> I hard-code it to be 2 (from original 128), and update kernel for
> one node, and start IBSS network with 5 nodes. In the node with hard-
> coded IBSS_MAX_STA_ENTRIES = 2, I still can see and ping all other 4
> nodes. I am using kernel v3.18.29, does IBSS_MAX_STA_ENTRIES work
> with latest kernel source code?
>
> My purpose is to limit the max number of peers (for all nodes in
> IBSS network) to be 12 or 20.
This isn't really the point of this setting, and that's why it's also
not configurable.
This setting is really just intended to catch the case of a rogue
network/transmitter or similar overflowing the amount of memory we
keep.
This setting has no impact on who we can *communicate* with - although
we can only communicate with peers that we don't have a station entry
for on very few low rates, so you won't get good performance beyond
that point.
If you wanted to actually limit the IBSS network to a certain number of
peers, you'd have to
* make that setting configurable (with a sane upper bound)
* write some additional code to restrict IBSS communication to when a
station entry exists
You could also do some higher layer filtering (iptables) I guess.
johannes
prev parent reply other threads:[~2017-06-09 8:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 4:50 [linux-wireless] [mac80211] Does IEEE80211_IBSS_MAX_STA_ENTRIES (in net/mac80211/ibss.c) work? Xuebing Wang
2017-06-09 8:59 ` Johannes Berg [this message]
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=1496998749.2424.3.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=xbing6@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).