You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Well 1.2.3.4/30? From .4 to .7. (Not caring about network and broadcast address).
Maxmind use CIDR like this. If you then want network ranges, then you can convert with their tool.
while it takes up more space, it is a consistent 2 variables, rather than breaking up a range into potentially more than 2 cidrs. but i do think the format of choice should be consistent.
Activity
ipapi-is commentedon Sep 16, 2023
Hey,
Will be done in the next release.
What format do you suggest?
benoitjpnet commentedon Sep 16, 2023
ipapi-is commentedon Sep 17, 2023
CIDR doesn't work for all networks.
How would you represent the network
1.2.3.4 - 1.2.3.7 in CIDR format?
Kind regards, Nikolai
benoitjpnet commentedon Sep 19, 2023
Well
1.2.3.4/30? From .4 to .7. (Not caring about network and broadcast address).Maxmind use CIDR like this. If you then want network ranges, then you can convert with their tool.
e.g:

ipapi-is commentedon Sep 21, 2023
You are correct.
How do you represent 1.2.3.1 - 1.2.3.7 in CIDR?
Not possible with one CIDR address, you have to provide 3 CIDR ranges:
Conclusion:
I will probably use the following format to represent IP ranges (Using integers):
Alternative, I can use the following format:
The problem with both of those formats is that they need considerably more space than CIDR format.
acidvegas commentedon Oct 4, 2023
while it takes up more space, it is a consistent 2 variables, rather than breaking up a range into potentially more than 2 cidrs. but i do think the format of choice should be consistent.