Re: First NIC appearing as eth10 instead of expected eth0

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



thomas62186218@xxxxxxx wrote:


> I am running Fedora 8 32-bit with no updates (fresh install) on a
> server with a Tyan S5380 motherboard with the latest 2.00 BIOS. This
> motherboard has two Intel GbE ports on the motherboard.
> 
> Oddly, when I type ifconfig -a, these GbE ports appear as eth10 and
> eth11. There is no eth0. I've been around Linux for a few years and
> have never seen anything like this, so I'm stumped. Why would it not
> map these GbE ports as eth0 and eth1, as expected?
> 
> [root@localhost ~]# ifconfig -a
> eth10     Link encap:Ethernet  HWaddr 00:E0:81:79:C9:51
>           inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0
>           inet6 addr: fe80::2e0:81ff:fe79:c951/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:2756 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:1732 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:3781521 (3.6 MiB)  TX bytes:132139 (129.0 KiB)
>           Base address:0x2000 Memory:d8020000-d8040000
> 
> eth11     Link encap:Ethernet  HWaddr 00:E0:81:79:C9:50
>           BROADCAST MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>           Base address:0x2020 Memory:d8060000-d8080000
> 
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           inet6 addr: ::1/128 Scope:Host
>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>           RX packets:3066 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:3066 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:2968932 (2.8 MiB)  TX bytes:2968932 (2.8 MiB)
> 
> 
> 
> Any ideas on this?

In addition to the entries in /etc/sysconfig/network-scripts/ifcfg-eth?
and /etc/modprobe.conf mentioned by others,
I think udev can affect the naming of interfaces,
as determined eg on my system by the entries
in /etc/udev/rules.d/70-persistent-net.rules .

-- 
Timothy Murphy  
e-mail (<80k only): tim /at/ birdsnest.maths.tcd.ie
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland

-- 
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora Magazine]     [Fedora News]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux