From: Johannes Berg <johannes@sipsolutions.net>
To: Javier Cardona <javier@cozybit.com>
Cc: Andrey Yurovsky <andrey@cozybit.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
John Linville <linville@tuxdriver.com>,
devel@lists.open80211s.org
Subject: Re: [PATCH] cfg80211: allow adding/deleting stations on mesh
Date: Tue, 16 Jun 2009 21:59:13 +0200 [thread overview]
Message-ID: <1245182353.21287.58.camel@johannes.local> (raw)
In-Reply-To: <445f43ac0906161251v63d59cc1jd72bade62910d086@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 841 bytes --]
On Tue, 2009-06-16 at 12:51 -0700, Javier Cardona wrote:
> > No, I don't have any in mind. I wasn't aware that only the mesh_id
> > defines the mesh, I was under the impression that more needs to match,
> > as codified in mesh_matches_local().
>
> In addition to the mesh id, a successful peering requires that peer
> candidates use the same methods for path selection, congestion
> control, synchronization and authentication. None of these are
> configurable via iw (essentially because only one single option for
> each method is implemented).
Ahh! Ok, goes to show how little I understand the mesh code. IIRC
somebody had a patch to make those configurable though. I guess as long
as those need to be configured while creating the interface the API is
actually very good and much better than I thought :)
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
prev parent reply other threads:[~2009-06-16 19:59 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
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 [this message]
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=1245182353.21287.58.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=andrey@cozybit.com \
--cc=devel@lists.open80211s.org \
--cc=javier@cozybit.com \
--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