linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Pedersen <thomas@noack.us>
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: Tue, 20 May 2014 10:36:23 -0700	[thread overview]
Message-ID: <CAMEF0p_sywFDC_PVa-7sAGvgJ=cRNSTZpVaE4EauV_9Zgmui6g@mail.gmail.com> (raw)
In-Reply-To: <CAGnRvup8OVnkTxxJzV5Pe88XNUFXXVh21tpgygS=f27Hux=uiQ@mail.gmail.com>

Hi Henning,

On Tue, May 20, 2014 at 5:32 AM, Henning Rogge <hrogge@gmail.com> wrote:
> Hi,
>
> after spending a day reading through the 802.11s implementation of
> Linux I have to admit I am lost...
>
> I am using 802.11s bridged to ethernet on both wlan interfaces and it
> works very well.
>
> Unfortunately the cfg802.11 is not telling me which ethernet mac
> address is behind which wifi mac address, something that has to be
> known to the kernel to forward the bridged ethernet frames.
>
> Is there a trick to get this information or is this just a missing
> functionality in the cfg80211 API (or the "iw <mesh-if> mpath ..."
> commands) ?

mac80211 keeps a separate table for bridged endpoints (mpp_paths).
Unfortunately this table currently isn't exported by the cfg80211
mpath_dump API. If you really need access to this information from
cfg80211 / userspace, then the quickest thing for now would be to hack
in support for iterating over both tables.

I'm not really sure why the decision was made to go with 2 different
path tables (see 79617dee for the initial implementation), but it
seems the cleaner approach would be to merge these and stick with the
existing mpath_dump commands.

-- 
thomas

  reply	other threads:[~2014-05-20 17:36 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
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 [this message]
2014-05-20 17:41             ` Henning Rogge
2014-05-21  6:51             ` Henning Rogge
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='CAMEF0p_sywFDC_PVa-7sAGvgJ=cRNSTZpVaE4EauV_9Zgmui6g@mail.gmail.com' \
    --to=thomas@noack.us \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).