3:53 a.m.
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_...).
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
6:11 a.m.
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 <pboy(a)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_...).
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(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)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
6:18 a.m.
New subject: Fedora 33 network configuration (ifcfg*) migration guide
available?
On Wednesday, 27 January 2021 at 13:11, Arthur G wrote:
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.
You can use crudini to manage .ini files. Works quite well. There's also
nmcli...
Regards,
Dominik
--
Fedora https://getfedora.org | RPM Fusion http://rpmfusion.org
There should be a science of discontent. People need hard times and
oppression to develop psychic muscles.
-- from "Collected Sayings of Muad'Dib" by the Princess Irulan
10:54 a.m.
New subject: Fedora 33 network configuration (ifcfg*) migration guide
available?
Am 27.01.2021 um 13:18 schrieb Dominik 'Rathann' Mierzejewski
<dominik(a)greysector.net>:
On Wednesday, 27 January 2021 at 13:11, Arthur G wrote:
> 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.
You can use crudini to manage .ini files. Works quite well. There's also
nmcli...
Did not know that. Very convenient indeed for ini files. Thanks
10:56 a.m.
On Sun, Jan 31, 2021 at 11:55 AM Peter Boy <pboy(a)uni-bremen.de> wrote:
> Am 27.01.2021 um 13:18 schrieb Dominik 'Rathann' Mierzejewski
<dominik(a)greysector.net>:
>
> On Wednesday, 27 January 2021 at 13:11, Arthur G wrote:
>> 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.
>
> You can use crudini to manage .ini files. Works quite well. There's also
> nmcli...
Did not know that. Very convenient indeed for ini files. Thanks
It's not INI either, it's GNOME GVariant file format:
https://developer.gnome.org/glib/stable/gvariant-text.html
It's *similar* to INI, but has slightly different rules.
--
真実はいつも一つ！/ Always, there's only one truth!
6:22 a.m.
Thanks also for the nmcli tip, it got me out of a pickle today with RedHat
8. From what I've experienced so far it's well implemented.
On Mon, 1 Feb 2021 at 08:42, Kevin Kofler via devel <
devel(a)lists.fedoraproject.org> wrote:
Dominik 'Rathann' Mierzejewski wrote:
> You can use crudini to manage .ini files. Works quite well. There's also
> nmcli...
You might also be able to work with kreadconfig5 and kwriteconfig5 from
kf5-
kconfig-core, though I have never tried those on NM configs.
Kevin Kofler
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)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
6:56 a.m.
New subject: Fedora 33 network configuration (ifcfg*) migration guide
available?
On 1/25/21 5:53 AM, Peter Boy 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_...).
Is there a kind of „mapping“ ifcfg-* —> *-nmconnection. ?
You can "migrate" using nmcli:
Save the output of `nmcli connection show <your_connection_name>`, then
create a new empty one a do a diff of the new `nmcli connection show
<your_connection_name>` with the old one. Set set the differences on the
new connection with `nmcli connection modify ...`
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(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)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
10:53 a.m.
New subject: Fedora 33 network configuration (ifcfg*) migration guide
available?
Am 27.01.2021 um 13:56 schrieb Robert Marcano via devel
<devel(a)lists.fedoraproject.org>:
On 1/25/21 5:53 AM, Peter Boy 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_...).
> Is there a kind of „mapping“ ifcfg-* —> *-nmconnection. ?
You can "migrate" using nmcli:
Save the output of `nmcli connection show <your_connection_name>`, then create a
new empty one a do a diff of the new `nmcli connection show <your_connection_name>`
with the old one. Set set the differences on the new connection with `nmcli connection
modify ...`
Thanks, it worked. Saves the effort of searching for the correct syntax for each
parameter. Very nice.
1:24 a.m.
New subject: Fedora 33 network configuration (ifcfg*) migration guide
available?
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_...).
Is there a kind of „mapping“ ifcfg-* —> *-nmconnection. ?
Currently, the easiest way I can find is to to use
`nmcli clone --temporary` before the official migration tool
mentioned in [1] gets released. For example,
`nmcli c clone --temporary bond-mybond0 bond-mybond1` would clone
/etc/sysconfig/network-scripts/ifcfg-bond-mybond0 to
/run/NetworkManager/system-connections/bond-mybond1.nmconnection.
[1]
https://blogs.gnome.org/thaller/2021/02/02/initscripts-ifcfg-rh-format-in...
--
Best regards,
Coiby
935
days inactive
1180
days old
9 comments
7 participants
participants (7)
-
Arthur G -
Coiby Xu -
Dominik 'Rathann' Mierzejewski -
Kevin Kofler -
Neal Gompa -
Peter Boy -
Robert Marcano