|
|
| (29 intermediate revisions by 4 users not shown) |
| Line 1: |
Line 1: |
| == OLSR vs B.A.T.M.A.N Layer2 vs B.A.T.M.A.N Layer3 ==
| |
|
| |
|
| The biggest requirement of any network is that it should be stable. After that you get all the other features like speed, ease of use, supported features etc. In a development network one can tolerate some degree of instability while working on new functionalities, but on a network that will be used by other parties should be rock solid and stable. The biggest factor about introducing any new protocols in a network, is that one needs a certain amount of time to test and make sure that everything is stable and usable.
| | migrated to wireless dev |
| | |
| === OLSR ===
| |
| Pros
| |
| * Proven and stable
| |
| * Scales well
| |
| * Support both IPv4 and IPv6
| |
| | |
| Conns
| |
| * Routing information packets can become big
| |
| * Lots of network overheads to food routing information
| |
| | |
| === B.A.T.M.A.N L2 ===
| |
| Pros
| |
| * Works on L2 and is protocol independent (support both IPv4 and IPv6)
| |
| * Can use DHCP for automatic IPv4 addressing
| |
| | |
| Conns
| |
| * No FreeBSD port
| |
| * Not mature protocol, still in developing state
| |
| * Problems with multi-radio nodes: https://lists.open-mesh.net/pipermail/b.a.t.m.a.n/2009-February/002405.html
| |
| | |
| === B.A.T.M.A.N L3 ===
| |
| Batman was designed for a single radio, single channel mesh.
| |
| | |
| Pros
| |
| | |
| Conns
| |
| * No IPv6 support
| |
| * No FreeBSD port
| |
| * Not mature protocol, still in developing state
| |
| | |
| Random thoughts that I need to sort.
| |
| *
| |