From: Antonio Quartulli <antonio@meshcoding.com>
To: cmsv@wirelesspt.net
Cc: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] batman-adv 2014.0.0 released
Date: Wed, 22 Jan 2014 01:20:30 +0100 [thread overview]
Message-ID: <52DF0ECE.7000707@meshcoding.com> (raw)
In-Reply-To: <52DF0D4E.5070207@wirelesspt.net>
[-- Attachment #1: Type: text/plain, Size: 1289 bytes --]
On 22/01/14 01:14, cmsv wrote:
>
>
> On 01/21/2014 07:06 PM, Antonio Quartulli wrote:
>> On 22/01/14 01:00, Antonio Quartulli wrote:
>>> On 21/01/14 21:01, cmsv wrote:
>>>> Yes i understand that but it keeps on increasing.
>>>> [ 28.600000] batman_adv: bat0: The MTU of interface adhoc0 is too
>>>> small (1546) 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 1560 would solve the problem.
>>>
>>> Have you tried applying this patch before testing it once again?
>>>
>>> http://git.open-mesh.org/batman-adv.git/commit/746d6436f88899a79c1cb3b27af0614510368bb7
>>>
>>
>> Actually this patch is already part of the batman-adv package in openwrt.
>> Therefore the question turns in: did you update the batman-adv package
>> before performing your second test?
>
> the second test was done today and yesterday's i updated bataman-adv.
Yes but we are creating confusion.
In the second test you *enabled* network coding, therefore it is normal
that the overhead grew up. This happens because NC uses more bytes for
its header.
If you disable NC the suggested value should go back to 1532.
Cheers,
--
Antonio Quartulli
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-01-22 0:20 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
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 [this message]
[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=52DF0ECE.7000707@meshcoding.com \
--to=antonio@meshcoding.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=cmsv@wirelesspt.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