My apologies for the lack of a subject. It was an unintentional screwup and my "unsend" button just wouldn't retrieve the message. :)
Your response pointed me in the correct direction. THANKS! I didn't know that my traceroute was using UDP vs windows' using ICMP. That put the problem squarely upon the linksys & not my linux box. It didn't take but a few moments to trace the problem down to year-old (UDP unfriendly) firmware. A quick flash & all is happy now. Thanks, -Chris > Message: 9 > Subject: No traceroute from linux was Re: (no subject) > From: Juan Martinez <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Organization: > Date: 29 Mar 2003 06:59:16 -0500 > Reply-To: [EMAIL PROTECTED] > > You're missing a subject on your original post. Honestly, it will help > you get a response. If you can't be bothered to give your post a > subject, how can you expect others to bother opening your message? > > Try 'traceroute -I' I had the same problem once when I was behind a > firewall on an Air Force base. The "I" switch makes traceroute use ICMP > ECHO instead of UDP datagrams. I believe the traceroute in Windows uses > ICMP ECHO by default. > -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
