Re: f36 ifcfg sub-package

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

 



Barry writes:

On 11 May 2022, at 19:34, Tom Horsley <horsley1953@xxxxxxxxx> wrote:

After peering at "dnf search" results I finally found the actual
name of the sub-package:

NetworkManager-initscripts-ifcfg-rh-1:1.36.4-1.fc36.x86_64

Now I finally have all my complicated bridges and wot-not back and
network functioning as it did on f35.

I don't suppose there is an automated tool to convert complicated
ifcfg files to NetworkManager keyfiles is there?


Yes there is a tool. See this article for details.


<URL:https://fedoramagazine.org/converting-networkmanager-from-ifcfg-to- keyfiles/>https://fedoramagazine.org/converting-networkmanager-from-ifcfg-to- keyfiles/

That article says:

# Starting with Fedora Linux 36, the ifcfg support will no longer be present
# in new installations. If you’re still using ifcfg files, do not worry —
# the existing systems will keep it on upgrades. Nevertheless, you can still
# decide to uninstall it and carry your configuration over to keyfiles. Keep
# on reading to learn how.

However, Tom seems to be reporting that everything broke for him, until he hunted down the package and manually installed it.

Reading further into that article, I am informed about "nmcli connection migrate".

Checking my F35's man page, there's no mention of this option, so this appears to be new in F36.

So, the migration process appears to be:

1) Update F35 to F36

2) After a reboot things will be broken because ifcfg support is gone

3) Run "nmcli connection migrate" to restore network connectivity

Is this correct?

Many moons ago, before this was even recognizable in NM (IIRC), I managed to hack together a bridge for a qemu VM. It works, the guest seems to have no problem getting its IP address from my DHCP server. After reading that article:

$ nmcli -f TYPE,FILENAME,NAME conn
TYPE FILENAME NAME
bridge    /etc/sysconfig/network-scripts/ifcfg-vnet0                  Bridge vnet0
bridge    /run/NetworkManager/system-connections/virbr0.nmconnection  virbr0
ethernet  /etc/sysconfig/network-scripts/ifcfg-eth0                   System eth0
ethernet  /etc/sysconfig/network-scripts/ifcfg-eth1                   System eth1

So, what are the chances that my VM's network connectivity survives migration to F36?

It would be useful to have nmcli connection migrate functional in F35, to give me some kind of an advance warning…


Attachment: pgpZt2PRE1VOR.pgp
Description: PGP signature

_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux