Unexpected NIC naming f23 firewall implications

Harald Hoyer harald.hoyer at gmail.com
Mon Nov 9 15:55:40 UTC 2015


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/
> 
> Rich.
> 

em* and p?p? come from biosdevname, which should not be used and is deprecated.


More information about the devel mailing list