From: "David S. Miller" <davem@redhat.com>
To: David Stevens <dlstevens@us.ibm.com>
Cc: pekkas@netcore.fi, r.venning@telstra.com, nate@thebog.net,
netdev@oss.sgi.com
Subject: Re: 6to4/SIT and IP DF
Date: Wed, 15 Oct 2003 22:27:12 -0700 [thread overview]
Message-ID: <20031015222712.18d1434f.davem@redhat.com> (raw)
In-Reply-To: <OF32DA07F2.CE83636D-ON88256DC1.001CC44C@us.ibm.com>
On Wed, 15 Oct 2003 22:21:37 -0700
David Stevens <dlstevens@us.ibm.com> wrote:
> That doesn't sound terrible, but won't it have to drop a minimum of
> 2 packets per tunnel on an MTU change (or initial probe with a large
> packet)?
Welcome to the real world where most routers don't quote enough
information. :) What we do is the only sane way to handle this
problem.
All of our ipv4 tunnels work this way due to that quoting size issue.
The "fragment but tell me about it" isn't such a great idea. You'll
run into all kinds of difficult decisions about behavior in the cases
where a too-big packet overruns multiple hops on the path. This is why
the original implementors didn't put this into the RFCs.
next prev parent reply other threads:[~2003-10-16 5:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-16 5:21 6to4/SIT and IP DF David Stevens
2003-10-16 5:27 ` David S. Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-15 7:15 David Stevens
2003-10-16 4:38 ` David S. Miller
2003-10-15 3:56 David Stevens
2003-10-15 6:28 ` Pekka Savola
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=20031015222712.18d1434f.davem@redhat.com \
--to=davem@redhat.com \
--cc=dlstevens@us.ibm.com \
--cc=nate@thebog.net \
--cc=netdev@oss.sgi.com \
--cc=pekkas@netcore.fi \
--cc=r.venning@telstra.com \
/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.