| United States-English |
|
|
|
![]() |
HP-UX IPFilter Version A.03.05.12 Administrator's Guide: HP-UX 11.0, HP-UX 11i version 1,HP-UX 11i version 2 > Chapter 5 IPFilter
UtilitiesThe ipmon Utility |
|
Use the ipmon utility to monitor IPFilter while it is in use. You can use ipmon to watch the packet log, as created with the log keyword in the IPFilter rules. ipmon can also monitor the state log, the NAT log, or any combination of these three. You can run ipmon in the foreground or as a daemon that logs to syslog or a file. -a Opens and reads data from all available log files. Equivalent to -o NSI. -o [NSI] Specifies which log file to read data from.
-A Logs the summary records created for DCA logging. -r Prints the summary records to the summary log file and clears the block count for each limit entry. -F Flushes the packet log buffer. Output displays the number of bytes flushed. -n Maps IP addresses and port numbers to host names and services wherever possible. For a complete list of ipmon options and their uses, refer to the ipmon manpage. To view the state table as it updates, use the ipmon -o S command. Example:
A state entry for an external DNS request to the nameserver is displayed by ipmon. Two xntp pings to well-known time servers and a short outbound SSH connection are also displayed. You can also use ipmon to display packets that have been logged. To view the IPFilter packet log, use the ipmon -o I command. Example:
The fields in this output are as follows:
Run the ipfstat -in command to determine which rule caused the problem. In this example, you would use this command to look at rule 2 in rule group 0. Occasionally, a packet that was part of a state connection might appear in the ipmon -o I log. This can happen if a packet with the same sequence number as another packet is processed by IPFilter. A state packet might also be logged by the regular IPFilter log if it is the last packet in a stateful connection, and arrives after the state has been torn down by IPFilter. Example:
This is a ICMP router discovery broadcast. It is indicated by the ICMP type 9/0. DCA logging creates a new device file. The log alerts records go to /dev/ipl and the summary records are logged to /dev/iplimit. To log the summary records, use ipmon with the -A option. Using ipmon -A prints a summary log for a limit entry before the entry being removed from the limit table. Example: ipmon -A /dev/iplimit > $LOGDIR/limit_summary.log & You can use ipmon -r to print the summary records to the log file for all existing limit entries that are active. For example, you have the following rule configured: pass in log limit quick proto tcp from IP1 to Server keep limit 10 If IP1 creates 70 connections, then 10 connections are let through and remaining 60 are blocked, which is the block count. When ipmon -r is called, a summary record is logged to the summary log records and the block count is set to 0. This is useful in a case where IP1 created many connections and has a large block count, but subsequently has connections that are within the connection limit. ipmon -r works only on active limit entries. If there are no limit entries, ipmon -r does not log any Summary Log records. Summary logs are printed only for those limit entries which have a non-zero connection exceeded counter. For cumulative limits, this option is the only way to obtain summary logs. |
||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||