Skip to contentSkip to conversation

batman-adv 2014.0.0 released

B.A.T.M.A.N. Marek Lindner 5 participants 17 messages Jan 7, 2014 – Feb 11, 2014 2 messages not in the archive

lore
Share & tools
lore
#0 lore raw

The B.A.T.M.A.N. team is pleased to announce the immediate availability of batman-adv 2014.0.0 - a release coming with a rewritten packet handling engine and many new features almost uniquely tailored to preserve backward compatibility in the future. As the kernel module always depends on the Linux kernel it was compiled against, it does not make sense to provide binaries on our website. As usual, you will find the signed tarballs in our download section:

http://downloads.open-mesh.org/batman/releases/batman-adv-2014.0.0/

as well as prepackaged binaries in your distribution.

Important changes
-----------------

*Compatibility break*: In 2011, batman-adv broke backward compatibility with the introduction of the translation table mechanism. Since then, interests have been divided between those who wish a stable network with as little changes as possible and those who wish to experiment with new features to bring meshing to the next level. To accommodate both groups the batman-adv developers dedicated a lot of effort on building code infrastructure allowing to mix stable nodes with new features without breaking compatibility. This new system is incompatible to the pre-2014.0.0 versions, but it has been designed to stay compatible with future versions for the next decade or so.

At the same time, the legacy visualization support was removed from the kernel module. The alfred user space module provides an adequate replacement.

Thanks
------

Thanks to all people sending in patches:

* Antonio Quartulli <[email protected]>
* Joe Perches <[email protected]>
* Linus Lüssing <[email protected]>
* Marco Dalla Torre <[email protected]>
* Marek Lindner <[email protected]>
* Martin Hundebøll <[email protected]>
* Simon Wunderlich <[email protected]>
* Spyros Gasteratos <[email protected]>
* Sven Eckelmann <[email protected]>
* Tan Xiaojun <[email protected]>

batman-adv
----------

Transforming a rather static design to a module architecture in the interest of preserving backward compatibility requires modifications on a multitude of levels. The principal idea behind the TVLV (type-version-length-value) infrastructure is to break up mesh management data into logic chunks (containers) which can be extended in the future while preserving backward compatibility. If a mesh participant receives an unknown TVLV type or version of a certain container it can simply skip the current container and proceed with the next. Therefore, all non-routing data sent with OGMs (e.g. gateway advertisement, translation table data, etc) were transformed to TVLV containers that are still attached to OGMs. In addition, translation table request & response packets as well as roaming advertisement packets were transformed to TVLV containers too.
While designing the containers a couple of feature requests were also
addressed: The compressed download & upload gateway bandwidth (known as 'gateway class') was replaced by uncompressed bandwidth information permitting granular gateway bandwidth announcement. DAT and network coding feature support is communicated into the mesh through TVLV containers as both subsystems optimize their performance based on the knowledge which mesh participant has the feature enabled.
In the interest of backward compatibility on the packet forwarding level batman-adv received a general unicast packet forwarding mechanism. This mechanism forwards or drops unknown packet types based on the packet type numbering.

The batman-adv built-in packet fragmentation has been redesigned and rewritten as part of the 'fragmentation 2' Google Summer of Code project. Major design goals include: Variable number of fragments (up to 16), generic fragmentation framework capable of handling all types of traffic (the 'old' fragmentation code was limited to payload unicast packets) and 'upper layer' transparency through early re-assembly. The maximum of local clients the translation table is able to handle went up by a factor of 16 (the maximum number of fragmented packets) as full translation table exchanges are able to take advantage of the newly introduced generic fragmentation. If the fragmentation is disabled or the MTU altered the local translation table is automatically reduced to fit the new maximum translation table size. Part of the increased maximum table size is the transition from CRC16 consistency checksumming to CRC32 to reduce collision probability and take advantage of hardware acceleration support. The translation table also gained full VLAN awareness making it the final component receiving full VLAN support. Non-mesh clients are now entirely separated on a per-VLAN basis. As a consequence, the bridge loop avoidance is capable of resolving bridge loops more elegantly (one VLAN might be bridged into the LAN while another one is not), the Distributed ARP Table (DAT) builds its distributed IP-MAC address hash on a per-VLAN basis and the AP isolation allows fine-grained control over which VLAN should be isolated and which should not.

