about multiple network interface

about multiple network interface

[wit]

Hi all,

   Sorry, I don't know if this is the right mail list. I got the
following question:
   I have a e100 card and a e1000 card. Whenever I boot the system, I
found the eth0 matches the e1000 card, and the eth2 matches the other.
How can I force the eth0 to match the e100 card and the eth2 to match
e1000?

Re: about multiple network interface

[Evgeniy Polyakov]

On Thu, Oct 18, 2007 at 09:06:40PM +0800, wit (is01kzh@gmail.com) wrote:
> Hi all,
> 
>    Sorry, I don't know if this is the right mail list. I got the
> following question:
>    I have a e100 card and a e1000 card. Whenever I boot the system, I
> found the eth0 matches the e1000 card, and the eth2 matches the other.
> How can I force the eth0 to match the e100 card and the eth2 to match
> e1000?

Hi.

Check your /etc/modprobe.conf and put there

alias eth0 e100
alias eth2 e1000


-- 
	Evgeniy Polyakov

Re: about multiple network interface

[wit]

Thanks very much

But this does work until I add a ifcfg-eth0 in
sysconfig/network-script with the following content:
DEVICE=eth0
ONBOOT=yes

What is the relationship between these two files? And sometimes, I see
this message:
Bringing up interface eth0:  e100 device does not seem to be present, delaying e
th0 initialization.
Why??

2007/10/18, Evgeniy Polyakov <johnpol@2ka.mipt.ru>:
> On Thu, Oct 18, 2007 at 09:06:40PM +0800, wit (is01kzh@gmail.com) wrote:
> > Hi all,
> >
> >    Sorry, I don't know if this is the right mail list. I got the
> > following question:
> >    I have a e100 card and a e1000 card. Whenever I boot the system, I
> > found the eth0 matches the e1000 card, and the eth2 matches the other.
> > How can I force the eth0 to match the e100 card and the eth2 to match
> > e1000?
>
> Hi.
>
> Check your /etc/modprobe.conf and put there
>
> alias eth0 e100
> alias eth2 e1000
>
>
> --
>         Evgeniy Polyakov
>

Re: about multiple network interface

[Evgeniy Polyakov]

On Mon, Oct 22, 2007 at 10:09:38AM +0800, wit (is01kzh@gmail.com) wrote:
> But this does work until I add a ifcfg-eth0 in
> sysconfig/network-script with the following content:
> DEVICE=eth0
> ONBOOT=yes
> 
> What is the relationship between these two files? And sometimes, I see

It depends on your distro - when script calls "modprobe $DEVICE"
this ends up with modprobe eth0, which will check modprobe.conf.

> this message:
> Bringing up interface eth0:  e100 device does not seem to be present, delaying e
> th0 initialization.
> Why??

This is fedora, right? Check you kernel config, scripts and whatever is
needed to load driver first and only then try to setup an address.

-- 
	Evgeniy Polyakov

Re: about multiple network interface

[wit]

thank you very much..

2007/10/22, Evgeniy Polyakov <johnpol@2ka.mipt.ru>:
> On Mon, Oct 22, 2007 at 10:09:38AM +0800, wit (is01kzh@gmail.com) wrote:
> > But this does work until I add a ifcfg-eth0 in
> > sysconfig/network-script with the following content:
> > DEVICE=eth0
> > ONBOOT=yes
> >
> > What is the relationship between these two files? And sometimes, I see
>
> It depends on your distro - when script calls "modprobe $DEVICE"
> this ends up with modprobe eth0, which will check modprobe.conf.
>
> > this message:
> > Bringing up interface eth0:  e100 device does not seem to be present, delaying e
> > th0 initialization.
> > Why??
>
> This is fedora, right? Check you kernel config, scripts and whatever is
> needed to load driver first and only then try to setup an address.
>
> --
>        Evgeniy Polyakov
>