Bug #11323
Removing a WireGuard tunnel can cause others to be renumbered
Start date:
01/27/2021
Due date:
% Done:
100%
Estimated time:
Affected Version:
2.5.0
Affected Architecture:
Description
- Configure two WireGuard tunnels, wg0 and wg1
- Delete wg0
- Tunnel list shows only wg1
- Edit/Save wg1
- Tunnel wg1 has been changed to wg0
- Operating system has the same settings on wg0 and wg1
Once created the name should be static, never change. Otherwise it could cause problems with interface assignments.
Associated revisions
History
#1
Updated by Jim Pingle about 1 month ago
- Status changed from New to In Progress
#2
Updated by Jim Pingle about 1 month ago
- Status changed from In Progress to Feedback
- % Done changed from 0 to 100
Applied in changeset 0c68239a28d3e7a2ee3b58e60b0dd0e0081d7731.
#3
Updated by Marcos Mendoza about 1 month ago
- Status changed from Feedback to Resolved
Tested on Jan 29 build. Looks good.
Fix WireGuard interface name assignment. Fixes #11323
Only set the name when it's empty/unset (e.g. when first created),
automatically determine the next available wg interface number.