Too bad NetworkManager persists with the old MS-DOS "INI" file format for it's configuration files. At least network-scripts was bash script friendly.
On Mon, 25 Jan 2021 at 20:53, Peter Boy <p...@uni-bremen.de> wrote: > With Fedora 33 network configuration is by default persisted in > /etc/NetworkManager/system-connections/*.nmconnection files. The old > /etc/sysconfig/network-scripts/ifcfg* files are „legacy“. They are still > being processed for the time being, but obviously it is time to migrate. > (cf > https://fedoraproject.org/wiki/Changes/NetworkManager_keyfile_instead_of_ifcfg_rh). > > > > Is there a kind of „mapping“ ifcfg-* —> *-nmconnection. ? > > > Most items are simple to migrate, but servers in particular sometimes have > unusual configurations, e.g. > > - for p2p Connections: SCOPE="peer xxx.yyy.zzz.aaa" > - and corresponding a lot of (ADDRESSx / NETMASKx / GATEWAYx ) entries in > route-{ifname} file > > How do I handle that kind of config items in *.nmconnection ? The "search > engine I trust" couldn't answer that for me (or I couldn’t ask the right > question). > > > > Thanks > Peter > > > _______________________________________________ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > 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/devel@lists.fedoraproject.org >
_______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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/devel@lists.fedoraproject.org
