Interface Naming inside nfsroot
Dennis Steinmann
dsteinmann at cardtech.de
Tue Mar 14 14:40:09 CET 2017
Hey Thomas,
thanks for your reply.
I've tried the new "30-interface" from github, but it doesn't work for
Ubuntu 16.04.
This script found eno16777728 as interface name, but after the
installation of Ubuntu 16.04 the name changed to "ens32":
ubuntu:~# udevadm info /sys/class/net/ens32
P: /devices/pci0000:00/0000:00:11.0/0000:02:00.0/net/ens32
E: DEVPATH=/devices/pci0000:00/0000:00:11.0/0000:02:00.0/net/ens32
E: ID_BUS=pci
E: ID_MODEL_FROM_DATABASE=82545EM Gigabit Ethernet Controller (Copper)
(PRO/1000 MT Single Port Adapter)
E: ID_MODEL_ID=0x100f
E: ID_NET_DRIVER=e1000
E: ID_NET_LINK_FILE=/lib/systemd/network/99-default.link
E: ID_NET_NAME_MAC=enx005056b175bb
E: ID_NET_NAME_PATH=enp2s0
E: ID_NET_NAME_SLOT=ens32
E: ID_OUI_FROM_DATABASE=VMware, Inc.
E: ID_PATH=pci-0000:02:00.0
E: ID_PATH_TAG=pci-0000_02_00_0
E: ID_PCI_CLASS_FROM_DATABASE=Network controller
E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller
E: ID_VENDOR_FROM_DATABASE=Intel Corporation
E: ID_VENDOR_ID=0x8086
E: IFINDEX=2
E: INTERFACE=ens32
E: SUBSYSTEM=net
E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/ens32
E: TAGS=:systemd:
E: USEC_INITIALIZED=1330762
Also with a deleted /lib/systemd/network/99-default.link file, it is
still ens32.
The same udevadm info under the debian 8 nfsroot on the same machine:
nfsroot:~# udevadm info /sys/class/net/eth0
P: /devices/pci0000:00/0000:00:11.0/0000:02:00.0/net/eth0
E: DEVPATH=/devices/pci0000:00/0000:00:11.0/0000:02:00.0/net/eth0
E: ID_BUS=pci
E: ID_MODEL_FROM_DATABASE=82545EM Gigabit Ethernet Controller (Copper)
(PRO/1000 MT Single Port Adapter)
E: ID_MODEL_ID=0x100f
E: ID_NET_DRIVER=e1000
E: ID_NET_LABEL_ONBOARD=enEthernet0
E: ID_NET_NAME_MAC=enx005056b175bb
E: ID_NET_NAME_ONBOARD=eno16777728
E: ID_NET_NAME_PATH=enp2s0
E: ID_NET_NAME_SLOT=ens32
E: ID_OUI_FROM_DATABASE=VMware, Inc.
E: ID_PATH=pci-0000:02:00.0
E: ID_PATH_TAG=pci-0000_02_00_0
E: ID_PCI_CLASS_FROM_DATABASE=Network controller
E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller
E: ID_VENDOR_FROM_DATABASE=Intel Corporation
E: ID_VENDOR_ID=0x8086
E: IFINDEX=2
E: INTERFACE=eth0
E: MATCHDEVID=0x0
E: MATCHIFTYPE=1
E: SUBSYSTEM=net
E: USEC_INITIALIZED=63509
CentOS 7 would work with ID_NET_NAME_ONBOARD / eno16777728, so this is
ok. But why does Ubuntu has ens32?
What would be the best practice to work with this?
Thanks,
Dennis
Am 14.03.2017 um 11:37 schrieb Thomas Lange:
>>>>>> On Tue, 14 Mar 2017 11:21:27 +0100, Dennis Steinmann <dsteinmann at cardtech.de> said:
>
> > When I boot the installed systems (CentOS 7 or Ubuntu 16.04), I have
> > eno16777984 (CentOS 7) or ens160 (Ubuntu) instead of eth0.
>
> Have a look at the new code in DEBIAN/30-interfaces
> https://github.com/faiproject/fai/blob/master/examples/simple/scripts/DEBIAN/30-interface
>
> We now try to determine the new names, if a newer version of udev is
> found. I guess you can adopt this code also for CentOS.
>
> I'm pretty sure that installing CentOS 7 with Debian 8 nfsroot works
> without any changes, if you use FAI 5.3.4.
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.uni-koeln.de/pipermail/linux-fai/attachments/20170314/cb216482/attachment.asc>
More information about the linux-fai
mailing list