There are plenty of mesh protocols available - 802.11s, batman, olsr, and my own fav babel. 802.11s operates at layer 2, is limited to 32 nodes, and has other issues, so I tend to ignore it. batman-adv is also layer too but much more flexible and interesting.
But as for babel, I like it because it is a pure layer 3 protocol, it handles ipv6 and ipv4, and has a pluggable metric. http://babelweb.kerneis.info:8080/ shows a live babel based mesh network. as is http://carme.lab.bufferbloat.net:8080/ (via this software. http://www.pps.univ-paris-diderot.fr/~kerneis/software/babelweb/ setting up a babel mesh on ad-hoc is simple, this is the simplest possible demo... build and install babeld and ahcp on all nodes All connected nodes share the same ssid and channel. (for diversity routing just change the channel) On all nodes, disable Network manager and anything else that automates ip getting ifconfig wlan0 down iwconfig wlan0 mode ad-hoc channel 1 essid babel # channel and essid are arbitrary. Some devices won't let you do that in one pass ifconfig wlan0 up babeld -D -z3 eth0 wlan0 ifconfig wlan0 172.20.0.1/32 # for the first node ifconfig wlan0 172.20.0.2/32 # for the second node ifconfig wlan0 172.20.0.3/32 # etc You can use the same ip addresses for your ethernet addresses as life is figured out via the address/interface tuple. If you do that, you can do transparent failover from ethernet to wireless. If you don't, like on any routed network, you need to make sure your address ranges/netmask are disjoint ifconfig eth0 172.20.0.1/32 # for the first node ifconfig eth0 172.20.0.2/32 # for the second node ifconfig eth0 172.20.0.3/32 # etc Now, it's easier to just setup an ahcp server to hand out addresses, and use ahcp for setup, but that's too long to go into the margins here. On Wed, Jun 20, 2012 at 9:28 AM, Rick C. Hodgin <[email protected]> wrote: > Matthias-Christian, > > I appreciate your response. If the research is available let's get it out > there and find the software and steps to setup mesh networks on FBX. > > > Best regards, > Rick C. Hodgin > > On 06/20/2012 08:50 AM, Matthias-Christian Ott wrote: >> >> On 2012-06-20 14:23, Rick C. Hodgin wrote: >>> >>> The protocol will establish what information is necessary to maintain a >>> living, dynamic mesh, how to route packets, etc. I will also work on >>> protocols for fixed placement FBXs (in a home, street lamp), as well as >>> roaming FBXs (carrying one on a backpack, bicycle, car). >> >> I don't fully understand what you are trying to do here and haven't >> looked at the software you created, but if you want to simulate wireless >> mesh networks, I found that ns-3 [1] works (I had to use it during a >> course on networks which included simulation wireless mesh networks and >> simple evaluations of routing algorithms), so I guess you don't have to >> write your own software. >> >> Regards, >> Matthias-Christian >> >> [1] http://www.nsnam.org/ >> >> _______________________________________________ >> Freedombox-discuss mailing list >> [email protected] >> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss >> > > _______________________________________________ > Freedombox-discuss mailing list > [email protected] > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss -- Dave Täht SKYPE: davetaht http://ronsravings.blogspot.com/ _______________________________________________ Freedombox-discuss mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
