Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
I have a Redhat 7.0 machine that I'm having some kind of routing problem or something with. This machine is used to monitor our routers.
The symptoms are as follows:
I can ping the router. When the router goes down, I cannot ping it (obviously). When the router comes back up, I still cannot ping it. After a few hours the problem seems to fix itself.
Oddly, this does not happen every time. I cannot figure out a pattern. The default route (0.0.0.0) is set to our gateway (a router). If I reboot the machine or add a static route to the router I can then ping it. No other Windows, UNIX, or Linux machines on the network are having this problem. Perhaps this is an arp problem? 'arp -a' does not show any of these problematic addresses. I even upgraded the kernel to 2.4 with no luck.
An idea, which may lead be way off base or could lead to something. Are you using DHCP? Is it possible that the previous DHCP info must expire and the PC request new DHCP info before you can see the router?
Distribution: Redhat v8.0 (soon to be Fedora? or maybe I will just go back to Slackware)
First, let me say, that this is a "math" problem so to speak and you have 3 unknowns and only 2 equations. What I mean is, if you haven't "found a pattern" then I am quite sure you are missing some very important part of the equation.
You say this is the only machine doing it?
Are there any other denominators? Does this system have a different kind of NIC than the other machines? Is it connected to a different switch? Are there any additional hubs or switches in its path to the router that the other machines don't have? Is it on a the same sub set as some other identical machines that this doesn't occur on?
Is this machine running a kernel, app, or distro that no other machine is running?
I got pretty drastic as I need to have this functioning as soon as possible. I wiped out Redhat and loaded OpenBSD 2.8. Same problem occurs. I moved the network cable from our switch to a hub and set the NIC for 10BaseT (as opposed to autoselect). Same problem.
TCPDUMP didn't seem to produce anything from a specific ping. The machine is running Big Brother (Network monitoring software) which the others do not.
What I finally discovered is that when these problems occur and I run 'netstat -rn' I see that the default gateway for the route to the router is set to our firewall (which is incorrect). I did not add these routes manually so I don't know why this is occurring. If I delete the route, then it's fine.
If you haven't put the firewalls IP address in any of scripts for building the routing FIB tables, then it could be that your Redhat/BSD box has been told by the firewall or another router on that subnet that the firewall is a router. Something is sending a multicast router advertisement query.
If you want to see this is the case, packet sniff for any packets from the subnet to a multicast address of 184.108.40.206, sending ICMP type 9 messages. (routers do this every 7 to 10 mins)
Then the problem is either the firewall thinks its a router or another router thinks the firewall is a router and likes
to info everyone via the router discovery protocol.