Project

General

Profile

Actions

Bug #397

open

BATMAN_V throughput on bridge, vxlan and veth

Added by Linus Lüssing over 5 years ago. Updated over 5 years ago.

Status:
New
Priority:
Normal
Target version:
-
Start date:
07/29/2019
Due date:
% Done:

0%

Estimated time:

Description

For these interfaces, bridge, vxlan and veth, batman-adv currently uses the 1Mbit/s default throughput. Also see:

https://github.com/freifunk-gluon/gluon/issues/1728

For vxlan Matthias is currently working on a patch to inherit the properties from its parent device (similar to what vlan does).

For veth ethtool reports 10Gbit/s, which is way more reasonable value for an in-kernel connection than our 1MBit/s default value:

$ ethtool veth0
Settings for veth0:
        Supported ports: [ ]
        Supported link modes:   Not reported
        Supported pause frame use: No
        Supports auto-negotiation: No
        Supported FEC modes: Not reported
        Advertised link modes:  Not reported
        Advertised pause frame use: No
        Advertised auto-negotiation: No
        Advertised FEC modes: Not reported
        Speed: 10000Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: off
        MDI-X: Unknown
        Link detected: yes

However batman-adv uses the default 1MBit/s throughput value due to auto-negotiation being disabled. We could add an exception in batman-adv for veth to disregard the auto-negotiation property, however that would not be sufficient for applications with for instance v(x)lans stacked on top of veth.

For bridge interfaces it is even more tricky.

Actions

Also available in: Atom PDF