Differences between revisions 35 and 37 (spanning 2 versions)
Revision 35 as of 2007-07-19 07:52:54
Size: 3141
Revision 37 as of 2007-08-02 10:50:06
Size: 3143
Editor: pool-71-117-214-166
Deletions are marked like this. Additions are marked like this.
Line 43: Line 43:
 * OLSR (Optimized Link State Routing)  * ["OLSR"] (Optimized Link State Routing)
Line 59: Line 59:

The ManSig is trying to figure out how to build out and scale community networks. There are several key issues with wireless networks and community networks which are less of an issue with commercial wired networks. -- AdamShand

With community networks each node is often owned by a separate person, further there are no paid admin staff to come to the rescue if the network fails. Thus it is important that the network be architected in a manner that faults are as localized as possible. In other words the death of one node or router shouldn't be able to paralyze a large chunk of the network.

With wireless networks the key issue is that it is very geographically specific. Consumer grade wireless protocols (specifically 802.11b) run at high frequencies and have a fairly limited range (100 feet to a couple of miles). This means that building a fully meshed network can be tricky through to impossible.

Because of these reasons we see AdHoc routing protocols as the key to our success in the ["NAN"] arena (the ["MAN"] will probably use a more traditional network structure).

See also: Peer2PeerRouting

Here is a list of some of the OpenSource AdHoc routing protocols that we are aware of. As we gain experience with them we will update these pages with what we learn.

And some commercial software:


AdhocRouting (last edited 2007-11-23 18:00:43 by localhost)