linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marco Porsch <marco.porsch@siemens.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: iw station del broken?
Date: Mon, 29 Mar 2010 15:41:14 +0200	[thread overview]
Message-ID: <4BB0ADFA.8010205@siemens.com> (raw)
In-Reply-To: <1269868155.4131.29.camel@jlt3.sipsolutions.net>

Johannes Berg schrieb:
> On Mon, 2010-03-29 at 15:05 +0200, Marco Porsch wrote:
>   
>> Johannes Berg schrieb:
>>     
>>> On Mon, 2010-03-29 at 14:47 +0200, Marco Porsch wrote:
>>>   
>>>       
>>>> Hi list,
>>>>
>>>> is it just me or is 'iw dev <devname> station del <MAC address>' broken?
>>>>     
>>>>         
>>> No ... we decided a while ago that station manipulation in mesh was too
>>> hard to support and removed it.
>>>
>>> What's the use case anyway?
>>>
>>> johannes
>>>   
>>>       
>> The use case is that, if I have some mesh points in a single room or one 
>> a small floor, I can simply give them a topology by removing the links 
>> between the STA, I do not wish to be directly connected.
>> Removing the links means 'iw dev <devname> set mesh_param 
>> mesh_auto_open_plinks 0', which blocks building up new peering links, 
>> and then removing some links with 'station del'.
>>     
>
> Can't you just do that before it gets discovered?
>
> I'm not really happy with the mesh API anyway ...
>
> johannes
>
>   
That makes any scripting impossible, because it would mean a fine timing 
between the ifup on the stations. Also I think you can't build complex 
topologies this way.
The alternative iw dev <devname> mpath set <destination MAC address> 
next_hop <next hop MAC address> is not useful (if it is still included 
though ^^) because it sets paths hard. Means that these paths are not 
changed, even if they are broken.

Well, you're the maintainer. Your choice.

By the way: which was the last version with 'station del' in mesh 
intact? Which codeparts would have to be exchanged if i'd like to use 
this further? Only iw and nl80211?

  reply	other threads:[~2010-03-29 13:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-29 12:47 iw station del broken? Marco Porsch
2010-03-29 12:58 ` Johannes Berg
2010-03-29 13:05   ` Marco Porsch
2010-03-29 13:09     ` Johannes Berg
2010-03-29 13:41       ` Marco Porsch [this message]
2010-03-29 13:43         ` 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=4BB0ADFA.8010205@siemens.com \
    --to=marco.porsch@siemens.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 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).