From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: Sven Eckelmann <sven@narfation.org>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCH] batman-adv: decrease maximum fragment size
Date: Tue, 31 Jan 2017 21:39:59 +0100 [thread overview]
Message-ID: <20170131203959.GA3899@otheros> (raw)
In-Reply-To: <1710363.lgBWTzDvpW@bentobox>
On Tue, Jan 31, 2017 at 12:07:24PM +0100, Sven Eckelmann wrote:
> On Sonntag, 29. Januar 2017 06:14:28 CET Linus Lüssing wrote:
> [...]
> > However, currently "Fragmentation v2" does not support re-fragmentation.
> > Which means that once a packet is split into two packets of 1400 + x
> > bytes for instance and the next hop provides an interface with an even
> > smaller MTU of 1280 bytes, then the larger fragment is lost.
> [...]
>
> Beside this change, did you try to make the fragments more equally sized?
> Here is just some really ugly and untested pseudo code:
Have thought about it initially but pushed it asided when I
noticed it would only help regarding the initial issue for the
unicast packets but not potentially large TTs.
But generally, I like the idea of making fragments more equally
sized :-).
prev parent reply other threads:[~2017-01-31 20:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-29 5:14 [B.A.T.M.A.N.] [PATCH] batman-adv: decrease maximum fragment size Linus Lüssing
2017-01-31 11:07 ` Sven Eckelmann
2017-01-31 20:39 ` Linus Lüssing [this message]
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=20170131203959.GA3899@otheros \
--to=linus.luessing@c0d3.blue \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=sven@narfation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.