原创 2012年03月30日 11:01:03


  • Servers often have multiple Ethernet ports, either embedded on the motherboard, or on add-in PCI cards. Linux has traditionally named these ports ethX, but there has been no correlation of the ethX names to the chassis labels - the ethX names are non-deterministic. Starting in Fedora 15, Ethernet ports will have a new naming scheme corresponding to physical locations, rather than ethX. Ethernet ports embedded on server motherboards will be named em<port_number>, while ports on PCI cards will be named p<slot_number>p<port_number>, corresponding to the chassis labels. Additionally, if the network device is an SR-IOV Virtual Function or has Network Partitioning (NPAR) capability, the name will have a suffix of _<virtual_function> or _<partition>.

By changing the naming convention, system administrators will no longer have to guess at the ethX to physical port mapping, or invoke workarounds on each system to rename them into some "sane" order.

This feature affects all physical systems that expose network port naming information in SMBIOS 2.6 or later (specifically field types 9 and 41). Dell PowerEdge 10G and newer servers (PowerEdge 1950 III family, PowerEdge R710 family, and newer), and HP ProLiant G6 servers and newer are known to expose this information, as do some newer desktop models. Furthermore, most older systems expose some information in the PCI IRQ Routing Table, which will be consulted if information is not provided by SMBIOS.

Fedora running as a guest virtual machine will continue to use the ethX names.

Existing installations upgraded to Fedora 15 will not see a change in names unless /etc/udev/rules.d/70-persistent-net.rules is deleted and the HWADDR lines are removed from all /etc/sysconfig/network-scripts/ifcfg-* files, and those files are renamed to use the new device names.

You may continue to write rules in /etc/udev/rules.d/70-persistent-net.rules to change the device names to anything you wish. Such will take precedence over this physical location naming scheme. Such rules may look like:

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:11:22:33:44:55", ATTR{type}=="1", KERNEL=="eth*", NAME="public"

This feature may be disabled by passing "biosdevname=0" on the kernel command line, in which case, behavior will revert to using ethX names.

Upgrading from an earlier version of Fedora (including 15-Alpha or -Beta) to Fedora 15 may result in a change of network device names from an earlier biosdevname naming scheme to the final naming scheme described here. Configuration files must be manually adjusted accordingly.

简单的说想恢复到传统的命名方式,只要在kernel command line 里加上biosdevname=0就可以了,修改grub2 kernel command line的路径为:/etc/default/grub




声明下,因为对底层协议不是很了解,如有错误,麻烦指正,谢谢! 1、先来简单了解下ARP地址解析协议的用途 设备存在网络层地址(即IP地址)和链路层地址(即MAC地址),MAC地址是适配器(即网卡...
  • wustzjf
  • wustzjf
  • 2016年01月29日 19:53
  • 2023

(Linux 技术)Fedora 16下编译无线网卡驱动成功

(本来发在红联社区,不过由于今天更新系统又编译了一次,感觉需要温习,故在这里也发一下,,,高手勿喷)     大学里不知有多少开源爱好者,在为不同版本的Linux驱动而头疼。特别是像我这里用校园网的...
  • zspcb
  • zspcb
  • 2012年09月04日 23:58
  • 1116


转自:http://wiki.ubuntu.org.cn/%E7%BD%91%E5%8D%A1 目录 [隐藏] 1 基础知识2 ifconfig简介 2.1...

嵌入式 获取网卡设备以及IP和MAC地址示例以及网络编程之ioctl小结

#include #include #include #include #include #include #include #include #ifdef SOLAR...
  • skdkjxy
  • skdkjxy
  • 2014年04月28日 15:57
  • 1822


  • 2017年11月13日 13:44
  • 4KB
  • 下载


  • myxmu
  • myxmu
  • 2012年09月16日 23:37
  • 578

xen 添加网卡设备初步分析之 network-attach 流程分析

本文从 xm network-attach 命令着手,逐步分析xen 平台添加网卡的整体流程。需要说明的是,本文档只介绍针对在PV驱动环境下前后端网卡设备的添加流程。对于非PV驱动下的全虚拟化设备,...

linux TUN 虚拟网卡设备

[网络虚拟化技术(二): TUN/TAP MACVLAN MACVTAP] https://blog.kghost.info/2013/03/27/linux-network-tun/ TUN 设备...
  • s1070
  • s1070
  • 2016年08月08日 17:56
  • 482


static int __devinit rtl8139_init_one (struct pci_dev *pdev, const struct pci_device_id *ent)函数功能描述:...
  • jw212
  • jw212
  • 2011年07月07日 10:10
  • 618