public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Antonio Quartulli <antonio@meshcoding.com>
To: cmsv@wirelesspt.net,
	"The list for a Better Approach To Mobile Ad-hoc Networking"
	<b.a.t.m.a.n@lists.open-mesh.org>,
	"Martin Hundebøll" <martin@hundeboll.net>
Subject: Re: [B.A.T.M.A.N.] batman-adv 2014.0.0 released
Date: Wed, 15 Jan 2014 12:15:48 +0100	[thread overview]
Message-ID: <52D66DE4.3050300@meshcoding.com> (raw)
In-Reply-To: <52D66D45.4060301@wirelesspt.net>

[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]

On 15/01/14 12:13, cmsv wrote:
> inline:
> 
> On 01/15/2014 02:00 AM, Martin Hundebøll wrote:
>> Hi,
>>
>> On 2014-01-14 23:04, cmsv wrote:
>>> batman_adv: bat0: The MTU of interface adhoc0 is too small (1528) to
>>> handle the transport of batman-adv packets. Packets going over this
>>> interface will be fragmented on layer2 which could impact the
>>> performance. Setting the MTU to 1546 would solve the problem.
>>
>> Did you enable network coding? That would explain the message, as NC
>> uses a larger header to make decoding possible at the receiver side.
> Yes it is enabled by default as it was with batavd 2013.4.0 with 1528 mtu
>>
>> As far as I can tell from a quick look in packet.h, the required MTU
>> should be 1532 now. (10 bytes unicast + 8 bytes extra for unicast_4addr
>> + 14 ethernet = 32 bytes). Or am I bad at counting bytes?
> 
> Regardless of being properly counted or not; dmesg outputs the message
> complaining about the need to make mtu 1546.

If you disable network coding the message will change.

The overhead is dynamic depending on NC being enabled or not and now the
message in dmesg tells you exactly what MTU you need.

Cheers,


-- 
Antonio Quartulli


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2014-01-15 11:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-07 12:53 [B.A.T.M.A.N.] batman-adv 2014.0.0 released Marek Lindner
2014-01-14 22:04 ` cmsv
2014-01-15  7:00   ` Martin Hundebøll
2014-01-15 11:13     ` cmsv
2014-01-15 11:15       ` Antonio Quartulli [this message]
2014-01-21 20:01         ` cmsv
2014-01-22  0:00           ` Antonio Quartulli
2014-01-22  0:06             ` Antonio Quartulli
     [not found]               ` <52DF0D4E.5070207@wirelesspt.net>
2014-01-22  0:20                 ` Antonio Quartulli
     [not found]                   ` <52DF10D1.4080207@wirelesspt.net>
2014-01-22  0:31                     ` Antonio Quartulli
2014-01-22  0:52                       ` cmsv
2014-01-22  6:46                         ` Antonio Quartulli
2014-01-22  6:50                         ` Martin Hundebøll
2014-02-10 19:45 ` cmsv
2014-02-10 19:57   ` Antonio Quartulli
2014-02-10 21:49   ` Linus Lüssing
2014-02-11  3:22     ` Marek Lindner

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=52D66DE4.3050300@meshcoding.com \
    --to=antonio@meshcoding.com \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=cmsv@wirelesspt.net \
    --cc=martin@hundeboll.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