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!
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.
Because the 192.168.30.* subnet only needs to know how to get to its gateway/router (and the router decides how to get requests to the next network, which happens to be 192.168.29.* in this case). There is no 192.168.29.1 gateway on the first network; they're two different networks.
Distribution: Debian, Ubuntu, Redhat, Fedora, SLES, OpenSUSE, FreeBSD, Mac OS X
Your subnet mask is 255.255.255.0, which means 192.168.29.0 & 192.168.30.0 are two different networks and hence packets from 192.168.29.0 needs to be transfered through a gateway/router to reach to 192.168.30.0
You need to under stand the working of gateway:
This route has been added to enable communication between these two different networks.
When gateway receives packet from 192.168.29.0 network it checks for destination network and since destination network is different from the the source network it then checks for other lancard and hence for the other network. If it founds one (which is also true in your case) then those packets are transfered to the destined network.
If your subnet mask would have been 255.255.0.0 then the two networks would have been same in that case gateway won't check for other network and hence no need to add the route.