From: Luis Carlos Cobo <luisca@cozybit.com>
To: cao jing <caojing.china@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: mesh point beacon sending problem for 802.11s
Date: Tue, 22 Apr 2008 17:48:39 -0700 [thread overview]
Message-ID: <1208911719.13800.2.camel@localhost> (raw)
In-Reply-To: <9f33c5230804152338va7a9118tdd869f2196a6742b@mail.gmail.com>
On Wed, 2008-04-16 at 02:38 -0400, cao jing wrote:
> Hi,
>
> Open11s developers said it's already supported the Mesh peer link
> establishment. But I can't find any code for mesh point to send
> beacons. How come the mesh point establish a peer link without
> beacons.
That you did not find the code does not necessarily means it is not
there ;-). Check out net/mac80211/tx.c:ieee80211_beacon_get()
I assume you are looking at wireless-testing.
Cheers!
--
Luis Carlos Cobo Rus GnuPG ID: 44019B60
cozybit Inc.
next prev parent reply other threads:[~2008-04-23 0:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-16 6:38 mesh point beacon sending problem for 802.11s cao jing
2008-04-23 0:48 ` Luis Carlos Cobo [this message]
2008-04-23 0:54 ` cao jing
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=1208911719.13800.2.camel@localhost \
--to=luisca@cozybit.com \
--cc=caojing.china@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