-
-
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
[BUG] PEERS > 253 #300
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
The image currently supports a mask of We currently have no plans of changing that as we don't believe it is necessary for the use cases we support (non-commercial, homelab use). Feel free to let us know of a valid use case and we'll consider. Keep in mind that we don't plan to support commercial use cases. |
I see, just wanted to have it clarified. I did find a workaround by just creating multiple services, with different |
Is there an existing issue for this?
Current Behavior
From what I understand as of now, when the number of PEERS are > 253, it does generate configs for all the peers, but when I took a look at individual configs,
peer253
and beyond have the same Address under Interface.Expected Behavior
When the PEERS > 253, I would like to have the IP address to increase on the third octet, so in the case of
peer254
, it would haveas Address instead of keep producing 254.
Steps To Reproduce
docker-compose.yaml
being:docker-compse up -d wireguard
And checked
config/peer254/peer254.conf
Environment
CPU architecture
x86-64
Docker creation
Written in steps to reproduce
Container logs
The text was updated successfully, but these errors were encountered: