• Request Invite
Blog Search
Blog Archives
Categories
Blog Latest Comments
excellent news. thanks!
by cameron on Monday, May 14, 2012
Hi cameron - haven't forgotten about this and we believe this makes sense to expose but I can't commit to a timeframe ju...
by Kevin Fielding on Monday, May 14, 2012
any updates on this? it would allow us to fully integrate our two systems to offer a complete solution to our clients &...
by cameron on Thursday, May 10, 2012
yup that way we can integrate it with our registration program so new users don't have 2 different passwords
by cameron on Friday, April 27, 2012
Hey Cameron - to clarify are you asking for a parameter to supply a user's registration password at time of the create A...
by Kevin Fielding on Friday, April 27, 2012
Page  of  Total Items: 268

firstprevnextlast

Feature Requests
Do you have some feedback for us? If there is any components of our software you would like to see added or changed feel free to post your thoughts here. We'd encourage you to be as clear as possible about why you like or don't like certain features so that other clients can weigh in with their thoughts as well. Also feel free to suggest that we actually remove certain components of the system that just aren't getting enough traction for you. All feedback is welcome!
View All Posts
gadgeteer
Allow and use CIDR ranges for banned ips...
Posted by gadgeteer
Thursday, August 04, 2011
Comments (4)
This admin dashboard for maintaing a list of banned IPs, only lists individual IPs.

/admin/app/remoteip/managebannedips.aspx

It would be much more affective to also support and allow CIDR notation for ranges of IPs to be blocked.
 
Categories:  Pending Review
  • Visit gadgeteer's profile
    gadgeteer: One example of a problem I'm trying to deal with.

    There is a company that's a "infrastructure as a service" company. They have a large range of IPs that are assigned to their hosting facilities... so that address range should never be posting comments to our site. Yet I'm seeing spam comments coming from that address range (173.192.0.0/15.)

    The IPs of comments that have been reported are scattered over that range. That's only the comments that have been directly reported and I've been able to track down an IP Address, there are bound to be more I've missed. (by the way, yhank you for including the IP Address in the results returned by the getComments API call, I've been fighting this issue for months with no clear solution.)

    There are also other webhosting/colo facilities where I'm seeing the same behavior.

    Being able to just add the CIDR range for the colo/webhost would go a long way to reducing my workload in battling comment spam.
     
  • Visit Kevin Fielding's profile
    Kevin Fielding: Thanks for sharing gadgeteer. We'll review this request for future product road-mapping. For now I'm going to mark this as pending review.

    - Kevin
     
  • Visit gadgeteer's profile
    gadgeteer: If this feature can't be implemented anytime soon is there a way to get bulk loaded ip addresses? I'd really like to stem the spam comments from webhosting facilities... unfortunately it's way to easy to move your server to a new IP Address as the vendors and and I'm in a constantly losing race to keep the spammers out.
     
  • Visit Kevin Fielding's profile
    Kevin Fielding: Hi gadgeteer, currently that option does not exist. One option that we may be able to implement sooner is exposing ban by IP via an API. That would allow you to write a script to ban all IPs in a given range. Would that work?