From: Hans Maes <Hans@bitnet.be>
To: linux-wireless@vger.kernel.org
Subject: current status of 802.11s mesh in ath5k ?
Date: Fri, 19 Jun 2009 11:32:01 +0200 [thread overview]
Message-ID: <4A3B5B11.7060103@bitnet.be> (raw)
Hello,
I've been reading conflicting articles on several linux wireless
websites about this, so I'm asking the question here:
What is the status of 802.11s mesh support in ath5k in the 2.6.30
kernel, in the current wireless-compat, and in the current
wireless-testing ?
Does it work, or is it broken ?
Can/should it be used in a production environment ?
Also, what is the best place to track the status/progress on 802.11s
mesh in ath5k ?
Thanks!
Regards,
Hans
next reply other threads:[~2009-06-19 10:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 9:32 Hans Maes [this message]
2009-06-19 17:00 ` current status of 802.11s mesh in ath5k ? Andrey Yurovsky
2009-06-19 17:19 ` Bob Copeland
2009-06-19 17:42 ` Andrey Yurovsky
2009-07-05 12:05 ` Bob Copeland
2009-07-07 18:42 ` Andrey Yurovsky
2009-06-20 0:58 ` Hans Maes
2009-06-20 9:32 ` Nick Kossifidis
2009-06-22 16:59 ` Stephane Davy
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=4A3B5B11.7060103@bitnet.be \
--to=hans@bitnet.be \
--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).