netdev - Re: eth1 became eth2, but dmesg still says eth1

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: <20070506184630.GD6222@tau.solarneutrino.net>
Date:	Sun, 6 May 2007 14:46:30 -0400
From:	Ryan Richter <ryan@....solarneutrino.net>
To:	Emil S Tantilov <emils.tantilov@...il.com>
Cc:	netdev@...r.kernel.org
Subject: Re: eth1 became eth2, but dmesg still says eth1

On Sun, May 06, 2007 at 09:19:40AM -0700, Emil S Tantilov wrote:
> >However the bond0 interface failed to come up, complaining that there
> >was no such interface as eth1.  I checked /proc/net/dev, and it listed
> >eth0 and _eth2_.  I changed the bonding configuration to use eth0 and
> >eth2 and it's working fine now.
> 
> Check your udev rules. This is usually what is causing interface to
> come up differently than what you would expect.

Thanks, I was unaware that udev had a hand in that.  It appears to be a
bug in Debian's udev configuration generator.

-ryan
-
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