-
Notifications
You must be signed in to change notification settings - Fork 150
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
rate limiting by IP address prefix #36
Comments
You could apply |
We are not against this evolution but currently I don't have the bandwidth to implement this... Cheers, |
@ammmir & @anacrolix: |
Looks about right. |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For IPv6, it doesn't make sense to rate limit individual /128 addresses since end hosts often get a huge prefix assigned to them, making it easy to bypass rate limits. Instead, how about adding a normalization prefix (default /32 for IPv4 and /128 IPv6 to keep existing functionality)?
It can be trivially accomplished by masking the desired number of bits for the prefix and using that as the IP key, for example:
IPv4:
192.0.2.123
with a/24
prefix: becomes192.0.2.0
IPv6:
2001:db8:cafe:1234:beef::fafa
with/48
prefix becomes2001:db8:cafe::
The text was updated successfully, but these errors were encountered: