[XCSSA] New Mesh Technology Experimentation

xcssa@xcssa.org xcssa@xcssa.org
Sun, 1 Oct 2006 19:58:57 +0000


--Boundary-00=_B4BIFh+t0uzVwb2
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Cool stuff going on with mesh technology and MIT.

Tweeks

--Boundary-00=_B4BIFh+t0uzVwb2
Content-Type: message/rfc822;
  name="forwarded message"
Content-Transfer-Encoding: 7bit
Content-Description: "Bao Q. Nguyen" <bn@ucsd.edu>: Re: [SCFN] cheap mesh that works, maybe
Content-Disposition: inline

Return-Path: <discuss-bounces@socalfreenet.org>
Received: from jupiter.dotcolo.com (jupiter.dotcolo.com [205.134.251.159])
	by server1.xcssa.org (8.12.11.20060308/8.12.11) with ESMTP id k91ICG5t023435
	for <tweeks-solcal@theweeks.org>; Sun, 1 Oct 2006 13:12:16 -0500
Received: from localhost ([127.0.0.1] helo=jupiter.dotcolo.com)
	by jupiter.dotcolo.com with esmtp (Exim 4.52)
	id 1GU5YO-00039m-Dq; Sun, 01 Oct 2006 17:56:40 +0000
Received: from [64.233.182.186] (helo=nf-out-0910.google.com)
	by jupiter.dotcolo.com with esmtp (Exim 4.52) id 1GU5YM-0001nl-Bl
	for Discuss@socalfreenet.org; Sun, 01 Oct 2006 17:56:39 +0000
Received: by nf-out-0910.google.com with SMTP id c29so1300433nfb
	for <Discuss@socalfreenet.org>; Sun, 01 Oct 2006 10:56:36 -0700 (PDT)
Received: by 10.78.128.15 with SMTP id a15mr1266248hud;
	Sun, 01 Oct 2006 10:56:35 -0700 (PDT)
Received: by 10.78.124.10 with HTTP; Sun, 1 Oct 2006 10:56:34 -0700 (PDT)
Message-ID: <47b36b290610011056r75fec2fdpf5fa330569fc3c60@mail.gmail.com>
Date: Sun, 1 Oct 2006 10:56:34 -0700
From: "Bao Q. Nguyen" <bn@ucsd.edu>
To: "Michael Mee" <mike@socalfreenet.org>
In-Reply-To: <451F6935.1040403@socalfreenet.org>
MIME-Version: 1.0
References: <451F6935.1040403@socalfreenet.org>
X-Google-Sender-Auth: 5eee2b66f6ba008d
Cc: SCFN <Discuss@socalfreenet.org>
Subject: Re: [SCFN] cheap mesh that works, maybe
X-BeenThere: discuss@socalfreenet.org
X-Mailman-Version: 2.1.9.cp1
Precedence: list
List-Id: "SoCalFreeNet.org General Discussion List"
	<discuss_socalfreenet.org.socalfreenet.org>
List-Unsubscribe: <http://socalfreenet.org/mailman/listinfo/discuss_socalfreenet.org>,
	<mailto:discuss-request@socalfreenet.org?subject=unsubscribe>
List-Archive: </pipermail/discuss_socalfreenet.org>
List-Post: <mailto:discuss@socalfreenet.org>
List-Help: <mailto:discuss-request@socalfreenet.org?subject=help>
List-Subscribe: <http://socalfreenet.org/mailman/listinfo/discuss_socalfreenet.org>,
	<mailto:discuss-request@socalfreenet.org?subject=subscribe>
Content-Type: multipart/mixed;
  boundary="===============1272344651=="
Sender: discuss-bounces@socalfreenet.org
Errors-To: discuss-bounces@socalfreenet.org
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - jupiter.dotcolo.com
X-AntiAbuse: Original Domain - theweeks.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - socalfreenet.org
X-Source: 
X-Source-Args: 
X-Source-Dir: 

--===============1272344651==
Content-Type: multipart/alternative; 
	boundary="----=_Part_11802_31420743.1159725394853"

------=_Part_11802_31420743.1159725394853
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

The ability to mesh with other nodes is what making this project special. As
the requirement of "good" wireless coverage is a function of quantity
instead of quality. I've also been playing with the project/devices with
friends and as far as I know the mest routing protocol and maybe some other
factors limited the mesh network growth to about 25-50 nodes, after that the
performance start dropping dramatically.

