Gentoo Archives: gentoo-amd64

From: Branko Badrljica <brankob@××××××××××.com>
To: gentoo-amd64@l.g.o
Subject: Re: [gentoo-amd64] eth3 - how to set up?
Date: Mon, 07 Feb 2011 13:09:04
In Reply to: [gentoo-amd64] eth3 - how to set up? by Paul Stear
S, Paul Stear piše:
> Hi, > I have just changed my motherboard and processor and am having trouble with my > network connection. > I am having to enter in a root terminal the following each time I boot the > system:- > > ifconfig eth3 broadcast netmask up > After this everything works as it should. > Where is this setting help? > I have read the guide but nothing seems to make a difference. > I'm sure this is a lack of understanding on my part so please help. > Paul
I'm not sure I am teh one to be answering this, but since I had similar problem many times and no one else seems to be answering, here it is. Your problem is compounded. Forst part of the problem is that system remembers seeing your former cards and has now reserved for each card its ethX number. Even if cards are not there any more ( and onboard NIC is different) system keeps hoping that one day you might plug them back and keeps those names reserved. udev is userland helper that is responsible for crating logical devices on the base of kernel messages it receives about present, plugged or unpluugged devices. How and which exactly devices it creates is described in its config files in /etc/udev.d. File that should inteset you is named XX-persistent-net.rules ( XX in front are two decimals ). udev writes and updates it itself with each new card it finds, so that it knows that card with tg3 driver and MAC address XX:YY:ZZ:WW:TT.BB should be created as device eth4, for example. If you don't care how new cards are numbered or if you have only one card, simply delete it and restart the system. If you do care, edit it by hand- format is obvious. Second part of the problem is that you card is not initialized, since it is not named "eth0", as system expects. If you did erase aforementioned file, after restart new card will be shown as eth0, starttup scripts will find it and everything should fall in its place again...