wireguard: add policy based routes to allowedIPs #607
Closed
Conversation
This file contains 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
Signed-off-by: Artem Glazychev <artem.glazychev@xored.com>
|
I'm not sure this solves the problem. The real issue is that with PBR, we don't know apriori what IPs will come over the interface and have their src IPs converted to dst IPs for return traffic. What would the side effects be if we just set AllowedIPs to 0.0.0.0/0 and ::00/128 ? |
|
@edwarnicke I don't see any problems with 0.0.0.0/0 and ::00/128.. |
|
Closed to opt for - #618 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Issue: networkservicemesh/deployments-k8s#6488
Signed-off-by: Artem Glazychev artem.glazychev@xored.com