Beniamino Galvani 9b82c62f33 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. Fixes: d4a7fe4679 ('libnm-core: add ovs-patch setting') (cherry picked from commit beb1dba8c1) (cherry picked from commit 5598c039e4)		2020-06-11 13:27:57 +02:00
..
cli	cli: unref main loop after destroying NMClient instance	2020-05-12 23:05:46 +02:00
cloud-setup	all: remove wrong CURL option initialization	2020-02-03 15:31:18 +01:00
common	libnm-core: interpret ovs-patch.peer as an interface name	2020-06-11 13:27:57 +02:00
tests	libnm,cli,ifcfg-rh: add ipv6.ra-timeout configuration option	2020-02-17 15:06:10 +01:00
tui	all: use nm_utils_ifname_valid_kernel() instead of nm_utils_is_valid_iface_name()	2020-02-17 17:28:14 +01:00
meson.build	cloud-setup: add tool for automatic IP configuration in cloud	2019-11-28 19:52:18 +01:00
nm-online.c	all: manually drop code comments with file description	2019-10-01 07:50:52 +02:00