Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Okay, I'm working on a special project that requires me to add an additional IP to my interface. I have eth2 that is currently running fine and I can ping other machines and send/receive packets.
and it seems like it works fine and all, but I can't ping this IP from other machines. I get: connect: Network is unreachable
Now, I tried to add a route to my routing table and I did:
route add -net 192.168.1.0 netmask 255.255.255.0 eth2
Now, when I do a ping, instead of that network unreachable message, I get the PING header information BUT it gets stuck there forever:
> ping 192.168.1.100
PING 192.168.1.100 (192.168.1.100) 56(84) bytes of data.
Any idea why this is happening and how I can fix it?
It seems pretty weird. But, at first, are you sure there is not any firewall rule which could be blocking input data?
I am behind no firewall. That's for sure. it's an internal network with no access to outside world and therefore no need for a firewall. I know it's weird, that's why I asked for help!
Are you using a Redhat-ish distro that has SELinux? SE Linux is kind of like a security layer that prevents certain un-authorized system changes. If you do try disabling SELinux temporarily and see if your changes take.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.