-
-
Notifications
You must be signed in to change notification settings - Fork 360
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
[FEAT] Do not regenerate all peers when adding a new peer #297
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
Please elaborate further. The peer confs are not necessarily used for the server so they shouldn't cause startup issues. Are you making manual changes to the wg0.conf? |
I see, i was a bit too guick. I made a test environment and this is my wg0.conf with 1 peer:
And the conf for Test1:
But now, when i add an extra peer when recreating the wireguard container
The wg0.conf now looks like this, the ipv6 address is missing for the interface, the ip6tables settings are gone and the ipv6 allowed ip for Test1 is just a string in the config :
And the config for Test1 is also not valid anymore, in case peer Test1 needs to recreate the tunnel locally on that peer.
I hope this made things clear. |
We don't support manual edits to the |
This is a bit off topic, but I have to just toss this out... why in the world are you natting ipv6? the whole point of ipv6 is that with the, on average, 18quintillion ip addresses you get, you do not ever need to NAT. |
Is this a new feature request?
Wanted change
Maybe you can add a parameter, like REGENERATE_ALL true|false, so when you add one new peer on recreate the container it will only add the new peer or add the new peer and regenerate all the configs.
Reason for change
I made some ipv6 adjustments, and now when i add a new peer al the configs are regenerated and the start-up of the container will fail.
Cause some of the ipv6 address will remain in the config but not in a proper way.
Like
Address: 2a02:a44b:xxxx:1:1 remains as
2a02:a44b:xxxx:1:1
Proposed code change
No response
The text was updated successfully, but these errors were encountered: