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: Wed, 13 Feb 2008 10:49:56 -0800 [thread overview]
Message-ID: <1202928596.6870.16.camel@localhost> (raw)
In-Reply-To: <1202889089.8931.14.camel@johannes.berg>
On Wed, 2008-02-13 at 08:51 +0100, Johannes Berg wrote:
> > 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.
>
> We don't have settings for the other control IDs yet, or did I miss
> them?
Those settings are in the struct ieee80211_if_sta. We are just
hardcoding the values on route initialization, since we just support one
path protocol and link metric.
> Another, off-topic in this thread, question: How is beaconing defined
> for a mesh point? Is it similar to how it works in an IBSS?
According to the draft you can choose IBSS-like beaconing (wait a small
random time before sending the beacon and don't send it if you hear it
first) or AP-like beaconing.
--
Luis Carlos Cobo Rus GnuPG ID: 44019B60
cozybit Inc.
prev parent reply other threads:[~2008-02-13 18:48 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
2008-02-13 7:51 ` Johannes Berg
2008-02-13 18:49 ` Luis Carlos Cobo [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=1202928596.6870.16.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.