-
-
Notifications
You must be signed in to change notification settings - Fork 183
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
IP Sorting range issues #99
Comments
Hi, sorry for the super late reply. I used the |
This issue has been solved in the next release ;) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe The Problem
When using the sort peers by Allowed IP it seems to fail to recognise early / single digit IPs as attached
instead of going 10.1.1.1 , 10.1.1.2 it seems to start at 10.1.1.10 then place 10.1.1.2 and the start of the .20 ranges
screenshots attached
To Reproduce
server with maybe 20+ like mine i have over 50 Peers, change to sort peers by Allowed IPs then review sequeance
OS Information:
Sample of your
.conf
file[Interface]
![AlllowedIP](https://user-images.githubusercontent.com/67483859/140646950-22e3604c-8b66-401c-912e-8df0af86de23.png)
![AllowedIPsorting](https://user-images.githubusercontent.com/67483859/140646952-2db3c068-a894-4233-92bd-d21d68c7578a.png)
PrivateKey = ABCDEFGHIJKLMNOP=
Address = 10.9.0.6/24
DNS = 8.8.8.8,8.8.4.4
[Peer]
PublicKey = ABCDEFGHIJKLMNOP=
AllowedIPs = 0.0.0.0/0, ::/0
Endpoint = MYSERVERIP:52080
PersistentKeepalive = 25
The text was updated successfully, but these errors were encountered: