netdev - Re: about multiple network interface

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20071022091410.GB12186@2ka.mipt.ru>
Date:	Mon, 22 Oct 2007 13:14:10 +0400
From:	Evgeniy Polyakov <johnpol@....mipt.ru>
To:	wit <is01kzh@...il.com>
Cc:	netdev@...r.kernel.org
Subject: Re: about multiple network interface

On Mon, Oct 22, 2007 at 10:09:38AM +0800, wit (is01kzh@...il.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
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html