How do I Report a Network Device Naming Bug

What was the device name earlier, and what is it now?
Probably https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/

On 05/13/16 01:37, Manfred Hampl wrote:
> Your question #293649 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/293649
>
> Status: Open => Answered
>
> Manfred Hampl proposed the following answer:
> What was the device name earlier, and what is it now?
> Probably https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
>

=== 14.04 ===
 > ifconfig -a
eth0 Link encap:Ethernet HWaddr 54:04:a6:17:f9:03
           inet addr:192.168.2.3 Bcast:192.168.2.255 Mask:255.255.255.0
           inet6 addr: fe80::5604:a6ff:fe17:f903/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
           RX packets:1347 errors:0 dropped:0 overruns:0 frame:0
           TX packets:1390 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:547874 (547.8 KB) TX bytes:199330 (199.3 KB)
           Interrupt:18 Memory:fbf00000-fbf20000

=== 16.04 -===
eno1 Link encap:Ethernet HWaddr 54:04:a6:17:f9:03
           inet addr:192.168.2.3 Bcast:192.168.2.255 Mask:255.255.255.0
           inet6 addr: fe80::db2f:510:22da:8659/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
           RX packets:24 errors:0 dropped:0 overruns:0 frame:0
           TX packets:67 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:4219 (4.2 KB) TX bytes:8311 (8.3 KB)
           Interrupt:18 Memory:fbf00000-fbf20000

Tom Dean

Try adding net.ifnames=0 to the boot command line, and you should have the old behavior.

On 05/13/16 01:37, Manfred Hampl wrote:
> Your question #293649 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/293649
>
> Status: Open => Answered
>
> Manfred Hampl proposed the following answer:
> What was the device name earlier, and what is it now?
> Probably https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
>

Interesting reading. This fixed a problem that does not exist on the
vast majority of systems!

Quote:

Does this have any drawbacks? Yes, it does. Previously it was
practically guaranteed that hosts equipped with a single ethernet card
only had a single "eth0" interface. With this new scheme in place, an
administrator now has to check first what the local interface name is
before he can invoke commands on it where previously he had a good
chance that "eth0" was the right name.

On 05/13/16 01:52, Manfred Hampl wrote:
> Your question #293649 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/293649
>
> Status: Open => Answered
>
> Manfred Hampl proposed the following answer:
> Try adding net.ifnames=0 to the boot command line, and you should have
> the old behavior.
>
This is not portable. I have to do this on every system, every time I
do an install!!!

If you use wicd instead of network manager, you can state the interface name manually