Re: Unexpected NIC naming f23 firewall implications

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, Nov 8, 2015, 14:29 Richard W.M. Jones <rjones@xxxxxxxxxx> 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/

Rich.

It's a good policy and a good idea, but I thought it had already been done with the em1 naming. I guess i misunderstood when it'd be implemented.

-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux