linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* 802.11s is possible
@ 2007-02-22 17:20 ivan.muccini
  2007-02-22 18:11 ` John W. Linville
  0 siblings, 1 reply; 2+ messages in thread
From: ivan.muccini @ 2007-02-22 17:20 UTC (permalink / raw)
  To: linux-wireless

Hi, i'm italian student. I want experiment a channel
assignment algorithm in 802.11s mesh network. I think to use
madwifi driver for develop 802.11 feature, like new mesh
header in MAC header of Data frame, beacon, probe message
and association. Moreover I need to create new information
elemnt for HWMP routing protcol.
Becouse i am new in madwifi, i'm asking you if is possible
do this whit madwifi.
Anybody can help me?
thank

Ivan

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: 802.11s is possible
  2007-02-22 17:20 802.11s is possible ivan.muccini
@ 2007-02-22 18:11 ` John W. Linville
  0 siblings, 0 replies; 2+ messages in thread
From: John W. Linville @ 2007-02-22 18:11 UTC (permalink / raw)
  To: ivan.muccini@witech.it; +Cc: linux-wireless

On Thu, Feb 22, 2007 at 06:20:02PM +0100, ivan.muccini@witech.it wrote:
> Hi, i'm italian student. I want experiment a channel
> assignment algorithm in 802.11s mesh network. I think to use
> madwifi driver for develop 802.11 feature, like new mesh
> header in MAC header of Data frame, beacon, probe message
> and association. Moreover I need to create new information
> elemnt for HWMP routing protcol.
> Becouse i am new in madwifi, i'm asking you if is possible
> do this whit madwifi.

You'll have to look elsewhere for madwifi.  This list is for work
destined for inclusion in the Linux kernel itself.  If you must use
Atheros hardware, then please consider working in the ar5k-based
dadwifi branch of the madwifi project.  That may have a future in
the upstream kernel.

However, please consider using the Devicescape-originated stack which
we here are working to have included in the upstream kernel "soon".  If you
are familiar with git, you can get the sources from the tree here:

	git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-dev.git

If you would prefer a stack of patches (over 700!) to apply on top
of a current tree from Linus, you may want to look here:

	http://www.kernel.org/pub/linux/kernel/people/linville/wireless-dev/mm-master

If that is unappealing but you are a Fedora user, you may want to
look at my test kernels here:

	http://people.redhat.com/linville/kernels/fc6/

Or my Fedora-netdev kernels available through yum by following the
instructions here:

	http://people.redhat.com/linville/kernels/fedora-netdev/

And if none of those apply, you may wish to stick to Ralink rt2x00 or
Intel ipw3945 hardware.  Each of those projects maintains a snapshot
of the Devicescape-originated stack for use with their own drivers.

As for help with understanding the stack code, Devicescape has some
documentation available at their site.	And, of course, the code
itself is the best reference.  :-)

Hth!

John
-- 
John W. Linville
linville@tuxdriver.com

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2007-02-22 18:21 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-02-22 17:20 802.11s is possible ivan.muccini
2007-02-22 18:11 ` John W. Linville

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).