diff options
author | Thomas Haller <thaller@redhat.com> | 2020-09-14 15:40:08 +0200 |
---|---|---|
committer | Thomas Haller <thaller@redhat.com> | 2020-09-14 17:30:59 +0200 |
commit | 3338ea0530bc05b403049df6df8f246cb455b597 (patch) | |
tree | b2659f655999a9c8527e0c5bbf800030a2efc691 /linker-script-binary.ver | |
parent | 3fcfb53c4b8d9c8c84008a01d0cc8e7cd7eff2e8 (diff) | |
download | NetworkManager-th/device-track-shared-ips.tar.gz |
device: track used shared-ips via NMNetnsth/device-track-shared-ips
Note that when NetworkManager tries to allocate more than 256 networks,
then previously the allocation would fail. We no longer fail, but log an
error and reuse the last address (10.42.255.1/24).
It's simpler to have code that cannot fail, because it's often hard to
handle failure properly. Also, if the user would configure two shared
profiles that explicitly use the same subnet, we also wouldn't fail. Why
not? Is that not a problem as well? If it is not, there is no need to
fail in this case. If it is a problem, then it would be much more
important to handle this case otherwise -- since it's more likely to
activate two profiles that accidentally use the same subnet than
activating 257+ shared profiles.
Diffstat (limited to 'linker-script-binary.ver')
0 files changed, 0 insertions, 0 deletions