Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 12 May 2004 12:33:20 -0700
From:      Mike Hogsett <hogsett@csl.sri.com>
To:        Clint Olsen <clint@0lsen.net>
Cc:        questions@freebsd.org
Subject:   Re: Traceroute supporting ICMP ECHO 
Message-ID:  <200405121933.i4CJXKOB022965@beast.csl.sri.com>
In-Reply-To: Message from Clint Olsen <clint@0lsen.net>  of "Wed, 12 May 2004 12:29:19 PDT." <20040512192918.GA69895@0lsen.net> 

next in thread | previous in thread | raw e-mail | index | archive | help

> I'm using 4.7p1 here, and I've had all sorts of fun on occasion with
> traceroute and my various firewall/routers.  The default traceroute will
> not work since UDP traffic is apparently blocked on the return.  Opening =
up
> port ranges on my router just doesn't seem right.  However, Linux
> traceroute has a -I option (I think Windows tracert uses ICMP ECHO by
> default) which allows it to work through a home firewall router.  The
> FreeBSD port for mtr also works.
>=20
> Is there anyone who has considered adding this capability to FreeBSD?

I think its already there. ( 4.9-RELEASE-p3 )

=46rom traceoute(8)

       -P     Send  packets  of specified IP protocol. The currently suppor=
ted
              protocols are: UDP, TCP, GRE and ICMP. Other protocols may  a=
lso
              be  specified  (either  by name or by number), though tracero=
ute
              does not implement any special knowledge of  their  packet  f=
or-
              mats. This option is useful for determining which router alon=
g a
              path may be blocking packets based on IP  protocol  number.  =
But
              see BUGS below.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200405121933.i4CJXKOB022965>