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.
Had a network problem the other night and had to reboot the server. Upon starting the nic cards reversed order. The eth0 information was switch with the eth1 information creating tons of confusion. The mac address was hard coded in the /etc/syconfig/ area but hwconf seems to have chanced. Any idea why the cards would have switched? Can anyone point me in the right direction?
The first card to load it's driver gets to be eth0..
It can be controlled by delaying setting up eth1 until eth0 settles,
however there are several factors in play here.
acpi is the first to detect the card, then hotplug then your /etc/modules file then the /etc/init.d scripts.
Usually, the rc.d scripts and ifup allow you to specify a pre-up script/command, which you could use to load the respective eth modules, if they aren't autoloading already. Your distro will have a specific way of doing this..
But if all else fails, compile into the kernel the driver for the card you want to be eth0. This ensures it will get loaded by the acpi system before any other scripts run.
The problem is that the cards are the same and the system has been rebooted several times before without the cards switching. Now all of the suddon the cards switch and great a networking nightmare. I have never had cards switch at this point.
I will have to moniter it from this point forward. I just started working for this company and don't know anything about this systems. They had no linux admin until about 2 weeks ago... me. I was just concerned because I have never seen cards set to macs chance name locations without being told to do so. I am starting to believe that someone set it up that way and upon boot it did it. No way to tell because the logs don't show anything but normal steps.
Distribution: #1 PCLinuxOS -- for laughs -> Ubuntu, Suse, Mepis
slayer17 ... there is no magic .. it was always like this.
It has to do with what boot/install did with module.conf does ..
edit the file and live happy thereafter.
Peter_Robb is correct, but the only twist I am suggesting is that it was always like this .. has happend to me a zillion times ... mostly with Suse, knoppix/Mepis never caused the same grief on the same hardware