Date: Wed, 12 Mar 2003 15:23:14 -0800 (PST) From: David@webedited.com To: Nathan Kinkade <nkinkade@dsl-only.net> Cc: Dragoncrest <dragoncrest@voyager.net>, <freebsd-questions@FreeBSD.ORG> Subject: Re: Traceroute issues Message-ID: <Pine.LNX.4.44.0303121518140.2416-100000@buzz.frogspace.net> In-Reply-To: <20030312165324.GB398@sub21-156.member.dsl-only.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 12 Mar 2003, Nathan Kinkade wrote: > > At 09:13 PM 3/11/03 -0800, Daxbert wrote: > > >Quoting Dragoncrest <dragoncrest@voyager.net>: > > > > > >> Hi all. Got a really weird issue here. Got a router that > > >> uses simple nat that for some reason won't allow me to traceroute > > >> out of my freebsd box, but every other computer connected to the > > >> router can, and can traceroute with flying colors. What might > > >> possibly be wrong with my machine that I can't traceroute anywhere? > > > > > >Could if be that the other hosts are using ICMP instead of UDP for > > >traceroute? > This may not be the issue in the first place, but if you want to try an > ICMP traceroute do: `traceroute -P icmp <host>`. I had/have the same issue with my D-link router. Originally I was using bridging on my Freebsd box so thought it I had set that up wrong, or it simply broke traceroute. However, it also occured without the bridging. Using -P icmp solves the issue completely for me. DG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.44.0303121518140.2416-100000>