[Snort-users] Allowing windows updates to pass through snort

Doug Olitsky

unread,

Feb 18, 2014, 11:30:55 AM2/18/14

to

OK, I'm a beginner at this and after months of trying to read and teach
myself I cry uncle...

I have Snort running on a pfSense gateway I built a year ago. For the
life of me I cannot figure out how to prevent windows updates from being
blocked. My lame solution is to disable Snort for updates and then
restart when done.

I tried setting IPS to Connectivity and even disabling it along w/ the
community rules to no avail.

Any guidance is appreciated

--
Regards;
Doug
=====================================================

------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________
Snort-users mailing list
Snort...@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://sourceforge.net/mailarchive/forum.php?forum_name=snort-users

Please visit http://blog.snort.org to stay current on all the latest Snort news!

Tony Reusser

unread,

Feb 18, 2014, 12:21:24 PM2/18/14

to

Follow-up...

For what it's worth...whatever you are using for your log analysis of the
SNORT alerts, I would think it should be relatively easy to find what rule
is being triggered by windows updates and either disable it, or add
exceptions for certain hosts.

-Tony

waldo kitty

unread,

Feb 18, 2014, 1:10:42 PM2/18/14

to

On 2/18/2014 11:30 AM, Doug Olitsky wrote:
> OK, I'm a beginner at this and after months of trying to read and teach
> myself I cry uncle...
>
> I have Snort running on a pfSense gateway I built a year ago. For the
> life of me I cannot figure out how to prevent windows updates from being
> blocked. My lame solution is to disable Snort for updates and then
> restart when done.

1. simply disable the specific rule(s) that are causing snort to alert on that
traffic.

*OR*

set those hosts as allowed for those sigs by using the threshold.conf file.

--
NOTE: No off-list assistance is given without prior approval.
Please keep mailing list traffic on the list unless
private contact is specifically requested and granted.

Tony Reusser

unread,

Feb 18, 2014, 12:10:38 PM2/18/14

to

Also, I think I mis-read your original post. Your SNORT isn't running ON a
Windows platform (wasn't familiar with pfsense until I looked it up)...But
rather configured "inline" in IPS mode. Can't help you there other than
recommended you use it strictly in "sniffing" mode as a IDS until you learn
to tweak the rules to your liking.

SNORT is merely a curiosity and an interesting analysis tool for me. I have
"better" products for IPS that are less quirky and easier to manage.

Hope you didn't take my original reply wrong.

Good luck.

-Tony

-----Original Message-----
From: Doug Olitsky [mailto:doug_o...@yahoo.com]
Sent: Tuesday, February 18, 2014 9:31 AM
To: snort...@lists.sourceforge.net
Subject: [Snort-users] Allowing windows updates to pass through snort

OK, I'm a beginner at this and after months of trying to read and teach
myself I cry uncle...

I have Snort running on a pfSense gateway I built a year ago. For the life
of me I cannot figure out how to prevent windows updates from being blocked.
My lame solution is to disable Snort for updates and then restart when done.

I tried setting IPS to Connectivity and even disabling it along w/ the
community rules to no avail.

Any guidance is appreciated

--
Regards;
Doug
=====================================================

----------------------------------------------------------------------------
--