HP-UX IPFilter A.03.05.13 Administrator's Guide: HP-UX 11i v3
Table Of Contents
- HP-UX IPFilter Version A.03.05.13 Administrator's Guide
- Legal Notices
- Table of Contents
- Preface: About This Document
- 1 Installing and Configuring HP-UX IPFilter
- Overview of HP-UX IPFilter Installation
- Step 1: Checking HP-UX IPFilter Installation Prerequisites
- Step 2: Loading HP-UX IPFilter Software
- Step 3: Determining the Rules for IPFilter
- Step 4: Adding Rules to the Rules Files
- Step 5: Loading IPFilter and NAT Rules
- Step 6: Verifying the Installation and Configuration
- Kernel Tunable Parameters
- Supported and Unsupported Interfaces
- Troubleshooting HP-UX IPFilter
- 2 HP-UX IPFilter on HP-UX 11i Version 3
- 3 Rules and Keywords
- IPFilter Configuration Files
- Basic Rules Processing
- IPFilter Keywords
- pass and block: Controlling IP Traffic
- in and out: Bidirectional Filtering
- quick: Optimizing IPFilter Rules Processing
- on: Filtering by Network Interfaces
- from and to: Filtering by IP Addresses and Subnets
- log: Tracking Packets on a System
- proto: Controlling Specific Protocols
- opt and ipopts: Filtering on IP Options
- icmp-type: Filtering ICMP Traffic by Type
- port: Filtering on TCP and UDP Ports
- keep state: Protecting TCP, UDP, and ICMP Sessions
- flags: Tight Filtering Based on TCP Header Flags
- keep frags: Letting Fragmented Packets Pass
- with frags: Dropping Fragmented Packets
- with short: Dropping Short Fragments
- return-rst: Responding to Blocked TCP Packets
- return-icmp: Responding to Blocked ICMP Packets
- dup-to: Drop-Safe Logging
- NAT Keywords
- 4 Dynamic Connection Allocation
- 5 Firewall Building Concepts
- Blocking Services by Port Number
- Using Keep State
- Using Keep State with UDP
- Using Keep State with ICMP
- Logging Techniques
- Improving Performance with Rule Groups
- Localhost Filtering
- Using the to
- Creating a Complete Filter by Interface
- Combining IP Address and Network Interface Filtering
- Using Bidirectional Filtering Capabilities
- Using port and proto to Create a Secure Filter
- 6 HP-UX IPFilter Utilities
- 7 HP-UX IPFilter and FTP
- 8 HP-UX IPFilter and RPC
- 9 HP-UX IPFilter and IPSec
- 10 HP-UX IPFilter and Serviceguard
- A HP-UX IPFilter Configuration Examples
- B HP-UX IPFilter Static Linking
- C Performance Guidelines
- Index

Rules and Keywords
IPFilter Keywords
Chapter 348
dup-to: Drop-Safe Logging
IPFilter can pass packets on to another system for additional logging,
examination, and processing.
Instead of configuring IPFilter rules to drop packets, you can configure
rules to pass them to another system that can perform more extensive
logging and analysis than ipmon does. A firewall system can have
multiple interfaces. You can create a “drop-safe” for packets using the
dup-to keyword.
For example, to configure IPFilter to send a copy of every packet going
out the lan0 interface to your drop-safe network on ed0, include this rule
in your filter list:
pass out on lan0 dup-to ed0 from any to any
You can also send a packet directly to a specific IP address on your
drop-safe network. For example:
pass out on lan0 dup-to ed0:192.168.254.2 from any to any
This method alters the destination address of the copied packet, which
can negatively impact the usefulness of the IPFilter log. For this reason,
HP recommends only using the known address method of logging to be
certain that the logged address corresponds in some way to the system
for which IPFilter is logging.
In general, dup-to ed0 is all that is required to get a new copy of the
packet over to the drop-safe network for logging and examination.
You could also use this feature to implement an intrusion detection
network by hiding the presence of the intrusion detection system from
the real network so that it cannot be detected from the outside.
In addition, there are some operational characteristics that should be
noted. If you are only dealing with blocked packets, you can use the to
keyword as described in “Using the to Keyword to Capture Blocked
Packets” on page 83. If the system is configured to pass packets, you
should configure rules to make a copy of the packet for the drop-safe log
using the dup-to keyword.