public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Branko Badrljica <brankob@avtomatika.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] eth3 - how to set up?
Date: Mon, 07 Feb 2011 13:28:40 +0000	[thread overview]
Message-ID: <4D4FF388.4030002@avtomatika.com> (raw)
In-Reply-To: <201102071200.59380.gentoo@appjaws.plus.com>

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 192.168.1.6 broadcast 192.168.1.255 netmask 255.255.255.0 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...





      parent reply	other threads:[~2011-02-07 13:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-07 12:00 [gentoo-amd64] eth3 - how to set up? Paul Stear
2011-02-07 12:12 ` Dale
2011-02-07 12:13 ` Claes Gyllenswärd
2011-02-07 12:24 ` Agostino Sarubbo
2011-02-07 12:35 ` P.V.Anthony
2011-02-07 12:47 ` Stefan G. Weichinger
2011-02-07 12:51 ` Thanasis
2011-02-07 13:04 ` Alex Schuster
2011-02-07 13:13 ` Joost Roeleveld
2011-02-07 13:28 ` Branko Badrljica [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D4FF388.4030002@avtomatika.com \
    --to=brankob@avtomatika.com \
    --cc=gentoo-amd64@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox