[Snort-users] Snort rule firing on another port

Joel Esler jesler at ...1935...
Thu Dec 13 13:41:39 EST 2012

Are you using adaptive profiling or host individual specifications?
Joel Esler
Senior Research Engineer, VRT
OpenSource Community Manager

On Dec 13, 2012, at 1:27 PM, Anthony Rees <arees734 at ...11827...> wrote:

> Hi,
> Vrt have a rule 1:16606, it should fire on port 443 but its firing on 3801. there is one content match in the packet, but shouldnt it ignore the rule if the header does not meet the criteria??
> All aspects of the rule look good, just wondering why it doesn't ignore the packets as the rule header doesn't match.
> Thanks
> Sent from my iPhone
> ------------------------------------------------------------------------------
> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> Remotely access PCs and mobile devices and provide instant support
> Improve your efficiency, and focus on delivering more value-add services
> Discover what IT Professionals Know. Rescue delivers
> http://p.sf.net/sfu/logmein_12329d2d
> _______________________________________________
> Snort-users mailing list
> Snort-users at 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!

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.snort.org/pipermail/snort-users/attachments/20121213/c25d98d1/attachment.html>

More information about the Snort-users mailing list