Thanks, but that didn't work. The google example gave me an error message (i.e. the help screen). traceroute -I requires an interface for an argumnt, the only choice I have is eth0, and that gives the same output as with no option. I messed around with some other options and had no luck (-g, -r, -t, -4, -6). Using tracroute 0.6.2, SuSE 8.2. Greg James Baldassari wrote:
Hi Greg. I have a similar situation at home. When I need to do a traceroute I use the -I switch (e.g. traceroute -I www.google.com), which uses ICMP echos instead of UDP datagrams. I believe that ping uses ICMP requests by default, which may explain why you can ping outside your network. Hope this helps.
-James Baldassari
I'm having trouble getting traceroutes to go out with my slick new dsl connection. The modem has a router built into it, and even with its internal firewall turned off, the only output I get from a traceroute is the router'r IP number and times, followed by 29 lines of stars.
I tried shutting down the network and using my dialup account, and traceroute works fine. I know it's not the firewall on my machine, because it makes no difference if it's on or off with the dsl, and traceroute works on the dialup with the firewall running. (Yes, I did remember to change the default path in the firewall config from eth0 to ppp0)
Any ideas? Is this likely to be something built into the dsl modem, or something with Verizon? Or might I have something screwed up in my network setup? I can ping my other computers and I can ping out to the internet ok.
Thanks, Greg Avedissian
_______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
_______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug