419a866f03
If the MTU of one of an attached interface becomes too small to transmit the local translation table then it must be resized to fit inside all fragments (when enabled) or a single packet. But if the MTU becomes too low to transmit even the header + the VLAN specific part then the resizing of the local TT will never succeed. This can for example happen when the usable space is 110 bytes and 11 VLANs are on top of batman-adv. In this case, at least 116 byte would be needed. There will just be an endless spam of batman_adv: batadv0: Forced to purge local tt entries to fit new maximum fragment MTU (110) in the log but the function will never finish. Problem here is that the timeout will be halved all the time and will then stagnate at 0 and therefore never be able to reduce the table even more. There are other scenarios possible with a similar result. The number of BATADV_TT_CLIENT_NOPURGE entries in the local TT can for example be too high to fit inside a packet. Such a scenario can therefore happen also with only a single VLAN + 7 non-purgable addresses - requiring at least 120 bytes. While this should be handled proactively when: * interface with too low MTU is added * VLAN is added * non-purgeable local mac is added * MTU of an attached interface is reduced * fragmentation setting gets disabled (which most likely requires dropping attached interfaces) not all of these scenarios can be prevented because batman-adv is only consuming events without the the possibility to prevent these actions (non-purgable MAC address added, MTU of an attached interface is reduced). It is therefore necessary to also make sure that the code is able to handle also the situations when there were already incompatible system configuration are present. Signed-off-by: Sven Eckelmann <sven@narfation.org> |
||
|---|---|---|
| .github | ||
| ahcpd | ||
| alfred | ||
| babel-pinger | ||
| babeld | ||
| batctl | ||
| batman-adv | ||
| batmand | ||
| bird1 | ||
| bird1-openwrt | ||
| bird2 | ||
| bmx6 | ||
| bmx7 | ||
| cjdns | ||
| hnetd | ||
| luci-app-bmx6 | ||
| luci-app-cjdns | ||
| luci-app-olsrd2 | ||
| mcproxy | ||
| mesh11sd | ||
| minimalist-pcproxy | ||
| naywatch | ||
| ndppd | ||
| nodogsplash | ||
| ohybridproxy | ||
| olsrd | ||
| oonf-dlep-proxy | ||
| oonf-dlep-radio | ||
| oonf-init-scripts | ||
| oonf-olsrd2 | ||
| opennds | ||
| pimbd | ||
| prince | ||
| quagga | ||
| vis | ||
| MAINTAINERS | ||
| README.md | ||
README.md
OpenWrt Routing Feed
Description
This OpenWrt package feed contains community maintained routing packages.
Usage
This repository is intended to be layered on-top of an OpenWrt buildroot. If you do not have an OpenWrt buildroot installed, see the documentation at: OpenWrt Buildroot – Installation on the OpenWrt support site.
This feed is enabled by default. To install all its package definitions, run:
./scripts/feeds update routing
./scripts/feeds install -a -p routing