public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Marek Lindner <lindner_marek@yahoo.de>
To: 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.] Layer 2 fragmentation
Date: Thu, 27 May 2010 23:30:15 +0800	[thread overview]
Message-ID: <201005272330.15388.lindner_marek@yahoo.de> (raw)
In-Reply-To: <20100527150700.GA29869@lunn.ch>

On Thursday 27 May 2010 23:07:00 Andrew Lunn wrote:
> I don't quite understand the problem. If you have implemented
> fragmentation, you will naturally increase the MTU on bat0 so that it
> is the standard for Ethernet. So this statement will not trigger.

AFAIK batman-adv determines the minimal MTU automatically, so that you can't 
simply increase the mtu on bat0. But you are right - if the fragmentation is 
enabled batman-adv could allow higher mtu values.

Cheers,
Marek

  reply	other threads:[~2010-05-27 15:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-27 14:23 [B.A.T.M.A.N.] Layer 2 fragmentation Andreas Langer
2010-05-27 15:07 ` Andrew Lunn
2010-05-27 15:30   ` Marek Lindner [this message]
2010-05-27 15:42     ` Andrew Lunn
2010-05-27 16:12       ` 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=201005272330.15388.lindner_marek@yahoo.de \
    --to=lindner_marek@yahoo.de \
    --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