public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Gus Wirth <gwirth79@gmail.com>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: [B.A.T.M.A.N.] Maximum MTU (was Re:  B.A.T.M.A.N. V outlook)
Date: Fri, 08 Jan 2010 09:11:39 -0800	[thread overview]
Message-ID: <4B47674B.6010508@gmail.com> (raw)
In-Reply-To: <20100107214343.GA2554@Linus-Debian>

On 01/07/2010 01:43 PM, Linus Lüssing wrote:
[snip]
> In general, batman-adv adds a little header of 24 Bytes. But this
> kind of extra cost also applies to packets between batman nodes,
> not only when a packet comes from the connected network. So if you
> are bridging any other networks/hosts into the mesh network (i.e.
> bridging eth0 + bat0) does not matter, you should just a) increase
> the MTU of the mesh-interfaces to 1524 which is usually not a
> problem for wifi interfaces or b) decrease the MTU on all hosts to
> 1476 (usually not so do-able).

Would you happen to know what the maximum MTU you could use on the
wireless interface?

For example, if I have an ethernet network that can support jumbo frames
like on a gigabit interface, how large of an MTU could I use on the
wireless interface. In my case I'm using Atheros wireless devices, so I
don't know if that matters.

Gus

  reply	other threads:[~2010-01-08 17:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-18  9:14 [B.A.T.M.A.N.] B.A.T.M.A.N. V outlook Marek Lindner
2009-12-18 16:53 ` Gus Wirth
2009-12-19  2:58   ` Marek Lindner
2010-01-07  7:44 ` Alex Morlang
2010-01-07 13:23   ` Marek Lindner
2010-01-07 16:10     ` Alex Morlang
2010-01-07 21:14       ` Simon Wunderlich
2010-01-07 22:39         ` Alex Morlang
2010-01-07 21:43       ` Linus Lüssing
2010-01-08 17:11         ` Gus Wirth [this message]
2010-01-08 18:18           ` [B.A.T.M.A.N.] Maximum MTU (was Re: B.A.T.M.A.N. V outlook) Andrew Lunn

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=4B47674B.6010508@gmail.com \
    --to=gwirth79@gmail.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