In my view and i'm experimenting is that if there's enought of these placed
at coffee shop and surrounding businesses it's possible to have very good
and wide coverage by adding lots of these.

The underlying problem with the project is still to improve the routing
protocol to work with installation of said 1000 full mesh node.

-bn

On 10/1/06, Michael Mee <mike@socalfreenet.org> wrote:
>
> At least two years ago, I took a look at the MIT roofnet mesh project
> (currently at http://pdos.csail.mit.edu/roofnet/doku.php). It was far
> from ready for prime time, requiring lots of custom tweaking and a
> non-trivial build process.
>
> Things have changed since then. The current state is one of transition.
> The students who built roofnet have started a company, www.meraki.net,
> which has a cute little ~$50 box that is a gateway ap, bridge, or
> standalone repeater. See http://meraki.net/mini.html.
>
> I've started playing with this (details below) and early indications are
> that it is AWESOME!  You plug it in, it configures itself, works out
> where the gateways are and just runs. You can use it via regular
> wireless or jack in and use it as a bridge. And, of course, you can plug
> in an existing DSL connection. There's even a great website to view the
> current status on a map.
>
> The original roofnet source was open. The new source will be 'mostly
> open' except for some proprietary bits.  A new website, www.roofnet.net,
> will track and support the open source version over time and maintain
> some relationship with Meraki primarily to help low income housing
> projects via www.netequality.org.
>
> Its a tangled web and things are moving quickly. We've received
> permission to be in the Meraki beta (as would anyone I suspect) and I'm
> going to order 4 minis - let me know by Monday if you'd like to piggy
> back as the minimum order size is 3 (though you can't do much with one!).
>
> I've done my testing with reflashed Netgear WRT634U boxes. I bought 5
> "refurbed" from Justdeals - though 2 are dead - and flashed them as
> described at http://roofnet.net/wiki/doku.php?id=netgear.
>
> So far, they work great!  And the roofnet.net web site uses google maps
> to give a  wonderfully clean view of the routes chosen and current
> status. Over the next few days I'll be rolling out units on my street,
> replacing minirelays (www.socalfreenet.org/minirelay) that are currently
> scattered throughout to see how it works in the real world. My neighbors
> will be so glad to have me back (not!) - my street network worked
> perfectly all the time I was away :-).
>
> There is also a version for the Wrap based system we use a lot. If the
> street test goes well, there is a strong chance we'll deploy this
> software very soon to upgrade the Mercado install we did 18 months ago.
> There have been continuing line of sight / signal quality issues that
> this could resolve quite well. We could change all the CF cards in a
> couple of hours, so its a low risk exercise. And remember its zero config.
>
> One particularly nice (rumoured) mode in the Meraki mini lets you use
> the box to connect to an existing (conventional) 802.11b/g network and
> use that as a gateway and then repeat locally and also mesh with any
> nearby minis. Rumour has it that Google bought 1000 of these for their
> employees in Mountain View to get the last part of the connection from
> their recently built muni network outside
> (https://wifi.google.com/support) to inside.
>
> cheers, michael
> R & D, www.socalfreenet.org
>
>
> _______________________________________________
> SoCalFreeNet.org General Discussion List
> To unsubscribe, please visit:
> http://socalfreenet.org/mailman/listinfo/discuss_socalfreenet.org
>



-- 
Bao Nguyen

------=_Part_11802_31420743.1159725394853
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

The ability to mesh with other nodes is what making this project special. As the requirement of &quot;good&quot; wireless coverage is a function of quantity instead of quality. I've also been playing with the project/devices with friends and as far as I know the mest routing protocol and maybe some other factors limited the mesh network growth to about 25-50 nodes, after that the performance start dropping dramatically.
<br><br>In my view and i'm experimenting is that if there's enought of these placed at coffee shop and surrounding businesses it's possible to have very good and wide coverage by adding lots of these.<br><br>The underlying problem with the project is still to improve the routing protocol to work with installation of said 1000 full mesh node.
<br><br>-bn<br><br><div><span class="gmail_quote">On 10/1/06, <b class="gmail_sendername">Michael Mee</b> &lt;<a href="mailto:mike@socalfreenet.org">mike@socalfreenet.org</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
At least two years ago, I took a look at the MIT roofnet mesh project<br>(currently at <a href="http://pdos.csail.mit.edu/roofnet/doku.php">http://pdos.csail.mit.edu/roofnet/doku.php</a>). It was far<br>from ready for prime time, requiring lots of custom tweaking and a
<br>non-trivial build process.<br><br>Things have changed since then. The current state is one of transition.<br>The students who built roofnet have started a company, <a href="http://www.meraki.net">www.meraki.net</a>,<br>
which has a cute little ~$50 box that is a gateway ap, bridge, or<br>standalone repeater. See <a href="http://meraki.net/mini.html">http://meraki.net/mini.html</a>.<br><br>I've started playing with this (details below) and early indications are
<br>that it is AWESOME!&nbsp;&nbsp;You plug it in, it configures itself, works out<br>where the gateways are and just runs. You can use it via regular<br>wireless or jack in and use it as a bridge. And, of course, you can plug<br>in an existing DSL connection. There's even a great website to view the
<br>current status on a map.<br><br>The original roofnet source was open. The new source will be 'mostly<br>open' except for some proprietary bits.&nbsp;&nbsp;A new website, <a href="http://www.roofnet.net">www.roofnet.net</a>,<br>
will track and support the open source version over time and maintain<br>some relationship with Meraki primarily to help low income housing<br>projects via <a href="http://www.netequality.org">www.netequality.org</a>.<br>
<br>Its a tangled web and things are moving quickly. We've received<br>permission to be in the Meraki beta (as would anyone I suspect) and I'm<br>going to order 4 minis - let me know by Monday if you'd like to piggy<br>back as the minimum order size is 3 (though you can't do much with one!).
<br><br>I've done my testing with reflashed Netgear WRT634U boxes. I bought 5<br>&quot;refurbed&quot; from Justdeals - though 2 are dead - and flashed them as<br>described at <a href="http://roofnet.net/wiki/doku.php?id=netgear">
http://roofnet.net/wiki/doku.php?id=netgear</a>.<br><br>So far, they work great!&nbsp;&nbsp;And the <a href="http://roofnet.net">roofnet.net</a> web site uses google maps<br>to give a&nbsp;&nbsp;wonderfully clean view of the routes chosen and current
<br>status. Over the next few days I'll be rolling out units on my street,<br>replacing minirelays (<a href="http://www.socalfreenet.org/minirelay">www.socalfreenet.org/minirelay</a>) that are currently<br>scattered throughout to see how it works in the real world. My neighbors
<br>will be so glad to have me back (not!) - my street network worked<br>perfectly all the time I was away :-).<br><br>There is also a version for the Wrap based system we use a lot. If the<br>street test goes well, there is a strong chance we'll deploy this
<br>software very soon to upgrade the Mercado install we did 18 months ago.<br>There have been continuing line of sight / signal quality issues that<br>this could resolve quite well. We could change all the CF cards in a<br>
couple of hours, so its a low risk exercise. And remember its zero config.<br><br>One particularly nice (rumoured) mode in the Meraki mini lets you use<br>the box to connect to an existing (conventional) 802.11b/g network and
<br>use that as a gateway and then repeat locally and also mesh with any<br>nearby minis. Rumour has it that Google bought 1000 of these for their<br>employees in Mountain View to get the last part of the connection from<br>
their recently built muni network outside<br>(<a href="https://wifi.google.com/support">https://wifi.google.com/support</a>) to inside.<br><br>cheers, michael<br>R &amp; D, <a href="http://www.socalfreenet.org">www.socalfreenet.org
</a><br><br><br>_______________________________________________<br>SoCalFreeNet.org General Discussion List<br>To unsubscribe, please visit: <a href="http://socalfreenet.org/mailman/listinfo/discuss_socalfreenet.org">http://socalfreenet.org/mailman/listinfo/discuss_socalfreenet.org
</a><br></blockquote></div><br><br clear="all"><br>-- <br>Bao Nguyen<br>

------=_Part_11802_31420743.1159725394853--


--===============1272344651==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
SoCalFreeNet.org General Discussion List
To unsubscribe, please visit: http://socalfreenet.org/mailman/listinfo/discuss_socalfreenet.org
--===============1272344651==--

--Boundary-00=_B4BIFh+t0uzVwb2--