289
edits
Difference between revisions of "Mesh/BATMAN-adv"
Jump to navigation
Jump to search
added network coding
Jwentwistle (talk | contribs) (→batmand configuration: added version two) |
Jwentwistle (talk | contribs) (added network coding) |
||
| Line 1: | Line 1: | ||
The [http://www.open-mesh.org/projects/batman-adv/wiki batman-adv] is an implementation of the [http://en.wikipedia.org/wiki/B.A.T.M.A.N. BATMAN routing protocol]. The protocol is configured with a file, but these settings can be changed with [http://downloads.open-mesh.org/batman/manpages/batctl.8.html batctl]. The advantage of routing using batman-adv, rather than [https://github.com/cjdelisle/cjdns cjdns], is its a layer two protocol, which can send all types of layers three packets (udp, tcp/ip, etc). The protocol "forwards all traffic until it reaches the destination, hence emulating a virtual network switch of all nodes participating. Therefore all nodes appear to be link local and are unaware of the network's topology as well as unaffected by any network changes.<ref>[http://www.open-mesh.org/projects/batman-adv/wiki/Wiki BATMAN advanced overview]</ref>" | The [http://www.open-mesh.org/projects/batman-adv/wiki batman-adv] is an implementation of the [http://en.wikipedia.org/wiki/B.A.T.M.A.N. BATMAN routing protocol]. The protocol is configured with a file, but these settings can be changed with [http://downloads.open-mesh.org/batman/manpages/batctl.8.html batctl]. The advantage of routing using batman-adv, rather than [https://github.com/cjdelisle/cjdns cjdns], is its a layer two protocol, which can send all types of layers three packets (udp, tcp/ip, etc). The protocol "forwards all traffic until it reaches the destination, hence emulating a virtual network switch of all nodes participating. Therefore all nodes appear to be link local and are unaware of the network's topology as well as unaffected by any network changes.<ref>[http://www.open-mesh.org/projects/batman-adv/wiki/Wiki BATMAN advanced overview]</ref>" | ||
= [http://downloads.open-mesh.org/batman/manpages/batctl.8.html batctl] configuration= | = [http://downloads.open-mesh.org/batman/manpages/batctl.8.html batctl] configuration= | ||
| Line 11: | Line 11: | ||
* [http://www.open-mesh.org/projects/batman-adv/wiki/Fragmentation-technical fragmentation] - a driver that sets fragmentation, which sends frames in fragmented frames when a wireless interfaces can't send/receive packets more than 1500 bytes. The protocol adds its own header to existing frames, which makes the packets have 1528 bytes. | * [http://www.open-mesh.org/projects/batman-adv/wiki/Fragmentation-technical fragmentation] - a driver that sets fragmentation, which sends frames in fragmented frames when a wireless interfaces can't send/receive packets more than 1500 bytes. The protocol adds its own header to existing frames, which makes the packets have 1528 bytes. | ||
* gw_mode - a server is an internet gateway, a client sends and receives traffic to and from the gateway | * gw_mode - a server is an internet gateway, a client sends and receives traffic to and from the gateway | ||
* [http://www.open-mesh.org/projects/batman-adv/wiki/NetworkCoding nc] (network coding) - when forwarding packets in a wireless mesh network, bandwidth can be saved by exploiting the information already present at the destinations of a forward. One way of doing this is network coding, where two packets are combined before transmission. | |||
* traceroute - tries to find the bat-host name if the given parameter was not a MAC address. It can also try to guess the MAC address using an IPv4/IPv6 address or a hostname when the IPv4/IPv6 address was configured on top of the batman-adv interface of the destination device and both source and destination devices are in the same IP subnet. | * traceroute - tries to find the bat-host name if the given parameter was not a MAC address. It can also try to guess the MAC address using an IPv4/IPv6 address or a hostname when the IPv4/IPv6 address was configured on top of the batman-adv interface of the destination device and both source and destination devices are in the same IP subnet. | ||