Repository navigation
fix(wireguard): use first free name for new peer tunnels - #1926
Merged
Merged
Conversation
Tbaile
approved these changes
Oct 9, 2026
m-dilorenzi
force-pushed
the
issue_1915
branch
from
October 9, 2026 08:34
328f881 to
e7547e0
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR fixes the WireGuard tunnel import issue that occurs when a tunnel in the middle of the list is deleted and a new one is imported, resulting in the configs of existing tunnels being overwritten.
add-tunnelandimport-configurationnow take the first freewgNname, asadd-serveralready does. They returnno_free_instancewhen all names are in use (max 100 tunnels are allowed).get-instance-defaultssuggests the first free name and the first free port starting from 51820.wg10and above. Before, it also restartedwg1.Closes: #1915