View Single Post
Old 10-08-2012, 09:00 PM   #21
knc1
Helpdesk Junkie
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 6,819
Karma: 6314522
Join Date: Feb 2012
Device: Too many.
You want to block the "reserved purpose" ips in each range also, as in:
23.0.0.0-23.15.255.255
But the above entry, I can not find why I included it in my notes, it may have been a UK only something.

But, back on topic, For instance:
Code:
NetRange:       50.16.0.0 - 50.19.255.255
CIDR:           50.16.0.0/14
OriginAS:       
NetName:        AMAZON-EC2-8
NetHandle:      NET-50-16-0-0-1
Parent:         NET-50-0-0-0-0
NetType:        Direct Assignment
The tool twobob used to convert CIDR must have been "protecting" the top and bottom two "special purpose" IP addresses of each range.
I am going to walk out onto the thinest of the ice and say those are the: "broadcast" and "anycast" addresses for each range.

Last edited by knc1; 10-08-2012 at 09:09 PM.
knc1 is offline   Reply With Quote