From: Johannes Berg <johannes@sipsolutions.net>
To: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>
Cc: linux-wireless@vger.kernel.org, Andrey Yurovsky <andrey@cozybit.com>
Subject: Re: [PATCH] nl80211: allow adding new station to devices in mesh mode
Date: Fri, 05 Feb 2010 10:59:02 +0100 [thread overview]
Message-ID: <1265363942.3613.1.camel@johannes.local> (raw)
In-Reply-To: <1265362748.3613.0.camel@johannes.local>
On Fri, 2010-02-05 at 10:39 +0100, Johannes Berg wrote:
> On Thu, 2010-02-04 at 23:00 -0200, Thadeu Lima de Souza Cascardo wrote:
> > When trying to use the NEW_STATION command, it fails with -EINVAL,
> > because there's no STA_SUPPORTED_RATES parameter. However, for mesh
> > mode, this parameter should be NULL. Besides, it requires
> > LISTEN_INTERVAL to be negative. We allow it to be ommited in the STA
> > case too, in which it will be -1.
> >
> > ---
> >
> > Hello.
> >
> > I was trying to use iw station set in mesh mode and found out I wanted
> > to call NEW_STATION.
>
> Hmm. Can you explain why you want to do that? Mesh usually discovers its
> peers, and you can add paths, but peers doesn't make a whole lot of
> sense to me?
So it's allowed due to commit 155cc9e4b1d60161ee53ffaf2c15b9411f086fa7,
but I don't understand why. Andrey?
johannes
next prev parent reply other threads:[~2010-02-05 9:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 1:00 [PATCH] nl80211: allow adding new station to devices in mesh mode Thadeu Lima de Souza Cascardo
2010-02-05 9:39 ` Johannes Berg
2010-02-05 9:59 ` Johannes Berg [this message]
2010-02-05 16:57 ` Thadeu Lima de Souza Cascardo
2010-02-05 17:47 ` Andrey Yurovsky
2010-02-05 17:55 ` Thadeu Lima de Souza Cascardo
2010-02-05 19:04 ` Simon Raffeiner
2010-02-05 23:16 ` Andrey Yurovsky
2010-02-06 8:59 ` Johannes Berg
2010-02-07 19:51 ` Andrey Yurovsky
2010-02-08 9:08 ` Johannes Berg
2010-02-08 19:25 ` Javier Cardona
2010-02-08 20:26 ` Thadeu Lima de Souza Cascardo
2010-02-09 7:58 ` Johannes Berg
2010-02-08 13:54 ` Simon Raffeiner
2010-02-08 17:26 ` Javier Cardona
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=1265363942.3613.1.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=andrey@cozybit.com \
--cc=cascardo@holoscopio.com \
--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