From: Russell Miller <rmiller@duskglow.com>
To: linux-kernel@vger.kernel.org
Subject: udp traceroute dropping packets
Date: Thu, 15 Apr 2004 21:55:13 -0500 [thread overview]
Message-ID: <200404152155.18724.rmiller@duskglow.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I came across this archived linux-kernel message:
http://www.uwsg.iu.edu/hypermail/linux/net/0007.2/0111.html
I am having the exact same problem as is outlined there, from a post three
years ago. Here's a summary:
"I think I've found a bug in UDP/ICMP code in the kernel using
traceroute.
To reproduce: Launch traceroute -n to some Linux system nearby
really quickly 3 times in the row; localhost won't work, it has to go
through network. Quick response is crucial. I used systems w/ in
the same physical network and a few routers between (still < 5 ms
response).
The effect: On third traceroute (or perhaps second/first, if you're quick
enough), ICMP port unreachable will not be sent to the UDP datagram. "
I reproduced this on a redhat 8.0 machine running kernel 2.4.23. Changing to
the -I option of traceroute (to use ICMP) works flawlessly. I'll be glad to
provide more information if you need it. Please CC, as I'm not subscribed.
- --Russell
- --
Russell Miller - rmiller@duskglow.com - Somewhere near Sioux City, IA.
Youth cannot know age, but age is guilty if it forgets youth
- Professor Dumbledore
Hi! I'm a .signature virus! Copy me into your ~/.signature, please!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAf0sUURTA4VCI9OARAs52AJ9llhS5KKvSe2nAU3lp82oySZ8c/gCfeyIK
i5V/P6Qj6ODS3jm6GSMQFrs=
=vREp
-----END PGP SIGNATURE-----
next reply other threads:[~2004-04-16 2:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-16 2:55 Russell Miller [this message]
2004-04-16 3:15 ` udp traceroute dropping packets Philippe Troin
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=200404152155.18724.rmiller@duskglow.com \
--to=rmiller@duskglow.com \
--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.