-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add AllowedIPs optional setting for peers #92
Comments
Note that i'm adding both subnets and a list of IPs (/32s), having them in a "template" or / and auto-completed from previous peers would be best i think. |
Tunnel all traffic for the public internet over WG (exclude any/all local network subnets) EDIT: CORRECTED 2021-11-22: For instance, as the WG-android app does - is a hell of a config to copy and paste each time, that should definitely be an option aswell while creating peers. EDIT: CORRECTED 2021-11-22: |
This is an unpleasant feature. This problem is solved by replacing the validators in the ipv4 field: In this class: |
Huh? The problem? It's not really a problem, more of an enhancement with more features (such as autocompletion of input subnets, common ones/previously used ones for instance).... ? But yeah - thanks for the input on where the placeholder comes from! I've also just updated the allowed ips above, we realized those before were actually wrong... :) |
Is your feature request related to a problem? Please describe.
I would like to add an optional field when adding peers - AllowedIPs configuration
Describe the solution you'd like
Would also be great if it was based upon templates/pre-existing/pre-used (autocomplete maybe??) values.
Describe alternatives you've considered
Currently I'm manually edit each peer-config, which unfortunately makes the pre-existing QR-code generator unusable.
Additional context
I'm not that great of a python developer, but i'll make an effort in modifying this myself later this week...
The text was updated successfully, but these errors were encountered: