From: Andrey Yurovsky <andrey@cozybit.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
John Linville <linville@tuxdriver.com>
Subject: Re: [PATCH] cfg80211: allow adding/deleting stations on mesh
Date: Tue, 16 Jun 2009 11:42:10 -0700 [thread overview]
Message-ID: <45e8e6c40906161142m759e6ecdgc6765333a4cced01@mail.gmail.com> (raw)
In-Reply-To: <1245177307.21287.34.camel@johannes.local>
On Tue, Jun 16, 2009 at 11:35 AM, Johannes
Berg<johannes@sipsolutions.net> wrote:
> On Tue, 2009-06-16 at 11:31 -0700, Andrey Yurovsky wrote:
>> Commit b2a151a288 added a check that prevents adding or deleting
>> stations on non-AP interfaces. Adding and deleting stations is
>> supported for Mesh Point interfaces, so add Mesh Point to that check as
>> well.
>
> Why? Aren't those automatically discovered like IBSS peers?
Yes, they normally are, however it's possible to turn that off from
user space (via iw).
The reason for this is that it's useful to manually create mesh
topologies. This is mostly for testing, verification, and
experimentation. For example, you can manually create a topology
where you have two paths and you know one path is better than another
and then run a test script that verifies that the right path was
taken. It could presumably also be used by some user-space "mesh
manager" similar to hostapd for APs.
-Andrey
>> Signed-off-by: Andrey Yurovsky <andrey@cozybit.com>
>> ---
>> net/wireless/nl80211.c | 6 ++++--
>> 1 files changed, 4 insertions(+), 2 deletions(-)
>>
>> diff --git a/net/wireless/nl80211.c b/net/wireless/nl80211.c
>> index e18856c..b28c641 100644
>> --- a/net/wireless/nl80211.c
>> +++ b/net/wireless/nl80211.c
>> @@ -1763,7 +1763,8 @@ static int nl80211_new_station(struct sk_buff *skb, struct genl_info *info)
>> goto out_rtnl;
>>
>> if (dev->ieee80211_ptr->iftype != NL80211_IFTYPE_AP &&
>> - dev->ieee80211_ptr->iftype != NL80211_IFTYPE_AP_VLAN) {
>> + dev->ieee80211_ptr->iftype != NL80211_IFTYPE_AP_VLAN &&
>> + dev->ieee80211_ptr->iftype != NL80211_IFTYPE_MESH_POINT) {
>> err = -EINVAL;
>> goto out;
>> }
>> @@ -1812,7 +1813,8 @@ static int nl80211_del_station(struct sk_buff *skb, struct genl_info *info)
>> goto out_rtnl;
>>
>> if (dev->ieee80211_ptr->iftype != NL80211_IFTYPE_AP &&
>> - dev->ieee80211_ptr->iftype != NL80211_IFTYPE_AP_VLAN) {
>> + dev->ieee80211_ptr->iftype != NL80211_IFTYPE_AP_VLAN &&
>> + dev->ieee80211_ptr->iftype != NL80211_IFTYPE_MESH_POINT) {
>> err = -EINVAL;
>> goto out;
>> }
>
next prev parent reply other threads:[~2009-06-16 18:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-16 18:31 [PATCH] cfg80211: allow adding/deleting stations on mesh Andrey Yurovsky
2009-06-16 18:35 ` Johannes Berg
2009-06-16 18:42 ` Andrey Yurovsky [this message]
2009-06-16 18:45 ` Johannes Berg
2009-06-16 18:55 ` Andrey Yurovsky
2009-06-16 18:56 ` Johannes Berg
2009-06-16 19:32 ` Javier Cardona
2009-06-16 19:37 ` Johannes Berg
2009-06-16 19:51 ` Javier Cardona
2009-06-16 19:59 ` 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=45e8e6c40906161142m759e6ecdgc6765333a4cced01@mail.gmail.com \
--to=andrey@cozybit.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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