From: Bob Copeland <me@bobcopeland.com>
To: Henning Rogge <hrogge@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: 802.11s mode without HWMP
Date: Mon, 19 May 2014 09:18:32 -0400 [thread overview]
Message-ID: <20140519131832.GA6198@localhost> (raw)
In-Reply-To: <CAGnRvurDvRqeNZYHZQG63=6FQv2XnFOR+J9K4-Dk=F77c6SdKQ@mail.gmail.com>
On Mon, May 19, 2014 at 11:00:53AM +0200, Henning Rogge wrote:
> Is there an easy way to stop HWMP in the 802.11s implementation?
If I understand your use case, you want to basically remove the
resolving part of mesh_nexthop_resolve()? I don't believe the
current implementation has a way to turn that off. In principle,
you can specify a vendor-specific path selection protocol when
joining, but glancing at the existing code, we don't really do
anything with that field except use it for peering fitness checks.
If all you want to do is force the paths, you can do so with the
NL80211_CMD_SET_MESH_PATH API; such paths would override any selected
by HWMP. But you'd still generate PREQ/PREPs and get multihop
communication in that case, it just wouldn't be subject to the
airtime link metric.
Perhaps we should skip resolve in case ifmsh->mesh_pp_id != 1
and assume paths are somehow set up out of band or something?
--
Bob Copeland %% www.bobcopeland.com
next prev parent reply other threads:[~2014-05-19 13:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 9:00 802.11s mode without HWMP Henning Rogge
2014-05-19 13:18 ` Bob Copeland [this message]
2014-05-19 14:14 ` Henning Rogge
2014-05-19 14:29 ` Bob Copeland
2014-05-19 14:45 ` Henning Rogge
2014-05-19 19:38 ` etienne.champetier
2014-05-20 6:06 ` Henning Rogge
2014-05-20 12:32 ` Henning Rogge
2014-05-20 17:36 ` Thomas Pedersen
2014-05-20 17:41 ` Henning Rogge
2014-05-21 6:51 ` Henning Rogge
-- strict thread matches above, loose matches on Subject: below --
2014-05-21 1:22 Yeoh Chun-Yeow
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=20140519131832.GA6198@localhost \
--to=me@bobcopeland.com \
--cc=hrogge@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.