renamed eth0 to eth1, why?

[Neal Becker]

Ah, this notebook just came back from having it's MB replaced.  I guess that 
explains it.

Josep Puigdemont wrote:

> Hi,
> 
> I experienced a similar situation a while ago. In my case the problem
> was that the driver changed the MAC address of the device (it was a
> bug in r8169 driver), udev simply detected a "new" network card and,
> to distinguish it from the old one, it automatically performed the
> device name change.
> 
> I don't know if this is the case for you, but if so, to get back the
> old MAC address I had to power-cycle the card (it required removing
> the network cable from the card too).
> 
> /Josep
> 
> 
> On Mon, Mar 9, 2009 at 11:49 AM, Neal Becker <ndbecker2 at gmail.com> wrote:
>> Mar  9 06:19:55 nbecker1 kernel: eth0: RTL8168b/8111b at
>> 0xffffc2000034c000, 00:23:8b:53:f0:80, XID 38000000 IRQ 17
>> Mar  9 06:19:55 nbecker1 kernel: udev: renamed network interface eth0 to
>> eth1
>>
>> Uh, why?  This notebook only has one wired interface.
>>
>> 2.6.27.19-170.2.35.fc10.x86_64
>>
>>
>> --
>> fedora-test-list mailing list
>> fedora-test-list at redhat.com
>> To unsubscribe:
>> https://www.redhat.com/mailman/listinfo/fedora-test-list
>>
>