From: Tore Anderson <tore@fud.no>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: [RFC] ipv6: dst_allfrag() not taken into account by TCP
Date: Wed, 18 Jan 2012 16:14:40 +0100 [thread overview]
Message-ID: <184325098dff696295968e09accafa9d@localhost> (raw)
In-Reply-To: <1326898746.2316.19.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC>
* Eric Dumazet
> Le mercredi 18 janvier 2012 à 15:43 +0100, Tore Anderson a écrit :
>
>> Another way of solving it and avoiding the Fragmentation headers
>> altogether would be to allow the "route MTU" to drop below 1280 as a
>> result of Path MTU Discovery. I opened an enchancement bug report
>> requesting this:
>>
>> https://bugzilla.kernel.org/show_bug.cgi?id=42599
>
> Please dont open bugzilla entries for this kind of stuff, since there is
> no bug in this case.
Okay...but then what is the «enhanchement» severity's intended use?
> netdev is more appropriate to discuss future improvements.
No problem. Bottom line, I'd like a "min_pmtu" IPv6 sysctl or something
similar that would allow me to configure it so that the kernel would
accept an arbitrary low PMTU being received in an ICMPv6 PTB. That
would prevent having to deal with the Fragmentation headers completely.
Best regards,
--
Tore Anderson
next prev parent reply other threads:[~2012-01-18 15:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 16:28 [RFC] ipv6: dst_allfrag() not taken into account by TCP Eric Dumazet
2012-01-17 17:34 ` David Miller
2012-01-17 18:15 ` Eric Dumazet
2012-01-17 18:25 ` David Miller
2012-01-17 20:03 ` Tore Anderson
2012-01-17 20:25 ` Eric Dumazet
2012-01-18 12:42 ` Tore Anderson
2012-01-18 14:06 ` Eric Dumazet
2012-01-18 14:43 ` Tore Anderson
2012-01-18 14:59 ` Eric Dumazet
2012-01-18 15:14 ` Tore Anderson [this message]
2012-01-18 15:40 ` Eric Dumazet
2012-01-18 17:01 ` David Miller
2012-01-17 23:43 ` Bugzilla 42595 Eric Dumazet
2012-01-18 10:58 ` Eric Dumazet
2012-01-18 13:44 ` Eric Dumazet
2012-01-18 14:20 ` Tore Anderson
2012-01-18 14:42 ` Eric Dumazet
2012-01-18 15:42 ` Eric Dumazet
2012-01-18 19:26 ` Tore Anderson
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=184325098dff696295968e09accafa9d@localhost \
--to=tore@fud.no \
--cc=eric.dumazet@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).