public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Simon Wunderlich <sw@simonwunderlich.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: "Martin Hundebøll" <martin@hundeboll.net>
Subject: Re: [B.A.T.M.A.N.] Fwd: MTU problem
Date: Wed, 04 Nov 2015 12:31:06 +0100	[thread overview]
Message-ID: <2343005.S5kpmKodS9@prime> (raw)
In-Reply-To: <5639EA30.6010403@hundeboll.net>

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

He also wrote me in private ... that's kind of rude :(

On Wednesday 04 November 2015 12:21:20 Martin Hundebøll wrote:
> Hi Antonio,
> 
> Please direct your mails to the batman mailing list:
> b.a.t.m.a.n@lists.open-mesh.org
> 
> This way, others can help you too.
> 
> On 2015-11-04 12:15, Antonio Abejaro wrote:
> > I have just configured the value of 1532 for MTU in /etc/config/network
> > as suggested but when I reboot my node I obtain the following dmesg:
> > 
> > batman_adv: bat0: The MTU of interface adhoc0 is too small (1500) 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 1532 would solve the problem.
> 
> What version of b.a.t.m.a.n. are you using? We had an issue in earlier
> version, where the suggested value was too small...
> 
> // Martin

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

      reply	other threads:[~2015-11-04 11:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CANC9+Di3GnouTrYDsp0ihbAFAV9xahr9T88KdqTBuK_nV6xUGw@mail.gmail.com>
     [not found] ` <CANC9+Djjuo3pvuwAUfFmPCM8KAxDXro8SeubMrdy9QB4ewgTjg@mail.gmail.com>
2015-11-04 11:21   ` [B.A.T.M.A.N.] Fwd: MTU problem Martin Hundebøll
2015-11-04 11:31     ` Simon Wunderlich [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=2343005.S5kpmKodS9@prime \
    --to=sw@simonwunderlich.de \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --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