The kernel module sets a dummy rx mode handler on batman-adv' virtual interface creation to be able to accepts static multicast listener configurations on top of the batX interface. In order to help wireless drivers to select the suitable traffic queue (e.g. WMM queues), batman-adv peeks into the encapsulated payload IP or VLAN header and sets the skb priority field accordingly. This priority field is used whenever the lower layer drivers (like wireless or ethernet drivers) are unable to retrieve the prioritization themselves due to the batman-adv traffic encapsulation.

batctl
------

As part of our ongoing effort for better IPv6 support quite a few missing pieces have been tackled: The IP-address-to-MAC-address resolver was extended to also support IPv6 addresses. This was achieved by porting the internal resolver from the '/proc/net/arp' based approach to the RTNL API. As a result the translate, ping and traceroute commands accept IPv6 addresses as destination argument which batctl tries to convert back to MAC addresses in similar to the IPv4 conversion. Furthermore, the tcpdump component was enriched with an IPv6 parser being able to decapsulate TCP, UDP and common ICMPv6 packet types.
The vis export feature has been removed as the kernel module no longer supports the visualization protocol. A number of cleanups and smaller fixes such as marking local functions as static, adding header include guards and more found their way into this release as well.

alfred
------

The missing libmath linker flag of the alfred-gpsd component was fixed and its manpage installation arranged.

Happy routing,
The B.A.T.M.A.N. team

#1 lore raw

Hello

