From: "Svenning Soerensen" <svenning@post5.tele.dk>
To: <linux-kernel@vger.kernel.org>
Cc: <linux-ipsec@freeswan.org>
Subject: Problem with PMTU discovery on ICMP packets
Date: Sat, 5 May 2001 13:36:32 +0200 [thread overview]
Message-ID: <015201c0d557$a1e69c50$1400a8c0@sss.intermate.com> (raw)
Hi there,
I think there is a bug in the 2.4 icmp code regarding PMTU discovery.
It seems to be inconsistent between reboots: at one boot echo replies always
have the DF bit set, while after another boot they don't, indicating that
this is caused by an uninitialized parameter.
Even 'echo 1 > /proc/sys/net/ipv4/ip_no_pmtu_disc' doesn't change this
behaviour.
I can't think of any legitimate reasons for doing PMTU discovery on ICMP
packets, and since it actually in some situations breaks ping in combination
with FreeS/WAN (I can elaborate, if anyone is interested), I would suggest
to turn it off in a consistent manner.
The patch below (against 2.4.4) should accomplish this.
Svenning
--- linux/net/ipv4/icmp.c 2001/04/28 12:30:34 1.1.1.2
+++ linux/net/ipv4/icmp.c 2001/05/05 11:06:41
@@ -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
next reply other threads:[~2001-05-05 11:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-05 11:36 Svenning Soerensen [this message]
2001-05-05 11:44 ` Problem with PMTU discovery on ICMP packets 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
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='015201c0d557$a1e69c50$1400a8c0@sss.intermate.com' \
--to=svenning@post5.tele.dk \
--cc=linux-ipsec@freeswan.org \
--cc=linux-kernel@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 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.