From: "David S. Miller" <davem@redhat.com>
To: "Svenning Soerensen" <svenning@post5.tele.dk>
Cc: <linux-kernel@vger.kernel.org>, <linux-ipsec@freeswan.org>
Subject: RE: Problem with PMTU discovery on ICMP packets
Date: Wed, 9 May 2001 18:21:23 -0700 (PDT) [thread overview]
Message-ID: <15097.60691.888764.916294@pizda.ninka.net> (raw)
In-Reply-To: <016e01c0d68b$51da19a0$1400a8c0@sss.intermate.com>
In-Reply-To: <15092.31381.395563.889405@pizda.ninka.net> <016e01c0d68b$51da19a0$1400a8c0@sss.intermate.com>
Svenning Soerensen writes:
> I've done a bit more testing. The behaviour doesn't change across reboots.
> Instead, it seems to be the case that:
> If the packet fits within the MTU of the outgoing interface, DF is set.
> If the packet doesn't fit, and thus gets fragmented, DF is clear on all
> fragments.
> Does this make sense?
Yes. I've put the following patch into my tree.
Thanks for doing the detective work.
--- net/ipv4/icmp.c.~1~ Sun Apr 29 21:40:40 2001
+++ net/ipv4/icmp.c Wed May 9 18:20:58 2001
@@ -3,7 +3,7 @@
*
* Alan Cox, <alan@redhat.com>
*
- * Version: $Id: icmp.c,v 1.75 2001/04/30 04:40:40 davem Exp $
+ * Version: $Id: icmp.c,v 1.76 2001/05/10 01:20:58 davem Exp $
*
* This program is free software; you can redistribute it and/or
* modify it under the terms of the GNU General Public License
@@ -1006,6 +1006,7 @@
icmp_socket->sk->allocation=GFP_ATOMIC;
icmp_socket->sk->sndbuf = SK_WMEM_MAX*2;
icmp_socket->sk->protinfo.af_inet.ttl = MAXTTL;
+ icmp_socket->sk->protinfo.af_inet.pmtudisc = IP_PMTUDISC_DONT;
/* Unhash it so that IP input processing does not even
* see it, we do not wish this socket to see incoming
prev parent reply other threads:[~2001-05-10 1:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-05 11:36 Svenning Soerensen
2001-05-05 11:44 ` David S. Miller
2001-05-05 14:23 ` Svenning Soerensen
2001-05-05 22:11 ` David S. Miller
2001-05-07 0:19 ` Svenning Soerensen
2001-05-10 1:21 ` David S. Miller [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=15097.60691.888764.916294@pizda.ninka.net \
--to=davem@redhat.com \
--cc=linux-ipsec@freeswan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=svenning@post5.tele.dk \
/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
all inboxes | Powered by JetHome®