687937ab34
With this patch we are finally able to support multicast optimizations in bridged setups, too. So far, if a bridge was added on top of a soft-interface (e.g. bat0) the batman-adv multicast optimizations needed to be disabled to avoid packetloss. Current Linux bridge implementations and API can now provide us with the so far missing information about interested but "remote" multicast receivers behind bridge ports. The Linux bridge performs the detection of remote participants interested in multicast packets with its own and mature so called IGMP and MLD snooping code and stores that in its database. With the new API provided by the bridge batman-adv can now simply hook into this database. We then reliably announce the gathered multicast listeners to other nodes through the batman-adv translation table. Additionally, the Linux bridge provides us with the information about whether an IGMP/MLD querier exists. If there is none then we need to disable multicast optimizations as we cannot learn about multicast listeners on external, bridged-in host then. Tested-by: Simon Wunderlich <sw@simonwunderlich.de> Signed-off-by: Linus Lüssing <linus.luessing@c0d3.blue> Signed-off-by: Marek Lindner <mareklindner@neomailbox.ch> Signed-off-by: Sven Eckelmann <sven@narfation.org> Signed-off-by: Simon Wunderlich <sw@simonwunderlich.de>
85 lines
2.9 KiB
Plaintext
85 lines
2.9 KiB
Plaintext
#
|
|
# B.A.T.M.A.N meshing protocol
|
|
#
|
|
|
|
config BATMAN_ADV
|
|
tristate "B.A.T.M.A.N. Advanced Meshing Protocol"
|
|
depends on NET
|
|
select CRC16
|
|
select LIBCRC32C
|
|
default n
|
|
help
|
|
B.A.T.M.A.N. (better approach to mobile ad-hoc networking) is
|
|
a routing protocol for multi-hop ad-hoc mesh networks. The
|
|
networks may be wired or wireless. See
|
|
https://www.open-mesh.org/ for more information and user space
|
|
tools.
|
|
|
|
config BATMAN_ADV_BATMAN_V
|
|
bool "B.A.T.M.A.N. V protocol (experimental)"
|
|
depends on BATMAN_ADV && CFG80211=y || (CFG80211=m && BATMAN_ADV=m)
|
|
default n
|
|
help
|
|
This option enables the B.A.T.M.A.N. V protocol, the successor
|
|
of the currently used B.A.T.M.A.N. IV protocol. The main
|
|
changes include splitting of the OGM protocol into a neighbor
|
|
discovery protocol (Echo Location Protocol, ELP) and a new OGM
|
|
Protocol OGMv2 for flooding protocol information through the
|
|
network, as well as a throughput based metric.
|
|
B.A.T.M.A.N. V is currently considered experimental and not
|
|
compatible to B.A.T.M.A.N. IV networks.
|
|
|
|
config BATMAN_ADV_BLA
|
|
bool "Bridge Loop Avoidance"
|
|
depends on BATMAN_ADV && INET
|
|
default y
|
|
help
|
|
This option enables BLA (Bridge Loop Avoidance), a mechanism
|
|
to avoid Ethernet frames looping when mesh nodes are connected
|
|
to both the same LAN and the same mesh. If you will never use
|
|
more than one mesh node in the same LAN, you can safely remove
|
|
this feature and save some space.
|
|
|
|
config BATMAN_ADV_DAT
|
|
bool "Distributed ARP Table"
|
|
depends on BATMAN_ADV && INET
|
|
default n
|
|
help
|
|
This option enables DAT (Distributed ARP Table), a DHT based
|
|
mechanism that increases ARP reliability on sparse wireless
|
|
mesh networks. If you think that your network does not need
|
|
this option you can safely remove it and save some space.
|
|
|
|
config BATMAN_ADV_NC
|
|
bool "Network Coding"
|
|
depends on BATMAN_ADV
|
|
default n
|
|
help
|
|
This option enables network coding, a mechanism that aims to
|
|
increase the overall network throughput by fusing multiple
|
|
packets in one transmission.
|
|
Note that interfaces controlled by batman-adv must be manually
|
|
configured to have promiscuous mode enabled in order to make
|
|
network coding work.
|
|
If you think that your network does not need this feature you
|
|
can safely disable it and save some space.
|
|
|
|
config BATMAN_ADV_MCAST
|
|
bool "Multicast optimisation"
|
|
depends on BATMAN_ADV && INET && !(BRIDGE=m && BATMAN_ADV=y)
|
|
default n
|
|
help
|
|
This option enables the multicast optimisation which aims to
|
|
reduce the air overhead while improving the reliability of
|
|
multicast messages.
|
|
|
|
config BATMAN_ADV_DEBUG
|
|
bool "B.A.T.M.A.N. debugging"
|
|
depends on BATMAN_ADV
|
|
depends on DEBUG_FS
|
|
help
|
|
This is an option for use by developers; most people should
|
|
say N here. This enables compilation of support for
|
|
outputting debugging information to the kernel log. The
|
|
output is controlled via the module parameter debug.
|