On Sun, Nov 08, 2015 at 08:36:57PM +0100, Reindl Harald wrote: > > > Am 08.11.2015 um 20:29 schrieb Richard W.M. Jones: > >On Sat, Nov 07, 2015 at 05:28:54PM +0000, Christopher wrote: > >>I recently updated my desktop to f23, and it went smoothly, for the most > >>part. However, it broke my mediatomb server because the NIC changed from > >>em1 to eno1. > >> > >>Is this something that was expected? It certainly surprised me. > > > >It happened to a bunch of servers when I updated them from F22 to F23. > >Their NICs changed from p6p1 -> enp3s0. It was annoying because I had > >to boot each one with a display and keyboard and change the network > >configuration by hand. > > > >"predictable, stable network interface names" > >https://wiki.freedesktop.org/www/Software/systemd/PredictableNetworkInterfaceNames/ > > that is simple to solve forever > > * add "net.ifnames=0 biosdevname=0" to your kernel params > * get rid of NetworkManager > * rename your ethernet-devices in the ifcfg-files based on the MAC > * survives yum-upgardes from Fedora 9 to Fedora 23 > * nobody needs NM and that other stuff on static configured servers > * frankly even with a DHCP wan-interface it works perfectly I agree, except it's not "simple" :-) Maybe giving permanent names to network interfaces (of our own choice or from a standard set) is something we should be able to choose at installation time? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-builder quickly builds VMs from scratch http://libguestfs.org/virt-builder.1.html -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