Withing the next month or 2 i will be deploying new firmware in my mesh overseas. I am now testing 2014 and if everything seems ok; the new builds will have and i can report results. (my current build that was to be deployed has 2013.4.0-1 v14.

Has anyone started any tests ? If so any results or conclusions in comparison to previous versions ?

Regarding the docs @
http://www.open-mesh.org/projects/batman-adv/wiki/Batman-adv-openwrt-config
are they to be updated or to stay as they are ?

The reason i ask is because there seems to be necessary changes such as:

batman_adv: bat0: The MTU of interface adhoc0 is too small (1528) to handle the transport of batman-adv packets. Packets going over this interface will be fragmented on layer2 which could impact the performance. Setting the MTU to 1546 would solve the problem.

Are there any other changes hat may need to be done for 2014 ?

Quoted 136 lines · Marek Lindner

The B.A.T.M.A.N. team is pleased to announce the immediate availability of batman-adv 2014.0.0 - a release coming with a rewritten packet handling engine and many new features almost uniquely tailored to preserve backward compatibility in the future. As the kernel module always depends on the Linux kernel it was compiled against, it does not make sense to provide binaries on our website. As usual, you will find the signed tarballs in our download section:

http://downloads.open-mesh.org/batman/releases/batman-adv-2014.0.0/

as well as prepackaged binaries in your distribution.

Important changes
-----------------

*Compatibility break*: In 2011, batman-adv broke backward compatibility with the introduction of the translation table mechanism. Since then, interests have been divided between those who wish a stable network with as little changes as possible and those who wish to experiment with new features to bring meshing to the next level. To accommodate both groups the batman-adv developers dedicated a lot of effort on building code infrastructure allowing to mix stable nodes with new features without breaking compatibility. This new system is incompatible to the pre-2014.0.0 versions, but it has been designed to stay compatible with future versions for the next decade or so.

At the same time, the legacy visualization support was removed from the kernel module. The alfred user space module provides an adequate replacement.

Thanks
------

Thanks to all people sending in patches:

* Antonio Quartulli <[email protected]>
* Joe Perches <[email protected]>
* Linus Lüssing <[email protected]>
* Marco Dalla Torre <[email protected]>
* Marek Lindner <[email protected]>
* Martin Hundebøll <[email protected]>
* Simon Wunderlich <[email protected]>
* Spyros Gasteratos <[email protected]>
* Sven Eckelmann <[email protected]>
* Tan Xiaojun <[email protected]>

batman-adv
----------

Transforming a rather static design to a module architecture in the interest of preserving backward compatibility requires modifications on a multitude of levels. The principal idea behind the TVLV (type-version-length-value) infrastructure is to break up mesh management data into logic chunks (containers) which can be extended in the future while preserving backward compatibility. If a mesh participant receives an unknown TVLV type or version of a certain container it can simply skip the current container and proceed with the next. Therefore, all non-routing data sent with OGMs (e.g. gateway advertisement, translation table data, etc) were transformed to TVLV containers that are still attached to OGMs. In addition, translation table request & response packets as well as roaming advertisement packets were transformed to TVLV containers too.
While designing the containers a couple of feature requests were also
addressed: The compressed download & upload gateway bandwidth (known as 'gateway class') was replaced by uncompressed bandwidth information permitting granular gateway bandwidth announcement. DAT and network coding feature support is communicated into the mesh through TVLV containers as both subsystems optimize their performance based on the knowledge which mesh participant has the feature enabled.
In the interest of backward compatibility on the packet forwarding level batman-adv received a general unicast packet forwarding mechanism. This mechanism forwards or drops unknown packet types based on the packet type numbering.

The batman-adv built-in packet fragmentation has been redesigned and rewritten as part of the 'fragmentation 2' Google Summer of Code project. Major design goals include: Variable number of fragments (up to 16), generic fragmentation framework capable of handling all types of traffic (the 'old' fragmentation code was limited to payload unicast packets) and 'upper layer' transparency through early re-assembly. The maximum of local clients the translation table is able to handle went up by a factor of 16 (the maximum number of fragmented packets) as full translation table exchanges are able to take advantage of the newly introduced generic fragmentation. If the fragmentation is disabled or the MTU altered the local translation table is automatically reduced to fit the new maximum translation table size. Part of the increased maximum table size is the transition from CRC16 consistency checksumming to CRC32 to reduce collision probability and take advantage of hardware acceleration support. The translation table also gained full VLAN awareness making it the final component receiving full VLAN support. Non-mesh clients are now entirely separated on a per-VLAN basis. As a consequence, the bridge loop avoidance is capable of resolving bridge loops more elegantly (one VLAN might be bridged into the LAN while another one is not), the Distributed ARP Table (DAT) builds its distributed IP-MAC address hash on a per-VLAN basis and the AP isolation allows fine-grained control over which VLAN should be isolated and which should not.

The kernel module sets a dummy rx mode handler on batman-adv' virtual interface creation to be able to accepts static multicast listener configurations on top of the batX interface. In order to help wireless drivers to select the suitable traffic queue (e.g. WMM queues), batman-adv peeks into the encapsulated payload IP or VLAN header and sets the skb priority field accordingly. This priority field is used whenever the lower layer drivers (like wireless or ethernet drivers) are unable to retrieve the prioritization themselves due to the batman-adv traffic encapsulation.

batctl
------

As part of our ongoing effort for better IPv6 support quite a few missing pieces have been tackled: The IP-address-to-MAC-address resolver was extended to also support IPv6 addresses. This was achieved by porting the internal resolver from the '/proc/net/arp' based approach to the RTNL API. As a result the translate, ping and traceroute commands accept IPv6 addresses as destination argument which batctl tries to convert back to MAC addresses in similar to the IPv4 conversion. Furthermore, the tcpdump component was enriched with an IPv6 parser being able to decapsulate TCP, UDP and common ICMPv6 packet types.
The vis export feature has been removed as the kernel module no longer supports the visualization protocol. A number of cleanups and smaller fixes such as marking local functions as static, adding header include guards and more found their way into this release as well.

alfred
------

The missing libmath linker flag of the alfred-gpsd component was fixed and its manpage installation arranged.

Happy routing,
The B.A.T.M.A.N. team

#2 lore raw

Hi,

Quoted 4 lines · cmsv

batman_adv: bat0: The MTU of interface adhoc0 is too small (1528) to handle the transport of batman-adv packets. Packets going over this interface will be fragmented on layer2 which could impact the performance. Setting the MTU to 1546 would solve the problem.

Did you enable network coding? That would explain the message, as NC uses a larger header to make decoding possible at the receiver side.

As far as I can tell from a quick look in packet.h, the required MTU should be 1532 now. (10 bytes unicast + 8 bytes extra for unicast_4addr
+ 14 ethernet = 32 bytes). Or am I bad at counting bytes?

// Martin

Signature · 8 lines
Kind Regards
Martin Hundebøll
Frederiks Allé 99, 1.th
8000 Aarhus C
Denmark

+45 61 65 54 61
[email protected]
#3 lore raw

inline:

Quoted 10 lines · Martin Hundebøll

Hi,

Quoted 4 lines · cmsv

batman_adv: bat0: The MTU of interface adhoc0 is too small (1528) to handle the transport of batman-adv packets. Packets going over this interface will be fragmented on layer2 which could impact the performance. Setting the MTU to 1546 would solve the problem.

Did you enable network coding? That would explain the message, as NC uses a larger header to make decoding possible at the receiver side.

Yes it is enabled by default as it was with batavd 2013.4.0 with 1528 mtu

Quoted 4 lines

As far as I can tell from a quick look in packet.h, the required MTU should be 1532 now. (10 bytes unicast + 8 bytes extra for unicast_4addr
+ 14 ethernet = 32 bytes). Or am I bad at counting bytes?

Regardless of being properly counted or not; dmesg outputs the message complaining about the need to make mtu 1546.

Quoted 2 lines

// Martin

#4 lore raw
Quoted 13 lines · cmsv

inline:

Quoted 10 lines · Martin Hundebøll

Hi,

Quoted 4 lines · cmsv

batman_adv: bat0: The MTU of interface adhoc0 is too small (1528) to handle the transport of batman-adv packets. Packets going over this interface will be fragmented on layer2 which could impact the performance. Setting the MTU to 1546 would solve the problem.

Did you enable network coding? That would explain the message, as NC uses a larger header to make decoding possible at the receiver side.

Quoted 8 lines

Yes it is enabled by default as it was with batavd 2013.4.0 with 1528 mtu

Quoted 4 lines

As far as I can tell from a quick look in packet.h, the required MTU should be 1532 now. (10 bytes unicast + 8 bytes extra for unicast_4addr
+ 14 ethernet = 32 bytes). Or am I bad at counting bytes?

Regardless of being properly counted or not; dmesg outputs the message complaining about the need to make mtu 1546.

If you disable network coding the message will change.

The overhead is dynamic depending on NC being enabled or not and now the message in dmesg tells you exactly what MTU you need.

Cheers,

Signature · 1 line
Antonio Quartulli
#5 lore raw
Quoted 20 lines · Antonio Quartulli
Quoted 19 lines · cmsv

inline:

Quoted 10 lines · Martin Hundebøll

Hi,

Quoted 4 lines · cmsv

batman_adv: bat0: The MTU of interface adhoc0 is too small (1528) to handle the transport of batman-adv packets. Packets going over this interface will be fragmented on layer2 which could impact the performance. Setting the MTU to 1546 would solve the problem.

Did you enable network coding? That would explain the message, as NC uses a larger header to make decoding possible at the receiver side.

Yes it is enabled by default as it was with batavd 2013.4.0 with 1528 mtu

Quoted 4 lines

As far as I can tell from a quick look in packet.h, the required MTU should be 1532 now. (10 bytes unicast + 8 bytes extra for unicast_4addr
+ 14 ethernet = 32 bytes). Or am I bad at counting bytes?

Quoted 7 lines
Quoted 2 lines

Regardless of being properly counted or not; dmesg outputs the message complaining about the need to make mtu 1546.

If you disable network coding the message will change.

The overhead is dynamic depending on NC being enabled or not and now the message in dmesg tells you exactly what MTU you need.

Yes i understand that but it keeps on increasing.

[   28.600000] batman_adv: bat0: The MTU of interface adhoc0 is too

small (1546) to handle the transport of batman-adv packets. Packets going over this interface will be fragmented on layer2 which could impact the performance. Setting the MTU to 1560 would solve the problem.

Quoted 4 lines

Cheers,

#6 lore raw
Quoted 5 lines · cmsv

Yes i understand that but it keeps on increasing.

[   28.600000] batman_adv: bat0: The MTU of interface adhoc0 is too

small (1546) to handle the transport of batman-adv packets. Packets going over this interface will be fragmented on layer2 which could impact the performance. Setting the MTU to 1560 would solve the problem.

Have you tried applying this patch before testing it once again?

http://git.open-mesh.org/batman-adv.git/commit/746d6436f88899a79c1cb3b27af0614510368bb7

Cheers,

Signature · 1 line
Antonio Quartulli
#7 lore raw
Quoted 11 lines · Antonio Quartulli
Quoted 5 lines · cmsv

Yes i understand that but it keeps on increasing.

[   28.600000] batman_adv: bat0: The MTU of interface adhoc0 is too

small (1546) to handle the transport of batman-adv packets. Packets going over this interface will be fragmented on layer2 which could impact the performance. Setting the MTU to 1560 would solve the problem.

Have you tried applying this patch before testing it once again?

http://git.open-mesh.org/batman-adv.git/commit/746d6436f88899a79c1cb3b27af0614510368bb7

Actually this patch is already part of the batman-adv package in openwrt. Therefore the question turns in: did you update the batman-adv package before performing your second test?

Cheers,

Signature · 1 line
Antonio Quartulli

A message that is not in the archive (sent off-list or not yet received): [email protected]

#9 lore raw
Quoted 13 lines · cmsv
Quoted 10 lines · Antonio Quartulli
Quoted 9 lines · Antonio Quartulli
Quoted 5 lines · cmsv

Yes i understand that but it keeps on increasing.

[   28.600000] batman_adv: bat0: The MTU of interface adhoc0 is too

small (1546) to handle the transport of batman-adv packets. Packets going over this interface will be fragmented on layer2 which could impact the performance. Setting the MTU to 1560 would solve the problem.

Have you tried applying this patch before testing it once again?

Quoted 8 lines
Quoted 6 lines
Quoted 2 lines

http://git.open-mesh.org/batman-adv.git/commit/746d6436f88899a79c1cb3b27af0614510368bb7

Actually this patch is already part of the batman-adv package in openwrt. Therefore the question turns in: did you update the batman-adv package before performing your second test?

the second test was done today and yesterday's i updated bataman-adv.

Yes but we are creating confusion.

In the second test you *enabled* network coding, therefore it is normal that the overhead grew up. This happens because NC uses more bytes for its header.

If you disable NC the suggested value should go back to 1532.

Cheers,

Signature · 1 line
Antonio Quartulli

A message that is not in the archive (sent off-list or not yet received): [email protected]

#11 lore raw
Quoted 34 lines · cmsv
Quoted 17 lines · Antonio Quartulli
Quoted 16 lines · cmsv
Quoted 13 lines · Antonio Quartulli
Quoted 11 lines · Antonio Quartulli
Quoted 5 lines · cmsv

Yes i understand that but it keeps on increasing.

[   28.600000] batman_adv: bat0: The MTU of interface adhoc0 is too

small (1546) to handle the transport of batman-adv packets. Packets going over this interface will be fragmented on layer2 which could impact the performance. Setting the MTU to 1560 would solve the problem.

Have you tried applying this patch before testing it once again?

http://git.open-mesh.org/batman-adv.git/commit/746d6436f88899a79c1cb3b27af0614510368bb7

Quoted 7 lines
Quoted 5 lines
Quoted 3 lines

Actually this patch is already part of the batman-adv package in openwrt. Therefore the question turns in: did you update the batman-adv package before performing your second test?

the second test was done today and yesterday's i updated bataman-adv.

Yes but we are creating confusion.

Maybe. Lets see.

Quoted 4 lines

In the second test you *enabled* network coding, therefore it is normal that the overhead grew up. This happens because NC uses more bytes for its header.

Quoted 8 lines

In both tests NC was enabled. I have NC enabled by default before and after the update.
In fact is all tests NC is enabled by default and i undestand the increase to 1546 but to 1560 it surprised me.
Should i still see the increase to 1560 or should it stayed at 1546 which would be 1532 ?

[Please don't remove the batman-adv mailing list from the CC field.]

The first test you have performed was without the patch that fixes the value reported in that message.

Now that the patch is applied you have to see 1560 when NC is enabled and 1532 when it is disabled.

Can you confirm?

cheers,

Signature · 1 line
Antonio Quartulli
#12 lore raw

inline:

Quoted 44 lines · Antonio Quartulli
Quoted 34 lines · cmsv
Quoted 17 lines · Antonio Quartulli
Quoted 16 lines · cmsv
Quoted 13 lines · Antonio Quartulli
Quoted 11 lines · Antonio Quartulli
Quoted 5 lines · cmsv

Yes i understand that but it keeps on increasing.

[   28.600000] batman_adv: bat0: The MTU of interface adhoc0 is too

small (1546) to handle the transport of batman-adv packets. Packets going over this interface will be fragmented on layer2 which could impact the performance. Setting the MTU to 1560 would solve the problem.

Have you tried applying this patch before testing it once again?

http://git.open-mesh.org/batman-adv.git/commit/746d6436f88899a79c1cb3b27af0614510368bb7

Quoted 7 lines
Quoted 5 lines
Quoted 3 lines

Actually this patch is already part of the batman-adv package in openwrt. Therefore the question turns in: did you update the batman-adv package before performing your second test?

the second test was done today and yesterday's i updated bataman-adv.

Yes but we are creating confusion.

Maybe. Lets see.

Quoted 4 lines

In the second test you *enabled* network coding, therefore it is normal that the overhead grew up. This happens because NC uses more bytes for its header.

Quoted 8 lines

In both tests NC was enabled. I have NC enabled by default before and after the update.
In fact is all tests NC is enabled by default and i undestand the increase to 1546 but to 1560 it surprised me.
Should i still see the increase to 1560 or should it stayed at 1546 which would be 1532 ?

Quoted 2 lines

[Please don't remove the batman-adv mailing list from the CC field.]

unintentional mistake of too many buttons around :P

Quoted 8 lines

The first test you have performed was without the patch that fixes the value reported in that message.

Now that the patch is applied you have to see 1560 when NC is enabled and 1532 when it is disabled.

Doing some tests and with NC disabled:

uci show batman-adv | grep network_coding
batman-adv.bat0.network_coding=0

after reboot:

# dmesg | grep MTU
[   28.030000] batman_adv: bat0: The MTU of interface adhoc0 is too
small (1546) to handle the transport of batman-adv packets. Packets
going over this interface will be fragmented on layer2 which could
impact the performance. Setting the MTU to 1560 would solve the problem.

uci show network | grep mtu
network.mesh0.mtu=1546

changing the mtu to 1560 when NC is disabled:

# uci show batman-adv | grep network_coding
batman-adv.bat0.network_coding=0
# dmesg | grep MTU
no output/result
# ifconfig | grep MTU
          UP BROADCAST RUNNING MULTICAST  MTU:1560  Metric:1
          UP BROADCAST RUNNING MULTICAST  MTU:1440  Metric:1
          UP BROADCAST RUNNING MULTICAST  MTU:1440  Metric:1
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

Frist result if the adhoc interface with 1560

correct me if i am mistaken but according to you it should be 1532 ?

Changing it to 1532 still keeping network coding disabled.

uci set network.mesh0.mtu=1532
uci commit network
reboot

uci show network| grep mtu
network.mesh0.mtu=1532

uci show batman-adv | grep network_coding
batman-adv.bat0.network_coding=0

# dmesg | grep MTU
[   28.020000] batman_adv: bat0: The MTU of interface adhoc0 is too
small (1532) to handle the transport of batman-adv packets. Packets
going over this interface will be fragmented on layer2 which could
impact the performance. Setting the MTU to 1560 would solve the problem.
# dmesg | grep MTU
[   28.020000] batman_adv: bat0: The MTU of interface adhoc0 is too
small (1532) to handle the transport of batman-adv packets. Packets
going over this interface will be fragmented on layer2 which could
impact the performance. Setting the MTU to 1560 would solve the problem.
# ifconfig | grep MTU
          UP BROADCAST RUNNING MULTICAST  MTU:1532  Metric:1
          UP BROADCAST RUNNING MULTICAST  MTU:1440  Metric:1
          UP BROADCAST RUNNING MULTICAST  MTU:1440  Metric:1
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

Changing now the MTU to 1560

uci set network.mesh0.mtu=1560
uci commit network
reboot

Keeping batman-adv.bat0.network_coding=0

# uci show network| grep mtu
network.mesh0.mtu=1560
# ifconfig | grep MTU
          UP BROADCAST RUNNING MULTICAST  MTU:1560  Metric:1
          UP BROADCAST RUNNING MULTICAST  MTU:1440  Metric:1
          UP BROADCAST RUNNING MULTICAST  MTU:1440  Metric:1
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
# dmesg | grep MTU
no complaints.

if i enable network coding and the mtu to 1560 no complaints either.

Quoted 1 line

Can you confirm?

confirmed ?

Quoted 3 lines

cheers,

#13 lore raw
Quoted 103 lines · cmsv

inline:

Quoted 44 lines · Antonio Quartulli
Quoted 34 lines · cmsv
Quoted 17 lines · Antonio Quartulli
Quoted 16 lines · cmsv
Quoted 13 lines · Antonio Quartulli
Quoted 11 lines · Antonio Quartulli
Quoted 5 lines · cmsv

Yes i understand that but it keeps on increasing.

[   28.600000] batman_adv: bat0: The MTU of interface adhoc0 is too

small (1546) to handle the transport of batman-adv packets. Packets going over this interface will be fragmented on layer2 which could impact the performance. Setting the MTU to 1560 would solve the problem.

Have you tried applying this patch before testing it once again?

http://git.open-mesh.org/batman-adv.git/commit/746d6436f88899a79c1cb3b27af0614510368bb7

Quoted 7 lines
Quoted 5 lines
Quoted 3 lines

Actually this patch is already part of the batman-adv package in openwrt. Therefore the question turns in: did you update the batman-adv package before performing your second test?

the second test was done today and yesterday's i updated bataman-adv.

Yes but we are creating confusion.

Maybe. Lets see.

Quoted 4 lines

In the second test you *enabled* network coding, therefore it is normal that the overhead grew up. This happens because NC uses more bytes for its header.

Quoted 8 lines

In both tests NC was enabled. I have NC enabled by default before and after the update.
In fact is all tests NC is enabled by default and i undestand the increase to 1546 but to 1560 it surprised me.
Should i still see the increase to 1560 or should it stayed at 1546 which would be 1532 ?

Quoted 2 lines

[Please don't remove the batman-adv mailing list from the CC field.]

unintentional mistake of too many buttons around :P

Quoted 8 lines

The first test you have performed was without the patch that fixes the value reported in that message.

Now that the patch is applied you have to see 1560 when NC is enabled and 1532 when it is disabled.

Doing some tests and with NC disabled:

uci show batman-adv | grep network_coding
batman-adv.bat0.network_coding=0

after reboot:

# dmesg | grep MTU
[   28.030000] batman_adv: bat0: The MTU of interface adhoc0 is too
small (1546) to handle the transport of batman-adv packets. Packets
going over this interface will be fragmented on layer2 which could
impact the performance. Setting the MTU to 1560 would solve the problem.

uci show network | grep mtu
network.mesh0.mtu=1546

changing the mtu to 1560 when NC is disabled:

# uci show batman-adv | grep network_coding
batman-adv.bat0.network_coding=0
# dmesg | grep MTU
no output/result
# ifconfig | grep MTU
          UP BROADCAST RUNNING MULTICAST  MTU:1560  Metric:1
          UP BROADCAST RUNNING MULTICAST  MTU:1440  Metric:1
          UP BROADCAST RUNNING MULTICAST  MTU:1440  Metric:1
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

Frist result if the adhoc interface with 1560

correct me if i am mistaken but according to you it should be 1532 ?

Changing it to 1532 still keeping network coding disabled.

uci set network.mesh0.mtu=1532
uci commit network
reboot

Quoted 5 lines

uci show network| grep mtu
network.mesh0.mtu=1532

uci show batman-adv | grep network_coding
batman-adv.bat0.network_coding=0

No, the MTU value changes only when NC is disabled at compile time.

Signature · 1 line
Antonio Quartulli
#14 lore raw
In reply to cmsv

Hi cmsv,

Quoted 14 lines · cmsv

uci show batman-adv | grep network_coding
batman-adv.bat0.network_coding=0

after reboot:

# dmesg | grep MTU
[   28.030000] batman_adv: bat0: The MTU of interface adhoc0 is too
small (1546) to handle the transport of batman-adv packets. Packets
going over this interface will be fragmented on layer2 which could
impact the performance. Setting the MTU to 1560 would solve the problem.

uci show network | grep mtu
network.mesh0.mtu=1546

Quoted 7 lines

changing the mtu to 1560 when NC is disabled:

# uci show batman-adv | grep network_coding
batman-adv.bat0.network_coding=0
# dmesg | grep MTU
no output/result

It might not have been clear, but when we tell to disable NC, we are referring to the compile time options. batman-adv is not considering if NC is enabled/disabled at runtime when checking for MTU, but only checking if NC is compiled in or not.

It might make sense to check for runtime options when complaining about MTU in batman-adv, but I don't think so, as it complicates the checks whenever MTU is changed or NC is toggled.

// Martin

Signature · 8 lines
Kind Regards
Martin Hundebøll
Frederiks Allé 99, 1.th
8000 Aarhus C
Denmark

+45 61 65 54 61
[email protected]
#15 lore raw
In reply to Marek Lindner

In regards to incompatibility with pre-2014.0.0 versions; will 2013.4.0 branch have any continued support with patches or even updated version or any support pre-2014.0.0 is not expected or planed ?

Quoted 18 lines · Marek Lindner

Important changes
-----------------

*Compatibility break*: In 2011, batman-adv broke backward compatibility with the introduction of the translation table mechanism. Since then, interests have been divided between those who wish a stable network with as little changes as possible and those who wish to experiment with new features to bring meshing to the next level. To accommodate both groups the batman-adv developers dedicated a lot of effort on building code infrastructure allowing to mix stable nodes with new features without breaking compatibility. This new system is incompatible to the pre-2014.0.0 versions, but it has been designed to stay compatible with future versions for the next decade or so.

At the same time, the legacy visualization support was removed from the kernel module. The alfred user space module provides an adequate replacement.

Thanks

#16 lore raw
Quoted 4 lines · cmsv

In regards to incompatibility with pre-2014.0.0 versions; will 2013.4.0 branch have any continued support with patches or even updated version or any support pre-2014.0.0 is not expected or planed ?

The core group (read: the most active developers) are not going to maintain any pre-2014.0.0 branch. The code base in 2014.0.0 is rather different wrt older versions therefore any "backport" will be really expensive in terms of time and effort.

Only crucial bugfixes are going to be ported to older versions (by means of our maint branch - for a limited time - and the stable kernel releases).

However nobody prevents anyone from the community to take over this task.

Cheers,

Signature · 1 line
Antonio Quartulli
#18 lore raw
Quoted 11 lines · On Monday 10 February 2014 22:49:09 Linus Lüssing wrote:
Quoted 3 lines · cmsv

In regards to incompatibility with pre-2014.0.0 versions; will 2013.4.0 branch have any continued support with patches or even updated version or any support pre-2014.0.0 is not expected or planed ?

We are planning to mantain a compat-14 branch for a couple of months here:

https://github.com/freifunk-gluon/batman-adv-legacy

Contributions welcome :).

As already mentioned on IRC: We can easily host your batman-adv-legacy code on open-mesh.org next to the other repositories. That'll make it easier for other people to find it and may appear to be more 'official'.

Cheers,
Marek