Public bug reported:
Out of a discussion (with Stuart Langridge) about SystemD's new
interface naming convention I discovered the following inconsistency in
device naming on a BIOS vs a UEFI system...
Using QEmu, set to act as a "440FX BIOS" system, and booting up the
Ubuntu MATE 16.04.2 LTS ISO I get the following output from "ifconfig"
...
eth0 Link encap:Ethernet HWaddr CA:FE:15:60:0D:70
inet addr:192.168.0.105 Bcast:192.168.0.1 Mask:255.255.255.0
inet6 addr: fe80::b19a:de94:6e2c:37b7/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:9100 Metric:1
RX packets:54071 errors:0 dropped:0 overruns:0 frame:0
TX packets:48515 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:22009423 (20.9 MiB) TX bytes:25690847 (24.5 MiB)
Interrupt:16
Doing the same thing again but with QEmu being set to act as a "Q35
UEFI" system (using the OVMF firmware) "ifconfig" gives me ...
enp0s3 Link encap:Ethernet HWaddr CA:FE:15:60:0D:70
inet addr:192.168.0.105 Bcast:192.168.0.1 Mask:255.255.255.0
inet6 addr: fe80::b19a:de94:6e2c:37b7/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:9100 Metric:1
RX packets:27003 errors:0 dropped:0 overruns:0 frame:0
TX packets:16171 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:11000712 (10.2 MiB) TX bytes:8563615 (8.1 MiB)
Interrupt:16
NOTE: The same is true on my desktop system (UEFI capable), the network
interface is "enp0s5" not "eth0".
The later one would be more like what I would expect as SystemD's
documentation goes to great lengths to try and explain the new naming
convention for network interfaces.
This inconsistency could actually lead to further problems down the road
with other packages ... for example Samba. The default example config
reads "bind interfaces = 127.0.0.0/8 eth0" (commented out though) where
"eth0" is not really a good example default because with SystemD it no
longer exists (at least on a UEFI system - and I had that issue with
several friends already where I told them "uncomment 'bind interfaces'"
to have samba only bind/listen to the desired interfaces ... and then it
not working because there's no "eth0"). It might be better to determine
and append the lan/subnet post-install (i.e. 192.168.0.0/24) or settle
on a uniform device naming convention for the network interfaces.
The problem should be reproducible by simply booting a installation ISO
on a BIOS and UEFI system (or accordingly configured VM).
** Affects: ubuntu
Importance: Undecided
Status: New
** Description changed:
Out of a discussion (with Stuart Langridge) about SystemD's new
interface naming convention I discovered the following inconsistency in
device naming on a BIOS vs a UEFI system...
Using QEmu, set to act as a "440FX BIOS" system, and booting up the
Ubuntu MATE 16.04.2 LTS ISO I get the following output from "ifconfig"
...
- eth0 Link encap:Ethernet HWaddr CA:FE:15:60:0D:70
- inet addr:192.168.0.105 Bcast:192.168.0.1 Mask:255.255.255.0
- inet6 addr: fe80::b19a:de94:6e2c:37b7/64 Scope:Link
- UP BROADCAST RUNNING MULTICAST MTU:9100 Metric:1
- RX packets:54071 errors:0 dropped:0 overruns:0 frame:0
- TX packets:48515 errors:0 dropped:0 overruns:0 carrier:0
- collisions:0 txqueuelen:1000
- RX bytes:22009423 (20.9 MiB) TX bytes:25690847 (24.5 MiB)
- Interrupt:16
+ eth0 Link encap:Ethernet HWaddr CA:FE:15:60:0D:70
+ inet addr:192.168.0.105 Bcast:192.168.0.1 Mask:255.255.255.0
+ inet6 addr: fe80::b19a:de94:6e2c:37b7/64 Scope:Link
+ UP BROADCAST RUNNING MULTICAST MTU:9100 Metric:1
+ RX packets:54071 errors:0 dropped:0 overruns:0 frame:0
+ TX packets:48515 errors:0 dropped:0 overruns:0 carrier:0
+ collisions:0 txqueuelen:1000
+ RX bytes:22009423 (20.9 MiB) TX bytes:25690847 (24.5 MiB)
+ Interrupt:16
Doing the same thing again but with QEmu being set to act as a "Q35
UEFI" system "ifconfig" gives me ...
- enp0s3 Link encap:Ethernet HWaddr CA:FE:15:60:0D:70
- inet addr:192.168.0.105 Bcast:192.168.0.1 Mask:255.255.255.0
- inet6 addr: fe80::b19a:de94:6e2c:37b7/64 Scope:Link
- UP BROADCAST RUNNING MULTICAST MTU:9100 Metric:1
- RX packets:27003 errors:0 dropped:0 overruns:0 frame:0
- TX packets:16171 errors:0 dropped:0 overruns:0 carrier:0
- collisions:0 txqueuelen:1000
- RX bytes:11000712 (10.2 MiB) TX bytes:8563615 (8.1 MiB)
- Interrupt:16
+ enp0s3 Link encap:Ethernet HWaddr CA:FE:15:60:0D:70
+ inet addr:192.168.0.105 Bcast:192.168.0.1 Mask:255.255.255.0
+ inet6 addr: fe80::b19a:de94:6e2c:37b7/64 Scope:Link
+ UP BROADCAST RUNNING MULTICAST MTU:9100 Metric:1
+ RX packets:27003 errors:0 dropped:0 overruns:0 frame:0
+ TX packets:16171 errors:0 dropped:0 overruns:0 carrier:0
+ collisions:0 txqueuelen:1000
+ RX bytes:11000712 (10.2 MiB) TX bytes:8563615 (8.1 MiB)
+ Interrupt:16
- The later one would be more like I what would expect as SystemD's
+ The later one would be more like what I would expect as SystemD's
documentation goes to great lengths to try and explain the new naming
convention for network interfaces.
This inconsistency could actually lead to further problems down the road
with other packages ... for example Samba. The default example config
reads "bind interfaces = 127.0.0.0/8 eth0" (commented out though) where
"eth0" is not really a good example default because with SystemD it no
longer exists (at least on a UEFI system - and I had that issue with
several friends already where I told them "uncomment 'bind interfaces'"
to have samba only bind/listen to the desired interfaces ... and then it
not working because there's no "eth0"). It might be better to determine
and append the lan/subnet post-install (i.e. 192.168.0.0/24) or settle
on a uniform device naming convention for the network interfaces.
The problem should be reproducible by simply booting a installation ISO
on a BIOS and UEFI system (or accordingly configured VM).
** Description changed:
Out of a discussion (with Stuart Langridge) about SystemD's new
interface naming convention I discovered the following inconsistency in
device naming on a BIOS vs a UEFI system...
Using QEmu, set to act as a "440FX BIOS" system, and booting up the
Ubuntu MATE 16.04.2 LTS ISO I get the following output from "ifconfig"
...
eth0 Link encap:Ethernet HWaddr CA:FE:15:60:0D:70
inet addr:192.168.0.105 Bcast:192.168.0.1 Mask:255.255.255.0
inet6 addr: fe80::b19a:de94:6e2c:37b7/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:9100 Metric:1
RX packets:54071 errors:0 dropped:0 overruns:0 frame:0
TX packets:48515 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:22009423 (20.9 MiB) TX bytes:25690847 (24.5 MiB)
Interrupt:16
Doing the same thing again but with QEmu being set to act as a "Q35
- UEFI" system "ifconfig" gives me ...
+ UEFI" system (using the OVMF firmware) "ifconfig" gives me ...
enp0s3 Link encap:Ethernet HWaddr CA:FE:15:60:0D:70
inet addr:192.168.0.105 Bcast:192.168.0.1 Mask:255.255.255.0
inet6 addr: fe80::b19a:de94:6e2c:37b7/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:9100 Metric:1
RX packets:27003 errors:0 dropped:0 overruns:0 frame:0
TX packets:16171 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:11000712 (10.2 MiB) TX bytes:8563615 (8.1 MiB)
Interrupt:16
+
+ NOTE: The same is true on my desktop system (UEFI capable), the network
+ interface is "enp0s5" not "eth0".
The later one would be more like what I would expect as SystemD's
documentation goes to great lengths to try and explain the new naming
convention for network interfaces.
This inconsistency could actually lead to further problems down the road
with other packages ... for example Samba. The default example config
reads "bind interfaces = 127.0.0.0/8 eth0" (commented out though) where
"eth0" is not really a good example default because with SystemD it no
longer exists (at least on a UEFI system - and I had that issue with
several friends already where I told them "uncomment 'bind interfaces'"
to have samba only bind/listen to the desired interfaces ... and then it
not working because there's no "eth0"). It might be better to determine
and append the lan/subnet post-install (i.e. 192.168.0.0/24) or settle
on a uniform device naming convention for the network interfaces.
The problem should be reproducible by simply booting a installation ISO
on a BIOS and UEFI system (or accordingly configured VM).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1695089
Title:
Network Interface names differ between BIOS / UEFI
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1695089/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
