Unexpected NIC naming f23 firewall implications

[Jóhann B. Guðmundsson]

On 11/08/2015 07:29 PM, Richard W.M. Jones wrote:
> 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/

The p6p1 and em1 interface names come from ( Dells ) biosdevname not 
systemd and most likely the biosdevname component got removed on upgrade 
or superseded by other udev rules.

Arguably biosdevname component should have been obsoleted in F19 as a 
component and in Anaconda and Dracut when predictable network interface 
names got introduced with systemd in the distribution, to prevent these 
kind of surprises but here we are so "surprise" ...

JBG