It may not necessarily be a local fw setup issue ...
some routers along the path may be configured to block
icmp and you get '*' for such hop.
Martin
17 ge-1-1.r0809.stngva01.us.wh.verio.net
(129.250.27.187) 62.065 ms 62.128 ms 62.837 ms
18 199.239.254.130 62.883 ms 63.087 ms 63.152 ms
19 * * *
20 198.65.246.22 62.538 ms 62.507 ms 62.500 ms
--- Peer Stefan
From: Michael Satterwhite [mailto:michael@weblore.com] I'm having a problem with traceroute. When I run it (e.g. traceroute weblore.com), it pauses for a bit, then prints out a series of hops with absolutely no information. After a bit, it repeats
Hi, this.
Here's a sample output:
linux:/home/michael # traceroute weblore.com traceroute to weblore.com (198.65.246.22), 30 hops max, 40 byte packets 1 * * * 2 * * * 3 * * * 4 * * * 5 * * * 6 * * *
Is there something I'm missing?
traceroute uses ICMP to determine the route. If you have SuSEFirewall2 installed then set FW_KERNEL_SECURITY and FW_ALLOW_FW_TRACEROUTE to "yes" in /etc/sysconfig/SuSEfirewall2.
regards, Stefan
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
__________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com