I’m supposed to be setting up a ‘geolocation based’, ipv6, wireless mesh network to run on google android.
I found what seems to be a good app to support the meshing: http://www.open-mesh.net/wiki/batman-adv
‘Batman-advanced is a new approach to wireless networking which does no longer operate on the IP basis. Unlike B.A.T.M.A.N, which exchanges information using UDP packets and sets routing tables, batman-advanced operates on ISO/OSI Layer 2 only and uses and routes (or better: bridges) Ethernet Frames. It emulates a virtual network switch of all nodes participating. Therefore all nodes appear to be link local, thus all higher operating protocols won’t be affected by any changes within the network. You can run almost any protocol above B.A.T.M.A.N. Advanced, prominent examples are: IPv4, IPv6, DHCP, IPX.’
But other members in my team has said it’s a no-go because it operates on OSI, rather than TCP/IP. This was the first I’d heard of OSI, and I’m wondering how much of a problem this is? What are the implications for mesh network apps that can be developed on top of it? Considering the android is relatively new, we don’t need to worry too much about compatibility with existing apps, so does it matter?
I haven’t spent a lot of time working with networks, so please put in noobmans terms.
‘You can run almost any protocol above B.A.T.M.A.N. Advanced, prominent examples are: IPv4, IPv6, DHCP, IPX.’
‘But other members in my team has said it’s a no-go because it operates on OSI, rather than TCP/IP. ‘
The other members in your team are confused by the buzzword-fest in BATMAN.
The ‘IP’ of TCP/IP is IPv4 (or IPv6). So BATMAN supports TCP/IP directly and completely.
There’s no conflict of any kind. Just confusion.