From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: How to mesh over ethernet VLAN?
Date: Wed, 14 Apr 2021 13:35:53 +0200 [thread overview]
Message-ID: <20210414113553.GA4886@otheros> (raw)
In-Reply-To: <CAEX-Y1ZnouWOpjrT4n8q4BVaRWSP30GLMbT_78Kn3_KoFELp9g@mail.gmail.com>
On Fri, Apr 09, 2021 at 03:38:15PM +0200, Andi Depressivum wrote:
> Actual OpenWRT trunk on TP-Link C7 / C2600 devices. Can decrease to
> anything lower than 1500 but cannot raise above 1500.
Hm, yes, many/most ethernet devices don't support jumbo frames.
You could test with iperf3 and its --set-mss option if smaller,
unfragmented frames have a better performance.
A few more options to solve this are then:
* using the DHCP MTU option on the DHCP server (though many
DHCP clients do not properly support this)
* use iptables MSS clamping (only works for TCP and routed
traffic)
* on a gateway router, set a route to the internet with a lower
MTU, which then results in "ICMP packet too big" messages back
to the client with containing the desired MTU and the initial
host should retry with a smaller packet size
(only works for routed traffic)
Or if you have full control of all hosts in the network you can
also reduce the MTU on the hosts.
Also note batman-adv v2021.0 had some performance
improvements for frames fragmented by batman-adv:
https://www.open-mesh.org/news/100 ->
* https://git.open-mesh.org/batman-adv.git/commit/92064deda9b063ca2d5a53b307c6127a9453357c
* https://git.open-mesh.org/batman-adv.git/commit/0966d5424bb87e863037301488519ccdd69e4d26
* https://git.open-mesh.org/batman-adv.git/commit/3e3ff987876d3be70d928561acbefe5a48ab1654
Regards, Linus
next prev parent reply other threads:[~2021-04-14 11:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-04 17:52 How to mesh over ethernet VLAN? Andi Depressivum
2021-04-06 19:51 ` Linus Lüssing
2021-04-06 21:33 ` Andi Depressivum
2021-04-09 11:24 ` Linus Lüssing
2021-04-09 13:38 ` Andi Depressivum
2021-04-14 11:35 ` Linus Lüssing [this message]
2021-05-04 18:04 ` Andi Depressivum
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210414113553.GA4886@otheros \
--to=linus.luessing@c0d3.blue \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox