diff options
| author | Thomas Haller <thaller@redhat.com> | 2019-11-27 13:18:52 +0100 |
|---|---|---|
| committer | Thomas Haller <thaller@redhat.com> | 2019-11-28 00:11:15 +0100 |
| commit | b9f1beb06e624cc3d6bb0bb8723347392376e200 (patch) | |
| tree | 471b2a01fa03174c115f752d59e823130caf6d4f /NEWS | |
| parent | b8c00780085d56cfcd0b489653aef9b23938dffc (diff) | |
| download | NetworkManager-b9f1beb06e624cc3d6bb0bb8723347392376e200.tar.gz | |
all: add support for "scope" attribute for IPv4 routes
- systemd-networkd and initscripts both support it.
- it seems suggested to configure routes with scope "link" on AWS.
- the scope is only supported for IPv4 routes. Kernel ignores the
attribute for IPv6 routes.
- we don't support the aliases like "link" or "global". Instead
only the numeric value is supported. This is different from
systemd-networkd, which accepts names like "global" and "link",
but no numerical values. I think restricting ourself only to
the aliases unnecessarily limits what is possible on netlink.
The alternative would be to allow aliases and numbers both,
but that causes multiple ways to define something and has
thus downsides. So, only numeric values.
- when setting rtm_scope to RT_SCOPE_NOWHERE (0, the default), kernel
will coerce that to RT_SCOPE_LINK. This ambiguity of nowhere vs. link
is a problem, but we don't do anything about it.
- The other problem is, that when deleting a route with scope RT_SCOPE_NOWHERE,
this acts as a wild care and removes the first route that matches (given the
other route attributes). That means, NetworkManager has no meaningful
way to delete a route with scope zero, there is always the danger that
we might delete the wrong route. But this is nothing new to this
patch. The problem existed already previously, except that
NetworkManager could only add routes with scope nowhere (i.e. link).
Diffstat (limited to 'NEWS')
| -rw-r--r-- | NEWS | 1 |
1 files changed, 1 insertions, 0 deletions
@@ -25,6 +25,7 @@ USE AT YOUR OWN RISK. NOT RECOMMENDED FOR PRODUCTION USE! type instances would have been created by NMClient for a while now. * DHCP: switch "internal" DHCPv4 plugin from code based on systemd to use nettools' n-dhcp4 library. +* Add support for "scope" attribute for IPv4 routes. * libnm: heavily internal rework NMClient. This slims down libnm and makes the implementation more efficient. NMClient should work now well with a separate GMainContext. |