Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello,
This doesn't seem to be a major problem, but I just installed a Linksys befsr41 ver3 router, and installed a default route -gateway as 192.168.1.1.
This works well and I seem to be able to ping everything. The one thing I noticed was the inability to traceroute. I have a WinXP box in the other room (The linux box is 192.168.1.101 and WinXP is 192.168.1.100 ---> both static meaning DHCP is turned off in router...)
--anyway the winxp box can tracert etc.
Back to Linux: I have 3 entries in my route table. (The loopback, the 192.168.1.0 net and the default GW) . What am I missing? I would really like to be able to traceroute from my slackware box. Hmmmm?
Thanks ahead of time,
BC
Last edited by bonecrusher; 05-21-2004 at 12:57 PM.
Well since it is a class c address and not subnetted further I assumed it should be 255.255.255.0 ??
As I mentioned I am able to ping outside of network (to Internet) - I just can't get anything from a traceroute. On a tcpdump it appears that it is receiving something from the address (a UDP packet I think) when I am in the middle of running traceroute, but the actual traceroute just comes back with " * * * ".
-bc
Last edited by bonecrusher; 05-22-2004 at 12:05 AM.
I wanted to note that I also had the same problem with knoppix (live distro) on my p4. Everything worked great when I got it up and going with the right driver (3c940 gig/ethernet ).
But, when I routed it to the Internet, I would have web working, ftp etc etc, just NO TRACEROUTE. And again, WinXP can do the "tracert" under the same exact machine. I am thinking that maybe I am not routing correctly. Here is my routes on the slack machine:
(The routing table is the same on the knoppix boot):
bash-2.05b# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.1.1 0.0.0.0 UG 1 0 0 eth0
bash-2.05b# netstat -r
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
localnet * 255.255.255.0 U 0 0 0 eth0
loopback * 255.0.0.0 U 0 0 0 lo
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
AND HERE IS A PORTION OF "TCPDUMP" WHILE TRACEROUTING:
I was having the same problem you were and I ran across your post while I was doing a search on google. I found out that windows uses icmp datagrams for traceroute. Linux traceroute runs using udp datagrams by default. As I didn't have my router configured to forward those udp ports to the system I was using to originate the traceroute I wasn't getting a response. If you look at the man page for traceroute you will see that you can change the traceroute to use icmp with -I. Ex : traceroute -I google.com
Originally posted by nightswolf I was having the same problem you were and I ran across your post while I was doing a search on google. I found out that windows uses icmp datagrams for traceroute. Linux traceroute runs using udp datagrams by default. As I didn't have my router configured to forward those udp ports to the system I was using to originate the traceroute I wasn't getting a response. If you look at the man page for traceroute you will see that you can change the traceroute to use icmp with -I. Ex : traceroute -I google.com
Right on- I appreciate the input. I was wondering why it wasn't responding. I knew it had something to do with port/packet forwarding as it worked under windows but not linux.. (One of the few things that is reversed HA) Guess once again rtfm and I should pay more attn to man pages. Strange, because I always thought traceroute was a icmp based application. Oh well... thanks!
-bc
Last edited by bonecrusher; 06-09-2004 at 01:11 PM.
np. everyone else in the netops department at my work thought that linux used imcp for traceroutes, as do the majority of the websites that I found when I was looking for an explanation. Finally found one post where someone mentioned that linux traceroutes use udp by default. Looked at the man page, beat my head against the wall a few times, replied to your post, and reveled in the fact that I've finally purged redmond's blight from every system I own.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.