diff options
| author | Thomas Haller <thaller@redhat.com> | 2020-04-25 07:46:56 +0200 |
|---|---|---|
| committer | Thomas Haller <thaller@redhat.com> | 2020-04-28 13:01:18 +0200 |
| commit | 9b295f0df56880be2677f18a21bc6b5c27c51dfc (patch) | |
| tree | ad4eece3a62bb21c7d23f35c5005be1838c58780 /man | |
| parent | e9ee4e39f199d4a69e2fc20f01e383ec73661018 (diff) | |
| download | NetworkManager-9b295f0df56880be2677f18a21bc6b5c27c51dfc.tar.gz | |
dhcp: make connection.mud-url configurable as global connection default
Conceptionally, the MUD URL really depends on the device, and not so
much the connection profile. That is, when you have a specific IoT
device, then this device probably should use the same MUD URL for all
profiles (at least by default).
We already have a mechanism for that: global connection defaults. Use
that. This allows a vendor drop pre-install a file
"/usr/lib/NetworkManager/conf.d/10-mud-url.conf" with
[connection-10-mud-url]
connection.mud-url=https://example.com
Note that we introduce the special "connection.mud-url" value "none", to
indicate not to use a MUD URL (but also not to consult the global connection
default).
Diffstat (limited to 'man')
| -rw-r--r-- | man/NetworkManager.conf.xml | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/man/NetworkManager.conf.xml b/man/NetworkManager.conf.xml index 6aa0398e64..76a535fb5d 100644 --- a/man/NetworkManager.conf.xml +++ b/man/NetworkManager.conf.xml @@ -679,6 +679,10 @@ ipv6.ip6-privacy=0 <term><varname>connection.autoconnect-slaves</varname></term> </varlistentry> <varlistentry> + <term><varname>connection.mud-url</varname></term> + <listitem><para>If unspecified, MUD URL defaults to <literal>"none"</literal>.</para></listitem> + </varlistentry> + <varlistentry> <term><varname>connection.lldp</varname></term> </varlistentry> <varlistentry> |