fff-babeld: add MTU option to babelpeers #125

jkimmel · 2021-02-17T06:47:08+01:00

jkimmel commented

2021-02-17 06:47:08 +01:00

Currently the MTU of a babelpeers is not configurable, nor set to a
default value. If present, the mtu option is now copied to the
interface section, otherwise it is set to a default value of 1500.

Warning for VLAN Interfaces:

For MTUs larger than 1500 to take effect, the parent interface also
needs adjusting. E.g. setting eth0.100 to an MTU larger than the MTU
of eth0 will not work.

At this point, manually add the following section to
/etc/config/network:

config interface
	option ifname 'eth0'
	option mtu '1570'

Beware that this will cause any child interface of eth0 to have the
same large MTU.

Signed-off-by: Johannes Kimmel fff@bareminimum.eu

Currently the MTU of a babelpeers is not configurable, nor set to a default value. If present, the `mtu` option is now copied to the interface section, otherwise it is set to a default value of 1500. Warning for VLAN Interfaces: For MTUs larger than 1500 to take effect, the parent interface also needs adjusting. E.g. setting `eth0.100` to an MTU larger than the MTU of `eth0` will not work. At this point, manually add the following section to `/etc/config/network`: ``` config interface option ifname 'eth0' option mtu '1570' ``` Beware that this will cause any child interface of `eth0` to have the same large MTU. Signed-off-by: Johannes Kimmel <fff@bareminimum.eu>

jkimmel added the

layer3

packages/fff

RFC

labels 2021-02-17 06:47:08 +01:00

jkimmel added 2 commits 2021-02-17 06:47:08 +01:00

057541129d fff-babeld: clean up type/rxcost option handling

Signed-off-by: Johannes Kimmel <fff@bareminimum.eu>

f333c3c822 fff-babeld: add MTU option to babelpeers

Currently the MTU of a babelpeers is not configurable, nor set to a
default value. If present, the `mtu` option is now copied to the
interface section, otherwise it is set to a default value of 1500.

Warning for VLAN Interfaces:

For MTUs larger than 1500 to take effect, the parent interface also
needs adjusting. E.g. setting `eth0.100` to an MTU larger than the MTU
of `eth0` will not work.

At this point, manually add the following section to
`/etc/config/network`:

```
config interface
	option ifname 'eth0'
	option mtu '1570'
```

Beware that this will cause any child interface of `eth0` to have the
same large MTU.

Signed-off-by: Johannes Kimmel <fff@bareminimum.eu>

jkimmel referenced this pull request

2021-02-17 06:49:26 +01:00

fff-layer3-vxmesh: join multple client nets with vxlan #82

jkimmel referenced this pull request

2021-02-17 06:49:41 +01:00

fff-layer3-vxmesh: join multple client nets with vxlan #82

jkimmel added a new dependency 2021-02-17 07:17:05 +01:00

#82 fff-layer3-vxmesh: join multple client nets with vxlan

fbl requested changes 2021-03-02 00:21:59 +01:00

fbl left a comment

Das was im ersten Commit gemacht wird, sollte man für alle derartige Vorkommen (speziell in /etc/layer3.d) machen. Gefällt mir gut.

Statt die MTU explizit auf 1500 zu setzen würde ich hier gerne dabei bleiben die MTU im Default-Fall nicht explizit zu setzen, wodurch sie dann beim Linux Default bleibt. Man kann babelpeer nämlich nicht nur für Ethernet-Interfaces her nehmen, sondern für beliebige Interfaces, die per Default auch etwas anderes als 1500 MTU haben könnten.

Das was im ersten Commit gemacht wird, sollte man für alle derartige Vorkommen (speziell in /etc/layer3.d) machen. Gefällt mir gut. Statt die MTU explizit auf 1500 zu setzen würde ich hier gerne dabei bleiben die MTU im Default-Fall nicht explizit zu setzen, wodurch sie dann beim Linux Default bleibt. Man kann babelpeer nämlich nicht nur für Ethernet-Interfaces her nehmen, sondern für beliebige Interfaces, die per Default auch etwas anderes als 1500 MTU haben könnten.

jkimmel removed a dependency 2024-03-12 12:31:40 +01:00

#82 fff-layer3-vxmesh: join multple client nets with vxlan

This pull request has changes conflicting with the target branch.