public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: "Linus Lüssing" <linus.luessing@web.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@lists.open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] BATMAN-Adv and MTU handling
Date: Fri, 11 Dec 2009 14:45:35 +0100	[thread overview]
Message-ID: <20091211134535.GA2879@Linus-Debian> (raw)
In-Reply-To: <20091123142151.GA21537@Sellars>

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

On Mon, Nov 23, 2009 at 03:21:51PM +0100, Linus Lüssing wrote:
> > > Hmm, yes, true, IPv6 does not support fragmentation at all...
> > 
> > It does, but it's done end-to-end, not at intermediate routers.  See
> > Section 5 of RFC 2460.
> Ah, ok, yes, you're right, forgot about the fragmentation header
> in IPv6 :).
By the way, does anyone know if it is possible to encapsulate
packets with the ethernet frame / packets from a brdige port in ipv6?
RFC 4303 for encapsulating security payload looks like only tunnelling of
ip-traffic is possible with the standardised features of IPv6.

Cheers, Linus

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2009-12-11 13:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-09 19:02 [B.A.T.M.A.N.] BATMAN-Adv and MTU handling Linus Lüssing
2009-11-10 10:34 ` Marek Lindner
2009-11-10 22:16   ` Simon Wunderlich
2009-11-12  0:51   ` Linus Lüssing
2009-11-12  3:28     ` Marek Lindner
2009-11-15 17:08     ` Juliusz Chroboczek
2009-11-23 14:21       ` Linus Lüssing
2009-12-11 13:45         ` Linus Lüssing [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=20091211134535.GA2879@Linus-Debian \
    --to=linus.luessing@web.de \
    --cc=b.a.t.m.a.n@lists.open-mesh.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