[105467] in North American Network Operators' Group
RE: easy way to scan for issues with path mtu discovery?
daemon@ATHENA.MIT.EDU (Frank Bulk - iNAME)
Tue Jun 24 10:57:59 2008
From: "Frank Bulk - iNAME" <frnkblk@iname.com>
To: "'Darden, Patrick S.'" <darden@armc.org>,
<nanog@nanog.org>
In-Reply-To: <CBE22E5FF427B149A272DD1DDE1075240236855F@EX2K3.armc.org>
Date: Tue, 24 Jun 2008 09:57:47 -0500
Reply-To: frnkblk@iname.com
Errors-To: nanog-bounces@nanog.org
Look at mturoute: http://www.elifulkerson.com/projects/mturoute.php
Frank
-----Original Message-----
From: Darden, Patrick S. [mailto:darden@armc.org]
Sent: Tuesday, June 24, 2008 9:28 AM
To: nanog@nanog.org
Subject: easy way to scan for issues with path mtu discovery?
Hi all,
Does anyone know of an easy way to scan for issues with path mtu discovery
along a hop path? E.g. if you think someone is ICMP black-holing along a
route, or even on the endpoint host, could you use some obscure nmap flag to
find out for sure, and also to identify the offending hop/router/host? What
tool would you use to test for this, and how would you do such a test? Is
there any probing tool that does checks like this automatically?
Seems to me this happens often enough that someone has probably already
figured it out, so I am trying not to reinvent the wheel. All I can think
of would be to handcraft packets of steadily increasing sizes and look for
replies from each hop on the route (which would be laborious at best).
Google has not been kind to my researches so far.
I appreciate any help!
--Patrick Darden
