Hi Guys,
I'm looking at making a small mesh network using dual radio's and BATMAN advanced and was after some advice to make sure I'm heading the right direction. The application is just a basic hotspot covering a large area, all traffic would need to come back to the captive portal server which would be 2-3 hops away maximum.
I'm using OpenWRT with a 5.8GHz 802.11n radio for backhaul and 2.4GHz 802.11b/g for serving non BATMAN clients. I'm going to run BATMAN Adv on the backhaul network and bridge it to the client radio which would effectively make it one giant layer 2 mesh. In this situation, would users on the b/g radio's be able to roam between nodes? Am I better off removing the bridge between the mesh and the client radio and use layer 3 routing or NAT instead?
Eventually I'd like to run PPPoE and do some point to point VPN's over the mesh but the hotspot is my starting point. If anyone has any constructive criticism or words of wisdom it would be much appreciated.
Thanks -Matt
On Thursday 01 July 2010 05:22:11 Matthew Anderson wrote:
I'm using OpenWRT with a 5.8GHz 802.11n radio for backhaul and 2.4GHz 802.11b/g for serving non BATMAN clients. I'm going to run BATMAN Adv on the backhaul network and bridge it to the client radio which would effectively make it one giant layer 2 mesh. In this situation, would users on the b/g radio's be able to roam between nodes? Am I better off removing the bridge between the mesh and the client radio and use layer 3 routing or NAT instead?
You got it right - bridge the 2.4GHz network with batman's interface (bat0) while batman itself runs on 5.8Ghz and your clients can happily roam around. Layer 3 routing or NAT is not the way to go if you want roaming.
Cheers, Marek
b.a.t.m.a.n@lists.open-mesh.org
-
Marek Lindner -
Matthew Anderson