<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
I prefer to use just one radio because multiple radio's will interfere
with each other if placed close together. Even if one is on channel 1
and the other on channel 11 there can be some bleedover which will
cause a lot of lost packets.<br>
<br>
Tim<br>
<br>
<br>
Rajesh Narayanan wrote:
<blockquote
cite="mid8e843e380701251442w2e7a7de2qad48f6fd4c776d87@mail.gmail.com"
type="cite">Hi,<br>
<br>
I posted this in the openwrt forum as well. Thought I might as well
stir the hornets nest a little more. Only the OLSR part is specifically
relevant . Has anyone looked at multi-radio multi-channel support in
the OLSR though???
<br>
<br>
I'm trying to look at any open-source implementations for MCMR. If I do
find I'll post it here. <br>
<br>
Thanks,<br>
Rajesh.<br>
<br>
Here is the post <br>
***************************<br>
It just occured to me that there might be a possible for
supporting multi-radio multi-channel support in the OpenWRT platform.
Many mesh-networking companies typically tout multi-radio/multi-channel
support. <br>
<br>
Here is a possible method by which three Linksys routers can be
combined to support multi-radio multi-channel. <br>
<br>
Methodology:<br>
1. Hardware<br>
- Put the three linksys (could be any other device) routers in
Bridge mode. <br>
- The three routers are physically connected via the ethernet LAN
ports <br>
- Lets call these routers LS1, LS2 and LS3.<br>
- I have tested the bridge-mode connection and works quite well<br>
- Essentially provides a very wide Layer2 connection
<br>
- These three linksys routers can be stacked on top of each other
essentially providing 3 radios (you could use 2 for 2 radios)<br>
- This will how a Node-group will look like <br>
\ / <-- Radio1<br>
Node1a<br>
| <----------- Wired link
<br>
\ | / <-- Radio2<br>
Node1b<br>
| <----------- Wired link<br>
\ | / <-- Radio3<br>
Node1c
<br>
<br>
2. Software<br>
- This is the secret-sauce that needs to be developed. The goal is:<br>
- Launch it in each of the routers LS1, LS2, LS3<br>
- Communicate among each other to know they are part of the same
bridge
<br>
- Have a channel allocation scheme for each router so they do not
mutually interfere with each other.<br>
- This needs to be a modular and scalable architecture so that
nodes can be added to the stack in an on-demand basis.
<br>
- The secret sauce could be developed either as a plugin for OLSR
or for the spanning-tree-protocol implementation.<br>
- The STP implementation would mean that its one big layer-2 wireless
network with the node-groups forming some kind of non-loop network<br>
- OLSR-plugin would obviously mean that all node-groups act as
olsr-routers with intelligent channel assignment schemes.<br>
<br>
3. References:<br>
*
While writing this post I did some web-search and looks like there is
already some activity that is similar to what I am suggesting - <a
href="http://moment.cs.ucsb.edu/tic/">http://moment.cs.ucsb.edu/tic/</a><br>
* (more references later)
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
olsr-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:olsr-users@olsr.org">olsr-users@olsr.org</a>
<a class="moz-txt-link-freetext" href="https://www.olsr.org/mailman/listinfo/olsr-users">https://www.olsr.org/mailman/listinfo/olsr-users</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Stop Spam Now: <a class="moz-txt-link-freetext" href="http://www.spamarrest.com/affl?4025320">http://www.spamarrest.com/affl?4025320</a>
</pre>
</body>
</html>