From: Andrey Yurovsky <andrey@cozybit.com>
To: Simon Raffeiner <sturmflut@lieberbiber.de>
Cc: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>,
linux-wireless@vger.kernel.org, johannes@sipsolutions.net
Subject: Re: [PATCH] nl80211: allow adding new station to devices in mesh mode
Date: Fri, 5 Feb 2010 15:16:49 -0800 [thread overview]
Message-ID: <c1545bb51002051516u15f25d75s88314534cbea569b@mail.gmail.com> (raw)
In-Reply-To: <201002052004.06220.sturmflut@lieberbiber.de>
On Fri, Feb 5, 2010 at 11:04 AM, Simon Raffeiner
<sturmflut@lieberbiber.de> wrote:
> If manual addition of plinks is allowed you could theoretically force your
> node to peer with a neighbor running a different profile, e.g. using a different
> path selection or authentication algorithm, or an implementation based on a
> different draft version.
>
> I can't really think of an use for it.
Right, in your case please ensure that your devices are beaconing
(that's the most common problem) before proceeding. plinks are
established automatically and as far as I know that's the only thing
we need to support at this time. If your device isn't beaconing, then
that's a bug and it should be fixed. That said, ath5k beaconed
correctly last time I tried it.
-Andrey
next prev parent reply other threads:[~2010-02-05 23:16 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
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 [this message]
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=c1545bb51002051516u15f25d75s88314534cbea569b@mail.gmail.com \
--to=andrey@cozybit.com \
--cc=cascardo@holoscopio.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=sturmflut@lieberbiber.de \
/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