Thomas Haller 55ae69233d all: add connection.multi-connect property for wildcard profiles ... Add a new option that allows to activate a profile multiple times (at the same time). Previoulsy, all profiles were implicitly NM_SETTING_CONNECTION_MULTI_CONNECT_SINGLE, meaning, that activating a profile that is already active will deactivate it first. This will make more sense, as we also add more match-options how profiles can be restricted to particular devices. We already have connection.type, connection.interface-name, and (ethernet|wifi).mac-address to restrict a profile to particular devices. For example, it is however not possible to specify a wildcard like "eth*" to match a profile to a set of devices by interface-name. That is another missing feature, and once we extend the matching capabilities, it makes more sense to activate a profile multiple times. See also https://bugzilla.redhat.com/show_bug.cgi?id=997998, which previously changed that a connection is restricted to a single activation at a time. This work relaxes that again. This only adds the new property, it is not used nor implemented yet. https://bugzilla.redhat.com/show_bug.cgi?id=1555012		2018-08-08 11:24:29 +02:00
..
terminal-colors.d	clients/tests: add tests for coloring	2018-06-26 11:32:39 +02:00
test-client.check-on-disk	all: add connection.multi-connect property for wildcard profiles	2018-08-08 11:24:29 +02:00
test-client.py	cli/tests: cache UUID for test replacement in stdout	2018-07-25 17:08:37 +02:00