Home > Uncategorized > Windows: You can’t, realistically, use an IPSec Policy to Filter Large Amounts of IPs.

Windows: You can’t, realistically, use an IPSec Policy to Filter Large Amounts of IPs.

Everything below finally finished, or I guess most, and I had 75,118 ranges added to a filterlist. I proceeded down my theory only to find that, when the policy was assigned, it spawned two svchost processes that took up about 50% of my CPU processing. I believe that it was loading the list, which probably would’ve taken another three days, and not actively blocking IPs. This proved this method of IP blocking unrealistic in practice.
Even though I realize that IPSec isn’t meant for this exactly, I am disappointed with Microsoft on this one. In my opinion, if there is an option to use Microsoft software in place of competition, especially at this level, there is no excuse for it not to work.

For now, everyone will have to wait for Bluetack to write a Vista compatible driver for Protowall.
reg file containing the filterlist, you must change the GUID

Advertisements
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: