linux-kernel - Re: e1000 in 2.6.21.2 and even older, like 2.6.13: eth0 does not exist but eth1 does

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] [day] [month] [year] [list]

Message-ID: <20070526055930.GA8647@atjola.homenet>
Date:	Sat, 26 May 2007 07:59:30 +0200
From:	Björn Steinbrink <B.Steinbrink@....de>
To:	Martin MOKREJŠ <mmokrejs@...osome.natur.cuni.cz>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: e1000 in 2.6.21.2 and even older, like 2.6.13: eth0 does not exist but eth1 does

Hi,

On 2007.05.25 00:00:06 +0200, Martin MOKREJŠ wrote:
>  Let me emphasize ifconfig(1) does only show loopback device all the time.
> Finally I found that in /proc/net/dev there is a row for "lo:" and "eth1".
> Yes, the network card is recognized as eth1. Blindly running 'ifconfig eth1 
> $IP'

ifconfig shows only interfaces that are "up" unless you run it with -a

> I think there is sometimes logged wrong device name to syslog, I do not 
> know why.
> But it always shows eth0 after inserting the e1000 module? Removing the 
> module
> disables the IRQ for the device, re-inserting the module again claims it is
> eth0 ... but it is eth1, I know now. The network card is wired into the 
> motherboard,

The log entries are probably right, but userspace renames the device
shortly after. Check /etc/iftab and/or your udev rules.

HTH
Björn
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/