[MLB-WIRELESS] meshing

David Arnold arnold at dstc.monash.edu.au
Mon Jan 21 14:02:40 EST 2002


-->"Jason" == Jason Hecker <jason at air.net.au> writes:

  Jason> Also, the more antennas that go up, the more flexible the
  Jason> routes as well.  So if someone goes down, the mesh can
  Jason> automatically readapt and deal with it.

let's distinguish between an ad-hoc mesh, where all nodes are routers
and use omni-directional radio, and a configured backbone architecture
with redundant uni-directional links.

such a backbone architecture gives you nearly as much resilence, with
a much better chance of getting reasonable bandwidth, fewer problems
of people having their bandwidth sucked unwillingly, and will work
with well-understood routing algorithms.

pure ad-hoc mesh networks have poorly understood routing behaviour,
less predictable (and manageable) bandwidth usage, and require a radio
setup that is more prone to interference as well.





d

--
To unsubscribe, send mail to minordomo at melbwireless.dyndns.org with a subject of 'unsubscribe melbwireless'  
Archive at: http://melbwireless.dyndns.org/cgi-bin/minorweb.pl?A=LIST&L=melbwireless
IRC at: au.austnet.org #melb-wireless



More information about the Melbwireless mailing list