RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem: 

When configuring wireguard peers for wireguard connections, there seems to be difference in separators used for adding multiple IP-addresses to allowed-ips field between config-file and nmtui. 

As shown here in section 13.5/6i - https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9-beta/html/configuring_and_managing_networking/assembly_setting-up-a-wireguard-vpn_configuring-and-managing-networking#proc_configuring-a-wireguard-using-nmcli_assembly_setting-up-a-wireguard-vpn - when wireguard peers are added through editing "/etc/NetworkManager/system-connections/server-wg0.nmconnection", semicolon is used to separate different ip addresses in "allowed-ips" field. 

In contrary to config-file, nmtui only uses commas to separate ip addresses in wg-peer's allowed-ips field, using semicolon results in failure.


Version-Release number of selected component (if applicable):


How reproducible: always


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:



Additional info: Not sure if this inconsistency is intended (as commas might seem more user friendly), if yes, please feel free to close the bug.

Thomas, is this intentional? If yes, please close the bug.

NetworkManager's keyfiles use GKeyfile API for reading/writing the text file. That API supports to write/read string arrays, which it then happens to separate by ';'. The ';' separator comes from there.

There is no reason why nmtui needs to be consistent with that. If at all, it should be more flexible and allow any kinds of separators, like ' ', ',', ';'.

Also, if you enter invalid strings there, the UX is not good (you only see the failure much later when you try to save the profile).

nmtui should improve here. But not to be consistent with keyfile.

(In reply to Matej Berezny from comment #0)

> Additional info: Not sure if this inconsistency is intended (as commas might
> seem more user friendly), if yes, please feel free to close the bug.

So based on comment 3, we cannot accept commas in key files, therefore I close this BZ.