NetworkManager/clients
Beniamino Galvani 87e79d214e
libnm-core: interpret ovs-patch.peer as an interface name
The 'peer' property of ovs-patch is inserted into the 'options' column
of the ovsdb 'Interface' table. The ovs-vswitchd.conf.db man page says
about it:

  options : peer: optional string
    The name of the Interface for the other side of the patch. The
    named Interface’s own peer option must specify this Interface’s
    name. That is, the two patch interfaces must have reversed name
    and peer values.

Therefore, it is wrong to validate the peer property as an IP address
and document it as such.

Backport: note that on nm-1-22, we have nm_utils_ifname_valid() function
for validating OVS interface names. We don't have that here, so we
re-implement the name validation differently.

Fixes: d4a7fe4679 ('libnm-core: add ovs-patch setting')
(cherry picked from commit beb1dba8c1)
(cherry picked from commit 5598c039e4)
(cherry picked from commit 9b82c62f33)
2020-09-04 16:38:15 +02:00
..
cli all: fix wrong "gs_free GError *" declarations 2019-12-16 17:46:59 +01:00
common libnm-core: interpret ovs-patch.peer as an interface name 2020-09-04 16:38:15 +02:00
tests clients/tests: fix expected client test output 2019-09-27 17:22:00 +02:00
tui tui: wifi: support WPA3-Personal (SAE) 2019-09-20 13:23:47 +02:00
meson.build build/meson: rename "nm_core_dep" to "libnm_core_dep" 2019-04-18 18:59:09 +02:00
nm-online.c all: drop emacs file variables from source files 2019-06-11 10:04:00 +02:00