From: cmsv <cmsv@wirelesspt.net>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] MTU issue
Date: Thu, 24 Apr 2014 05:15:07 -0400 [thread overview]
Message-ID: <5358D61B.9090706@wirelesspt.net> (raw)
In-Reply-To: <5358CC9E.3040506@amideeptech.com>
[-- Attachment #1: Type: text/plain, Size: 695 bytes --]
https://lists.open-mesh.org/pipermail/b.a.t.m.a.n/2014-January/011276.html
On 04/24/2014 04:34 AM, Saurabh Chakrabarti wrote:
> Following the Troubleshooting guide, I have changed the MTU for bat0
> interface to 1524. I'm getting this message in my syslog:
>
> Jan 1 00:00:53 localhost kernel: [ 26.899762] batman_adv: bat0: The
> MTU of interface wlan0 is too small (1524) 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.
>
> I'm not seeing any apparent performance issues, but do I really need to
> make the MTU 1560?
>
> -saurabh
>
[-- Attachment #2: 0x15C4B382.asc --]
[-- Type: application/pgp-keys, Size: 36238 bytes --]
next prev parent reply other threads:[~2014-04-24 9:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 8:34 [B.A.T.M.A.N.] MTU issue Saurabh Chakrabarti
2014-04-24 9:15 ` cmsv [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-11-03 14:53 Wayne Abroue
2011-11-06 13:57 ` Marek Lindner
[not found] ` <CAKeC-QEJAJVk1=bdB0R6iqu_Q5NBdcgL3=qU9-KLg8k7zbCKMQ@mail.gmail.com>
2011-11-06 16:27 ` [B.A.T.M.A.N.] Fwd: " Wayne Abroue
2011-11-06 17:27 ` [B.A.T.M.A.N.] " Marek Lindner
2011-11-06 18:05 ` Wayne Abroue
2011-11-06 19:37 ` Sven Eckelmann
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=5358D61B.9090706@wirelesspt.net \
--to=cmsv@wirelesspt.net \
--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 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.