diff options
| author | Adrian Freihofer <adrian.freihofer@siemens.com> | 2022-04-08 13:11:56 +0200 |
|---|---|---|
| committer | Thomas Haller <thaller@redhat.com> | 2022-05-27 08:24:28 +0200 |
| commit | cbde63a493a686f39abd03fab6231fe7de365d38 (patch) | |
| tree | 2c956bcce0b2fa183f1dd19595662cdb7c84ab38 /man | |
| parent | 7d8b749293d1a9dde70580dd337a6b0bc0ac21f1 (diff) | |
| download | NetworkManager-cbde63a493a686f39abd03fab6231fe7de365d38.tar.gz | |
settings: add ipv4.link-local flag
Introduction of a new setting ipv4.link-local, which enables
link-local IP addresses concurrently with other IP address assignment
implementations such as dhcp or manually.
No way is implemented to obtain a link-local address as a fallback when
dhcp does not respond (as dhcpd does, for example). This could be be
added later.
To maintain backward compatibility with ipv4.method ipv4.link-local has
lower priority than ipv4.method. This results in:
* method=link-local overrules link-local=disabled
* method=disabled overrules link-local=enabled
Furthermore, link-local=auto means that method defines whether
link-local is enabled or disabled:
* method=link-local --> link-local=enabled
* else --> link-local=disabled
The upside is, that this implementation requires no normalization.
Normalization is confusing to implement, because to get it really
right, we probably should support normalizing link-local based on
method, but also vice versa. And since the method affects how other
properties validate/normalize, it's hard to normalize that one, so that
the result makes sense. Normalization is also often not great to the
user, because it basically means to modify the profile based on other
settings.
The downside is that the auto flag becomes API and exists because
we need backward compatibility with ipv4.method.
We would never add this flag, if we would redesign "ipv4.method"
(by replacing by per-method-specific settings).
Defining a default setting for ipv4.link-local in the global
configuration is also supported.
The default setting for the new property can be "default", since old
users upgrading to a new version that supports ipv4.link-local will not
have configured the global default in NetworkManager.conf. Therefore,
they will always use the expected "auto" default unless they change
their configuration.
Co-Authored-By: Thomas Haller <thaller@redhat.com>
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 18b25d9370..c2da67fe2b 100644 --- a/man/NetworkManager.conf.xml +++ b/man/NetworkManager.conf.xml @@ -923,6 +923,10 @@ ipv6.ip6-privacy=0 <term><varname>ipv4.required-timeout</varname></term> </varlistentry> <varlistentry> + <term><varname>ipv4.link-local</varname></term> + <listitem><para>If left unspecified, fallback to "auto" which makes it dependent on "ipv4.method" setting.</para></listitem> + </varlistentry> + <varlistentry> <term><varname>ipv4.route-metric</varname></term> </varlistentry> <varlistentry> |