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
HP-UX IPFilter and Serviceguard
Using HP-UX IPFilter with Serviceguard
Chapter 10142
In the previous set of rules,
<clusternodes>
are all nodes in the cluster,
<remote node name>
is the specific remote node, and
<remotenodes>
are all other nodes outside the cluster that are designated in the
cmclnodelist file for remote command access.
Running the cmscancl command requires the “shell” port be open.
Cluster Object Manager If you are using a Cluster Object Manager
(COM) on a node outside of the cluster to provide connections to
Serviceguard Manager clients, each node in the cluster must have the
following rules configured:
pass in quick proto tcp from
<comnode>
to
<clusternodes>
port =
5302 flags S keep state
pass in quick proto udp from
<comnode>
to
<clusternodes>
port =
5302 keep state
pass out quick proto tcp from
<clusternodes>
to
<comnode>
port
49151 >< 65536 keep state
pass out quick proto udp from
<clusternodes>
to
<comnode>
port
49151 >< 65536 keep state
The node running COM must have the following rules configured:
pass in quick proto tcp from
<comclient>
to
<comnode>
port =
5303 flags S keep state
pass in quick proto tcp from
<clusternodes>
to
<comnode>
port
49151 >< 65536 keep state
pass in quick proto udp from
<clusternodes>
to
<comnode>
port
49151 >< 65536 keep state
pass out quick proto tcp from
<comnode>
to
<clusternodes>
port
= 5302 flags S keep state
pass out quick proto udp from
<comnode>
to
<clusternodes>
port
= 5302 keep state
Each COM client must have the following rules configured:
pass out quick proto tcp from
<comclient>
to
<comnode>
port =
5303 flags S keep state
In the previous set of rules,
<clusternodes>
are all nodes in the cluster,
<comclient>
are nodes that are clients of COM for Serviceguard
Manager or Continental Clusters products, and
<comnode>
is the node
running the COM.