Looks interesting, but it only takes a fairly short list of ASNs for a
prefix. For our big CIDR blocks, we have WAY too many ASNs to enter them
all, so it's pretty useless for me. I need to be able to enter at very
least a dozen ASes and I suspect may folks have a LOT more then that.
For now, I'll enter some shorter pieces from the block, but I'm most
concerned with the pieces that are not currently assigned, so are
available for hijack. I have added the larger, unassigned blocks. I'll
start adding assigned bits and pieces as well as unassigned pieces, but
being able to put all valid origin ASes in the list for the full blocks
would be a lot nicer.
Looks interesting, but it only takes a fairly short list of ASNs for a
prefix. For our big CIDR blocks, we have WAY too many ASNs to enter them
all, so it's pretty useless for me. I need to be able to enter at very
least a dozen ASes and I suspect may folks have a LOT more then that.
I am sure we can fix that, Thanks for the comment!
For now, I'll enter some shorter pieces from the block, but I'm most
concerned with the pieces that are not currently assigned, so are
available for hijack. I have added the larger, unassigned blocks. I'll
start adding assigned bits and pieces as well as unassigned pieces, but
being able to put all valid origin ASes in the list for the full blocks
would be a lot nicer.
It might be useful to have an option to generate an example alert mail for purposes of setting up necessary mail processing rules and that sort. Just a thought.
It might be useful to have an option to generate an example alert mail for purposes of setting up necessary mail processing rules and that sort. Just a thought.
Good point. Any suggestions from folks here on how they would like it to be built?
It might be useful to have an option to generate an example alert mail for purposes of setting up necessary mail processing rules and that sort. Just a thought.
Good point. Any suggestions from folks here on how they would like it to be built?
Could you throw up a page that tells a little about what logic is used, what you check, where you get feeds from and how often, so that people can evaluate the differences between checkmy.net, phas, IRU and MYAsn?
It might be useful to have an option to generate an example alert mail for purposes of setting up necessary mail processing rules and that sort. Just a thought.
Good point. Any suggestions from folks here on how they would like it to be built?
Could you throw up a page that tells a little about what logic is used, what you check, where you get feeds from and how often, so that people can evaluate the differences between checkmy.net, phas, IRU and MYAsn?
--Heather
I don't see why not. But whilw we take this very seriously and so release only when a phase is done, it is a free-time based project. Therefore, while we will definitely do so... I can't commit it will be very soon.
Much like other coders, while we appreciate documentation.. being very busy theorizing on what we already did will take some motivational coffee or a free evening. Comparing ourselves to other services... well, maybe some magazine will run a comperative testing.
Ah, both reasons really; setup mail flow rules, verify mail delivery, and create appropriate whitelist entries if need be to make sure that notifications tend not to mysteriously vanish. All general things that I like to do for any new mail-based monitoring system.
Looks interesting, but it only takes a fairly short list of ASNs for a
prefix. For our big CIDR blocks, we have WAY too many ASNs to enter them
all, so it's pretty useless for me. I need to be able to enter at very
least a dozen ASes and I suspect may folks have a LOT more then that.
We made many fixes over the last few days, as well as added a few more feeds. Any volunteers to give us more feeds?
One of the fixes is that you can add many more ASs now, which should resolve your previous issues.
Please let us know if you find any other problems or think of any suggestions, big and small.
