Message Board

Newbie/Basic Questions

Older Posts ]   [ Newer Posts ]
 AS Number IP Tracking Algorithm Fail?
Author: C.Rosevear   (30 Sep 10 10:38am)
So, I just set-up IP tracking based on my AS number... and it has selected a block that is next to ours but not ours in addition to our blocks... and from our blocks it has chosen both the full block and a subset of that.

As for the full block (/21) and the subnet (/22), that is probably fine...

But I certainly have no interest in monitoring this adjoining block that is not ours.

I looked in whois and in various bgp looking-glasses and I don't know why this adjoining block would be identified as part of our AS.

I would just use one of the other address specification methods but there doesn't seem to be one for "Multiple CIDR blocks"... which, by the way, would be extremely useful because some office networks have lots of little /28, /27 netblocks around the world and it would be great to enter all of those in one place etc.

Not sure if someone wants to contact me off-list perhaps about what I am seeing in regard to the adjoining netblock that is not ours shwing-up under our AS, etc... perhaps I will run-into a feature request section for the "Multiple CIDR blocks" address entry method. I just signed up less than an hour ago but the adjoining netblock issue is definitely something I can't seem to tweak.



do not follow this link

Privacy Policy | Terms of Use | About Project Honey Pot | FAQ | Cloudflare Site Protection | Contact Us

Copyright © 2004–25, Unspam Technologies, Inc. All rights reserved.

contact | wiki | email