All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luis Carlos Cobo <luisca@cozybit.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 02/13] o11s: (nl80211/cfg80211) support for mesh interfaces and set_mesh_cfg command
Date: Fri, 08 Feb 2008 16:25:43 -0800	[thread overview]
Message-ID: <1202516743.7025.20.camel@localhost> (raw)
In-Reply-To: <1202343489.9965.47.camel@johannes.berg>

On Thu, 2008-02-07 at 01:18 +0100, Johannes Berg wrote:
> However, maybe I don't understand the mesh ID well enough yet, can you
> maybe explain in a few sentences where it is used and what for?

The mesh ID works as the SSID for mesh networks, on mesh beacons/probes
SSID is set to the wildcard value to avoid interfering with non-mesh
STAs.

An MP only opens a peer link with a neighboring mesh peer if you have
the same mesh configuration. This mesh configuration is composed by the
mesh ID and path discovery protocol/metric/congestion control IDs. Once
the link is open the mesh ID is not included in the frames. Let me know
if you want more info.

It might be a good idea as you suggest in another thread to refuse to
change the mesh id for running interfaces as it would make a lot of
information stale, will consider it.

-- 
Luis Carlos Cobo Rus       GnuPG ID: 44019B60
cozybit Inc.



  reply	other threads:[~2008-02-09  0:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-04 18:51 [PATCH 02/13] o11s: (nl80211/cfg80211) support for mesh interfaces and set_mesh_cfg command Luis Carlos Cobo
2008-02-07  0:18 ` Johannes Berg
2008-02-09  0:25   ` Luis Carlos Cobo [this message]
2008-02-13  7:51     ` Johannes Berg
2008-02-13 18:49       ` Luis Carlos Cobo

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=1202516743.7025.20.camel@localhost \
    --to=luisca@cozybit.com \
    --cc=johannes@sipsolutions.net \
    --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.