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.

I've got 4 NIC's in my server (debian 5.0.2)as im attempting to set up a load balancer. I just installed 2 extra NIC's and booted, linux proceeded to rename my interfaces (side request - anyone know how to stop that from happening? i know it should only really occur when new hardware is put in).

So i went through udev and renamed my interfaces appropriately which went fine. I now have:

eth0/eth1 are not setup yet. Now the server was acting as a router for the 2 internal networks before i put in the 2 new NIC's but now gig0 and gig1 can't seem to communicate to their respective networks. Does anyone know why this would be ?

From the server i cannot ping the gateway for either network nor any hosts and vice-versa. The weird thing is that ifconfig is showing tx and rx bytes on the gig interfaces... the routing table seems to reflect the correct configuration. I can write it up if need be but i can't copy n paste because i can only console it

ANy help would be appreciated - did i miss something that you need to do when renaming interfaces?

if you absolutely sure about ur route table check for firewall .
if firewall is configured correctly and your other side that you want to ping is pingable ,so i'm sure something wrong is with ur routing table.

Now when i ping the networks i get destination unreachable from their respective (local) NIC's on the server. Bear in mind that this was communicating perfectly fine before i changed the interface names from eth0/eth1 - gig0/gig1. Are the interfaces referenced in some other config that i don't know about?