From: cmsv <cmsv@wirelesspt.net>
To: Antonio Quartulli <antonio@meshcoding.com>
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: Tue, 21 Jan 2014 19:52:58 -0500 [thread overview]
Message-ID: <52DF166A.7080309@wirelesspt.net> (raw)
In-Reply-To: <52DF1156.6000606@meshcoding.com>
inline:
On 01/21/2014 07:31 PM, Antonio Quartulli wrote:
> On 22/01/14 01:29, cmsv wrote:
>>
>>
>> On 01/21/2014 07:20 PM, Antonio Quartulli wrote:
>>> 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.
>> Maybe. Lets see.
>>>
>>> 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.
>>
>>
>> In both tests NC was enabled. I have NC enabled by default before and
>> after the update.
>> In fact is all tests NC is enabled by default and i undestand the
>> increase to 1546 but to 1560 it surprised me.
>> Should i still see the increase to 1560 or should it stayed at 1546
>> which would be 1532 ?
>>
>>
>
> [Please don't remove the batman-adv mailing list from the CC field.]
>
unintentional mistake of too many buttons around :P
>
> The first test you have performed was without the patch that fixes the
> value reported in that message.
>
>
>
> Now that the patch is applied you have to see 1560 when NC is enabled
> and 1532 when it is disabled.
Doing some tests and with NC disabled:
uci show batman-adv | grep network_coding
batman-adv.bat0.network_coding=0
after reboot:
# dmesg | grep MTU
[ 28.030000] 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.
uci show network | grep mtu
network.mesh0.mtu=1546
changing the mtu to 1560 when NC is disabled:
# uci show batman-adv | grep network_coding
batman-adv.bat0.network_coding=0
# dmesg | grep MTU
no output/result
# ifconfig | grep MTU
UP BROADCAST RUNNING MULTICAST MTU:1560 Metric:1
UP BROADCAST RUNNING MULTICAST MTU:1440 Metric:1
UP BROADCAST RUNNING MULTICAST MTU:1440 Metric:1
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
UP LOOPBACK RUNNING MTU:16436 Metric:1
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Frist result if the adhoc interface with 1560
correct me if i am mistaken but according to you it should be 1532 ?
Changing it to 1532 still keeping network coding disabled.
uci set network.mesh0.mtu=1532
uci commit network
reboot
uci show network| grep mtu
network.mesh0.mtu=1532
uci show batman-adv | grep network_coding
batman-adv.bat0.network_coding=0
# dmesg | grep MTU
[ 28.020000] batman_adv: bat0: The MTU of interface adhoc0 is too
small (1532) 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.
# dmesg | grep MTU
[ 28.020000] batman_adv: bat0: The MTU of interface adhoc0 is too
small (1532) 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.
# ifconfig | grep MTU
UP BROADCAST RUNNING MULTICAST MTU:1532 Metric:1
UP BROADCAST RUNNING MULTICAST MTU:1440 Metric:1
UP BROADCAST RUNNING MULTICAST MTU:1440 Metric:1
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
UP LOOPBACK RUNNING MTU:16436 Metric:1
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Changing now the MTU to 1560
uci set network.mesh0.mtu=1560
uci commit network
reboot
Keeping batman-adv.bat0.network_coding=0
# uci show network| grep mtu
network.mesh0.mtu=1560
# ifconfig | grep MTU
UP BROADCAST RUNNING MULTICAST MTU:1560 Metric:1
UP BROADCAST RUNNING MULTICAST MTU:1440 Metric:1
UP BROADCAST RUNNING MULTICAST MTU:1440 Metric:1
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
UP LOOPBACK RUNNING MTU:16436 Metric:1
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
# dmesg | grep MTU
no complaints.
if i enable network coding and the mtu to 1560 no complaints either.
> Can you confirm?
confirmed ?
>
>
> cheers,
next prev parent reply other threads:[~2014-01-22 0:52 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
[not found] ` <52DF10D1.4080207@wirelesspt.net>
2014-01-22 0:31 ` Antonio Quartulli
2014-01-22 0:52 ` cmsv [this message]
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=52DF166A.7080309@wirelesspt.net \
--to=cmsv@wirelesspt.net \
--cc=antonio@meshcoding.com \
--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