diff options
author | Thomas Haller <thaller@redhat.com> | 2017-12-20 12:45:02 +0100 |
---|---|---|
committer | Thomas Haller <thaller@redhat.com> | 2017-12-20 13:48:13 +0100 |
commit | 4277bc0ee0479ad62369c3a261ea8d098e5e25ad (patch) | |
tree | 69318f522aafd2f42800f659e620de24aa8b95b2 /src/nm-manager.h | |
parent | 7deb3b4fb5bc7b71e66cd6c85694f218a01f2334 (diff) |
core: persist aspired default route-metric in device's state file
NMManager tries to assign unique route-metrics in an increasing manner
so that the device which activates first keeps to have the best routes.
This information is also persisted in the device's state file, however
we not only need to persist the effective route-metric which was
eventually chosen by NMManager, but also the aspired metric.
The reason is that when a metric is chosen for a device, the entire
range between aspired and effective route-metric is reserved for that
device. We must remember the entire range so that after restart the
entire range is still considered to be in use.
Fixes: 6a32c64d8fb2a9c1cfb78ab7e2f0bb3a269c81d7
Diffstat (limited to 'src/nm-manager.h')
-rw-r--r-- | src/nm-manager.h | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/src/nm-manager.h b/src/nm-manager.h index 34e868a9cb..1019022df4 100644 --- a/src/nm-manager.h +++ b/src/nm-manager.h @@ -119,9 +119,6 @@ guint32 nm_manager_device_route_metric_reserve (NMManager *self, int ifindex, NMDeviceType device_type); -guint32 nm_manager_device_route_metric_get (NMManager *self, - int ifindex); - void nm_manager_device_route_metric_clear (NMManager *self, int ifindex); |