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.
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.
I am using ip aliases via /etc/sysconfig/network-scripts/ifcfg-eth0-range0, but I don't think that's related (error messages show up before "Bringing up interface eth0-range0" message).
The odd thing is that the interface actually does seem to come up correctly, with all the aliases, so I'm not sure what the error is referring too. I know it is assigning the interface an ipv6 address as well, could this be the cause of the error?
One last thing, eth0 has a /29 subnet mask, but whenever I reboot the computer the routing table has the correct default gw, a correct /29 network route for the device, and a completely unnecessary /8 network route for that device. Any idea where the /8 address is coming from and how I can stop it?
Neither of these are really hurting anything, but they ShouldNotHappen(tm), so I'd like to track down the problem.
ifcfg-eth0, ifcfg-eth0-range0, and network (ips have been changed to protect the ignorant)
It's been happening since day 1 I believe. This is FC4 btw. Removing the network card is not really an option for two reasons; one it's built-in to the motherboard, but actually even more important is that this is a production machine - downtime is not allowed.