Re: [PATCH] cfg80211: allow adding/deleting stations on mesh

[Johannes Berg <johannes@sipsolutions.net>]

[-- Attachment #1: Type: text/plain, Size: 1287 bytes --]

On Tue, 2009-06-16 at 11:42 -0700, Andrey Yurovsky wrote:
> 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.

Ok, fair enough. There are a lot of quirks in the mesh API, one of these
days I'd like to make it less like wext and have you join/leave like the
ibss commands instead of setting each parameter one by one...

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]