fix Allowed IPs validation & normalize Allowed IPs for routing configuration - #1123
Merged
Conversation
jakub-tldr
requested changes
Aug 28, 2026
moubctez
reviewed
Aug 28, 2026
moubctez
reviewed
Aug 28, 2026
t-aleksander
previously approved these changes
Sep 1, 2026
moubctez
reviewed
Sep 1, 2026
jakub-tldr
approved these changes
Sep 1, 2026
moubctez
approved these changes
Sep 1, 2026
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
4 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.
Allow bare IP addresses in tunnel configuration, they are already handled by the backend by adding the correct mask (/32 or /128).
Also strip host bits from Allowed IPs before configuring routing to avoid unnecessary interface configuration errors.
A full fix requires an update in wireguard-rs: DefGuard/wireguard-rs#140
Closes #1084