diff options
author | Thomas Haller <thaller@redhat.com> | 2018-04-05 11:35:55 +0200 |
---|---|---|
committer | Thomas Haller <thaller@redhat.com> | 2018-04-06 18:36:57 +0200 |
commit | 27d600f18a20c8fc362c1db0e1ebd99d7096276c (patch) | |
tree | fd330fbdfe980c97daf36464cfe05a6a8714e458 | |
parent | 78d03833fcbfc33ab36e86a79f4f58480811ad8d (diff) | |
download | NetworkManager-27d600f18a20c8fc362c1db0e1ebd99d7096276c.tar.gz |
platform: refetch TUN link when no type-specific lnk data was received
Now that kernel supports providing information about tun/tap devices
via netlink, make use of it.
Also, enable the hack that:
- when we first see a link that has no lnk data, we refetch
it on the assumption, that kernel just didn't send it
the first time.
For old kernels that do not yet support tun properties on netlink,
this means that we will always refetch the link once, the first
time we see it. I think that is acceptable, and the more correct
behavior for newer kernels that do support it.
-rw-r--r-- | src/platform/nm-linux-platform.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/src/platform/nm-linux-platform.c b/src/platform/nm-linux-platform.c index 96d8367ecb..3c01d3d36e 100644 --- a/src/platform/nm-linux-platform.c +++ b/src/platform/nm-linux-platform.c @@ -3939,6 +3939,7 @@ cache_on_change (NMPlatform *platform, NM_LINK_TYPE_MACVLAN, NM_LINK_TYPE_MACVLAN, NM_LINK_TYPE_SIT, + NM_LINK_TYPE_TUN, NM_LINK_TYPE_VLAN, NM_LINK_TYPE_VXLAN)) { /* certain link-types also come with a IFLA_INFO_DATA/lnk_data. It may happen that |