TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to
[EMAIL PROTECTED]  Contact [EMAIL PROTECTED] for help with any problems!
----------------------------------------------------------------------------

Mike:

IPUnknownProtocol is NOT associated with a particular port, but is triggered
by the contents of the IP packet's NextHigherProtocol byte, which contains a
number identifying the Transport Layer protocol which should receive the
results of the IP layer processing.  There are 256 potential "next higher"
protocols, with RealSecure recognizing ONLY three, 1 (ICMP), 6 (TCP), and 17
(UDP).  There is an IPUnknownProtocol event "tuning parameter" available in
the policy editor.  There have been instances in which the GUI policy editor
fails to save changes in the IGNORE parameter.  If that happens, you can
open the policy file in question in NotePad, "find" the IPUnknownProtocol
section and the Ignore parameter and just type in the protocol number to be
ignored.  If you have several protocols to be ignored, separate the numbers
with commas.  Then save and apply the edited policy file.  But this process
should work in the RS 3.2+ policy editor without a problem.

NOW IF YOU'RE JUST INTERESTED IN "FILTERING" A PORT:  That's different from
the IPUnknownProtocol event.  Obviously you've tried a User-Defined Filter
against the port, but, as noted above, this won't have any effect on the
IPUnknownProtocol event.  You may also take advantage of the processing
sequence in Connect Events to monitor and respond a port's traffic without
throwing away the traffic.  However, if you are just looking to cut down on
the amount of traffic for a specific event, remember that you can set the
definition of an "event" in the event's Advanced area, where you can define
an event AND define the response of so-called "non-filtered" responses.  

For example, the default definition of an "event" in RealSecure is usually
traffic from an IP Socket set to another IP Socket set, where each item in
the complete quartet is significant.  To explain:  an HTTP-GET event is
defined as a source IP Address AND a source IP Port AND a destination IP
Address AND a destination IP Port.  So a second HTTP-GET from the same
source IP Address using a different port IS A SECOND EVENT and shows up
twice in the non-filtered responses (Alerts, LogDB, etc.)  Using the
Advanced button in the HTTP-GET event and defining an HTTP-GET as a source
IP Address AND a destination IP Address AND a destination IP Port (e.g. 80)
means that you will trigger ONE response when a source does an HTTP-GET and
subsequent HTTP-GETs from the same IP source will NOT trigger additional
Alerts/LogDB/etc.


James R Lindley
Senior Security Instructor
Internet Security Systems Inc
678-443-6323
An unquenchable thirst for Pierian water.
I don't make mistakes!  I self-generate learning opportunities!
PS: I always suggest an ISS Education class, where you will learn even more
about all ISS products.

-----Original Message-----
From: Fleck, Michael [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 13, 2000 10:59 AM
To: [EMAIL PROTECTED]
Subject: IPUnknown Protocol



TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to
[EMAIL PROTECTED]  Contact [EMAIL PROTECTED] for help with any
problems!
----------------------------------------------------------------------------

My logs are overrunning with IPUnknownProtocol events but I know what the
protocol is. It is an IP port used for a specific function. I have tried to
set filters on the Engine Profile to ignore it but that does not seem to
reduce the amount of reporting/logging the engine is performing. How do I
enable a filter for this IP port.

>       Michael Fleck 
> 



Reply via email to