OUTLINE BMX@WBMv3
- Background
- Propagating Reachability Information:
- learning about other nodes exitence and profile
Metrics: identifying best routes
(Distributed Hashes and Individual IDentifiers)
Demonstration
- Realtime, emulating a ~40 nodes virtual mesh network
configurable packet loss and delay
- experiment demands from the audience
BACKGROUND BMX@WBMv3
- BMX (acronym for B.a.t.M.a.n - eXperimental)
- historically: experimental branch for testing new features for BATMAN
- more configuration options, new mechanisms, ...
- always executable as # batmand ath0
- generation III-IV temporary compatible to BATMAN
BMX v0.3 evolved towards an independent routing protocol:
- some communities selected BMX for meshinh
(LugroMesh, GraciaSensefills, FFLeipzig, FFDresden, Nicaragua,..)
- larges BATMAN/BMX network in Leipzig (~200 nodes) is BMX
- some communities selected BMX for meshinh
- Winner of Merakas' Routing Protocol Evalutation is BMX (comparing OLSR, BATMAN, BMX)
- Since WBMv3 BMX v0.4 implementation...
Propagating Reachability Information
- Motivation and Ideas
Propagating Reachability Information
Motivation for redesign of propagation mechanism
- (triggered by IPv6 support requests)
1. Idea: Use Hash instead of constant description
2. Idea: Use Individual Identifier (IID) instead of Hash
Metric
Demonstration
Testbed