All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Langer <an.langer@gmx.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: [B.A.T.M.A.N.] batman adv unicast fragmentation
Date: Wed, 30 Jun 2010 20:58:46 +0200	[thread overview]
Message-ID: <20100630205846.230b2112@rechenknecht> (raw)

Hi,

things that changed since the last patch:
- with fragmentation enabled the mtu of batX is always ETH_DATA_LEN
- fragment if mtu of the outgoing interface is smaller the needed size
- add a new packet type for fragmentation
- new recv function for fragmented packets
- new route unicast packet function to share routing code
- increase compat number to 12


regards,
andreas

             reply	other threads:[~2010-06-30 18:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-30 18:58 Andreas Langer [this message]
2010-06-30 19:00 ` [B.A.T.M.A.N.] [PATCH 1/2] batctl: layer2 unicast packet fragmentation Andreas Langer
2010-07-04 22:40   ` Sven Eckelmann
2010-06-30 19:00 ` [B.A.T.M.A.N.] [PATCH 2/2] batman-adv: " Andreas Langer
2010-07-05  0:37   ` Sven Eckelmann
2010-07-05 12:53   ` Sven Eckelmann
2010-07-04 21:57 ` [B.A.T.M.A.N.] batman adv unicast fragmentation Simon Wunderlich
2010-07-05  9:24   ` 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=20100630205846.230b2112@rechenknecht \
    --to=an.langer@gmx.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 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.