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.

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

Tracker: review Smartbot filter for Live/Bing #1948

Closed
robocoder opened this issue Jan 5, 2011 · 3 comments
Closed

Tracker: review Smartbot filter for Live/Bing #1948

robocoder opened this issue Jan 5, 2011 · 3 comments
Labels
Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.
Milestone

Comments

@robocoder
Copy link
Contributor

In [3155], we added a filter based on the User-Agent.

However, BadBehaviour continues to release updates based on IP ranges (using CIDR notation), i.e.,

  • 207.46.0.0/16
  • 65.52.0.0/14
  • 207.68.128.0/18
  • 207.68.192.0/20
  • 64.4.0.0/18
  • 157.54.0.0/15
  • 157.60.0.0/16
  • 157.56.0.0/14

We need to verify that our filter still works.

@mattab
Copy link
Member

mattab commented Apr 28, 2011

Maybe, this is a quick fix now that CIDR notation is supported? or maybe we don't really care since it is not an issue and maybe we should not trust badbehavior db anyway!

@robocoder
Copy link
Contributor Author

before adding any of the ip ranges used by badbehavior, we'll verify the netblock belongs to Google/Bing/etc

@robocoder
Copy link
Contributor Author

(In [4784]) fixes #1948 - confirmed these are Microsoft assigned netblocks; should we incubate the BotTracker in #2391 to takeover the smartbot filtering?

@robocoder robocoder added this to the 1.5 - Piwik 1.5 milestone Jul 8, 2014
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.
Projects
None yet
Development

No branches or pull requests

2 participants