public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: "Leo Krüger" <leo@hamburg.freifunk.net>
Subject: [B.A.T.M.A.N.] Add VLAN tag size to MTU recommendation?
Date: Thu, 20 Oct 2016 23:56:14 +0200	[thread overview]
Message-ID: <20161020215614.GG32033@otheros> (raw)

Hi,

First of all, just wanted to forward this awesome diagram
regarding MTUs in Gluon-Setups which Freifunk Hamburg created
:D :

https://twitter.com/ohrensesselnet/status/789176399655350272

Which might be helpful for anyone new to understand how the
encapsulation in batman-adv works and how the MTU recommendations
of the underlying hard interfaces are calculated.

(I need to ask Leo for the sources, maybe a version without the
fastd overhead might be interesting for an MTU-explained page in
the open-mesh.org wiki :)?)


While checking the calculations Freifunk Hamburg did, I was
wondering whether the batadv_hardif_min_mtu() function should add
an extra 4 bytes for VLAN tagged, encapsulated payload to the MTU
calculations and the kmesg recommendations, especially since
Antonio's great work made TT fully VLAN-aware?

Open-Mesh.com/Cloudtrax routers are using the VLAN awareness, right?
Is the wifi interface MTU there just set to +4 bytes over the kmesg
recommedation?

Regards, Linus

             reply	other threads:[~2016-10-20 21:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-20 21:56 Linus Lüssing [this message]
     [not found] ` <123097163.ZmppEksrjh@voltaire>
2016-10-21  6:03   ` [B.A.T.M.A.N.] Add VLAN tag size to MTU recommendation? Linus Lüssing

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=20161020215614.GG32033@otheros \
    --to=linus.luessing@c0d3.blue \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=leo@hamburg.freifunk.net \
    /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