lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 23 Jan 2007 11:18:27 -0500
From:	"Jon Smirl" <jonsmirl@...il.com>
To:	"Johannes Berg" <johannes@...solutions.net>
Cc:	"Marcelo Tosatti" <marcelo@...ck.org>,
	"Dan Williams" <dcbw@...hat.com>, "Jiri Benc" <jbenc@...e.cz>,
	netdev <netdev@...r.kernel.org>,
	"Jeff Garzik" <jgarzik@...ox.com>,
	"John W. Linville" <linville@...hat.com>,
	"Luis R. Rodriguez" <mcgrof@...il.com>,
	"Arnd Bergmann" <arnd@...db.de>,
	"Arnaldo Carvalho de Melo" <acme@...stprotocols.net>
Subject: Re: [PATCH] Marvell Libertas 8388 802.11b/g USB driver (v2)

On 1/23/07, Johannes Berg <johannes@...solutions.net> wrote:
> On Mon, 2007-01-22 at 10:20 -0500, Jon Smirl wrote:
>
> > What is the general solution for 802.11s?
>
> None yet.
>
> > I'm working on an embedded
> > design that would benefit from 11s support and I'd rather not have to
> > roll my own mesh implementation in user space.
>
> Well, there is no mesh implementation that I'm aware of, you'll want to
> stick it along with the userspace MLME into wpa_supplicant.

Is the 802.11s Draft 1.0 spec publicly available yet? It is supposed
to be making changes at the very lowest MAC layers. It will be hard to
be compatible with that from user space.

> > I'd also like to get an
> > idea of what kind of hardware I need to design onto my board given
> > that the 8388 is not available general consumption. My system has
> > plenty of power and CPU available so a softmac type 11s solution is
> > the most cost effective. It seems to me that the design of a software
> > based 11s stack should be coordinated with the 8388 firmware one.
>
> It should, but afaik no one is really working on it either way.

The software doesn't have to be written but there should be at least
some design work done on how 11s should fit into the existing world
for both a firmware and software implementation. I'd hate to see a
different implementation for each vendor and another one for the
software stack.

-- 
Jon Smirl
jonsmirl@...il.com
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