From: David Madore <david+ml@madore.org>
To: Linux NetDev Mailing-List <netdev@vger.kernel.org>
Subject: MTU blackhole discovery for IPv6 ?
Date: Thu, 7 May 2009 23:19:26 +0200 [thread overview]
Message-ID: <20090507211926.GA28662@regulus.madore.org> (raw)
Hi,
There's a sysctl called net.ipv4.tcp_mtu_probing: has there been any
work done on the analogous key for IPv6?
I'm encountering a number of asinine network providers who either
discard ICMPs (whether v4 or v6...) or simply don't emit them. The
IPv6 picture is even bleaker than IPv4 because so much traffic goes
through tunnels like 6to4. An IPv6 MTU blackhole discovery
implementation would truly save my day.
I understand that RFC 4821 specifies the same algorithms for
packetization layer path MTU discovery in IPv4 and IPv6. Did Linux
implement this in IPv4 only because there is some difficulty in doing
the same thing for IPv6, or simply because nobody was asking for it?
Happy hacking,
--
David A. Madore
( http://www.madore.org/~david/ )
next reply other threads:[~2009-05-07 21:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 21:19 David Madore [this message]
2009-05-07 21:48 ` MTU blackhole discovery for IPv6 ? David Miller
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=20090507211926.GA28662@regulus.madore.org \
--to=david+ml@madore.org \
--cc=netdev@vger.kernel.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