Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Ban enhancements post CIDR addition #109

Open
GoogleCodeExporter opened this issue Aug 17, 2015 · 2 comments
Open

Ban enhancements post CIDR addition #109

GoogleCodeExporter opened this issue Aug 17, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link
Contributor 

In a conversation about the CIDR ban addition with Enari, the added option of 
adding bans in another form of say 172.16.0.10-40, or 172.16.0.0-172.31.255.255 
came up. They can be implemented in constant time (a <= ip <= b) so it wouldn't 
add much overhead to the existing ban system. Naturally they'd need a bit more 
checking when being added since they can't simply be parsed with inet_pton, but 
it might be helpful for some admins. Thoughts?

Original issue reported on code.google.com by [email protected] on 7 Sep 2011 at 1:07
@GoogleCodeExporter
Copy link
Contributor Author

Original comment by [email protected] on 7 Sep 2011 at 1:07

  • Changed state: New

@GoogleCodeExporter
Copy link
Contributor Author 

I agree! Also this should be added to the ban publish/subscribe

Original comment by [email protected] on 8 Sep 2011 at 3:29

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter