RE: New IP Range for AIM_SERVERS

["Chris Harrington" <charrington () nitrosecurity com>]

 On Thu, Jan 13, 2005 at 01:39:55PM -0600, Frank Knobbe wrote:
> > Given AOL owns 205.188.0.0/16, perhaps the whole range should be 
> > included.
>
> Incorrect.
>
> Many of those addresses are not AIM servers.
>
> Brian

But they are registered to AOL and _could_ be used as AIM servers. The
performance decrease for changing the AIM_SERVER variable to the 2 Class B's
was not even noticeable on my test systems. I would rather so this than have
to add a new class C every time someone happens to notice a new rang is in
use. Any other reason why this should not be changed? Worst case scenario is
Snort is watching address ranges that may never have AIM servers. 

--Chris




-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Snort-users mailing list
Snort-users () lists sourceforge net
Go to this URL to change user options or unsubscribe:
https://lists.sourceforge.net/lists/listinfo/snort-users
Snort-users list archive:
http://www.geocrawler.com/redir-sf.php3?list=snort-users