my server can't ping other boxes on private network (192.168.0.0)
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.
my server can't ping other boxes on private network (192.168.0.0)
I run a server that is connected to several other boxes in a private network (192.168.0.0). I have had no problems previously, but upon a reinstall of Debian squeeze I have no connectivity to the private network: a ping of other addresses on that network fail. Ping and connection to outside world is fine. This box is configured similarly to another on this private network which connects successfully. I have quadruple-checked all my basic information. I post my ifconfig below of the malfunctioning device, then the ifconfig for equivalent nic on a box connected succesfully to the private network.
Questions:
1.Could it be a cable problem? (I don't see how since the cables have not been changed I do not believe since my reinstallation).
2. What about the difference in the last lines of eth1 below and eth2 of the successful box. Is it significant that the bad eth1 reads ... Memory:fc3a0000-fc3c0000
while eth2 on the good box reads Interrupt:16 Base address:0xef00
I suspect a routing problem, because you've got eth0 facing the public, and eth1 facing the internal network, and you're working just fine through the public interface. I suspect that works because the default route is pointing to the public interface.
Check your route table with the route command, and use route add if there's nothing there for the private network.
I suspect a routing problem, because you've got eth0 facing the public, and eth1 facing the internal network, and you're working just fine through the public interface. I suspect that works because the default route is pointing to the public interface.
Check your route table with the route command, and use route add if there's nothing there for the private network.
As SL00b suggested please show output of commands: # ip r s
# ip a s
# netstat -rn
It turned out to be a cable problem. But these commands you all suggested will be very useful to me. They give me output I was looking for on this and on other problems.
Thanks again!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.