[Server-devel] Mesh connectivity from regular WiFi gear

[Michail Bletsas]

In theory we should be fine with the driver. In practice, given its 
current status, a lot of testing is needed.

M.





"Kim Quirk" <kim at laptop.org> 
Sent by: server-devel-bounces at lists.laptop.org
04/17/2008 02:35 PM

To
"Marten Vijn" <info at martenvijn.nl>
cc
server-devel <server-devel at lists.laptop.org>
Subject
Re: [Server-devel] Mesh connectivity from regular WiFi gear






I thought there might be a wireless driver piece that needed to be 
addressed. I gave the PEAP trac item to Michail for comment.

Thanks,
Kim

On Thu, Apr 17, 2008 at 1:51 PM, Marten Vijn <info at martenvijn.nl> wrote:

On Thu, 2008-04-17 at 09:27 -0400, Kim Quirk wrote:
> Martin, Wad,
> We have promised to provide NYC with a schedule for the item you
> mention, Martin, trac #6855, as well as support for PEAP. trac #6900.
> I have told them that PEAP was a 2009 feature (mainly because I wanted
> to discourage them), but they have asked if we can pull it in.

Considering:

http://www.freebsd.org/doc/en/books/handbook/network-wireless.html
and
http://www.freebsdmall.com/%
7Eloader/en_US.ISO8859-1/articles/wireless/article.html

This would be possible and I am willing to put time in this.

If needed, I could put some effort to put it in firmware (tinybsd) for
any i386 mobo/embedded system.

The XS could to radius (and optinally config AP's with ssh/or/puppet)

Marten

>
> So the next step on these two items is to figure out the development
> and test effort associated with these two features. It would be great
> if people could add their thoughts into those trac bugs as to what
> work is needed.
>
> After we have that, we can weigh that against other priorities and
> come up with which release to put these in.
>
> Thanks,
> Kim
>
> On Thu, Apr 17, 2008 at 8:58 AM, Martin Langhoff
> <martin.langhoff at gmail.com> wrote:
>         On Thu, Apr 17, 2008 at 3:26 AM, John Watlington
>         <wad at laptop.org> wrote:
>         >  If a school is using a mesh, we have a carefully designed
>         system
>         >  to ensure that a laptop doesn't go into simple mesh mode,
>         and instead
>         >  connects automatically with the school.
>         >
>         >  If a school is using traditional WiFi, there is no such
>         guarantee.
>         >  This is possibly bad, as kids that aren't associated can
>         interfere with
>         >  those that are.
>
>
>         When at NYC, you mentioned that the NM searches and prefers
>         the
>         school-mesh-<n> essids of mesh-type signals. And that perhaps
>         we could
>         make it lock into infrastructure-mode essids of that name with
>         the
>         same kind of preference. Would this simple fix help sort the
>         problem
>         out?
>
>         Also, do we have wikipage of tested APs?
>
>         cheers,
>
>
>
>
>         m
>         --
>          martin.langhoff at gmail.com
>          martin at laptop.org -- School Server Architect
>          - ask interesting questions
>          - don't get distracted with shiny stuff - working code first
>          - http://wiki.laptop.org/go/User:Martinlanghoff
>         _______________________________________________
>         Server-devel mailing list
>         Server-devel at lists.laptop.org
>         http://lists.laptop.org/listinfo/server-devel
>
>
> _______________________________________________
> Server-devel mailing list
> Server-devel at lists.laptop.org
> http://lists.laptop.org/listinfo/server-devel
--

Marten Vijn
http://martenvijn.nl
http://wifisoft.org
http://opencommunitycamp.org

_______________________________________________
Server-devel mailing list
Server-devel at lists.laptop.org
http://lists.laptop.org/listinfo/server-devel