support for AirVPN entry-IP 3 with Wireguard protocol #1890
Conversation
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
le0m
force-pushed
the
airvpn-wireguard-ipin3
branch
from
c27275d to
8e8fbb9
Compare
qdm12
force-pushed
the
master
branch
2 times, most recently
from
57a0645 to
059b128
Compare
le0m
force-pushed
the
airvpn-wireguard-ipin3
branch
from
8e8fbb9 to
3328e65
Compare
qdm12
force-pushed
the
master
branch
2 times, most recently
from
bba6a9f to
23b0320
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Add support for entry-IP 3 in AirVPN's Wireguard protocol. See specs, i incurred in this problem today.
AirVPN also supports Wireguard's standard port
51820with entry-IP 3, but this is my very first time writing GO code so i don't know how to conditionally add it to the validation here.Tested this locally with the updater CLI command, seems to work.