56 lines
3.8 KiB
HTML
56 lines
3.8 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
|
<!DOCTYPE html
|
||
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html lang="en-us" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow" />
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<meta name="DC.Type" content="concept" />
|
||
|
|
<meta name="DC.Title" content="Organize multiple IP filter rules" />
|
||
|
|
<meta name="abstract" content="When you create a filter rule, it refers to a one-rule statement. A group of filter rules is called a set. The filters within a set are processed top-to-bottom, in physical order. Multiple sets are processed in physical order within a FILTER_INTERFACE statement." />
|
||
|
|
<meta name="description" content="When you create a filter rule, it refers to a one-rule statement. A group of filter rules is called a set. The filters within a set are processed top-to-bottom, in physical order. Multiple sets are processed in physical order within a FILTER_INTERFACE statement." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajbrzajb1whatis.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2000, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2000, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzajbom-files" />
|
||
|
|
<meta name="DC.Language" content="en-us" />
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
|
<title>Organize multiple IP filter rules</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzajbom-files"><a name="rzajbom-files"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Organize multiple IP filter rules</h1>
|
||
|
|
<div><p>When you create a filter rule, it refers to a one-rule statement.
|
||
|
|
A group of filter rules is called a <dfn class="term">set</dfn>. The filters within a
|
||
|
|
set are processed top-to-bottom, in physical order. Multiple sets are processed
|
||
|
|
in physical order within a FILTER_INTERFACE statement.</p>
|
||
|
|
<p>The following example shows where one set contains three filter statements.
|
||
|
|
Whenever you refer to this set, all three rules will be included. It is typically
|
||
|
|
easiest to include all of your filter rules in one set.</p>
|
||
|
|
<pre>FILTER SET all ACTION = PERMIT DIRECTION = INBOUND SRCADDR = * DSTADDR %
|
||
|
|
= * PROTOCOL = TCP/STARTING DSTPORT = * SRCPORT = * FRAGMENTS %
|
||
|
|
= HEADERS JRN = FULL
|
||
|
|
FILTER SET all ACTION = PERMIT DIRECTION = INBOUND SRCADDR = * DSTADDR %
|
||
|
|
= * PROTOCOL = TCP DSTPORT = * SRCPORT = * FRAGMENTS = NONE %
|
||
|
|
JRN = OFF
|
||
|
|
FILTER SET all ACTION = PERMIT DIRECTION = INBOUND SRCADDR = * DSTADDR %
|
||
|
|
= * PROTOCOL = ICMP TYPE = * CODE = * FRAGMENTS = NONE JRN %
|
||
|
|
= OFF
|
||
|
|
FILTER_INTERFACE LINE = ETHLINE SET = all
|
||
|
|
###Ethernet line ETHLINE</pre>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzajbrzajb1whatis.htm" title="Packet rules comprise both network address translation (NAT) rules and IP filtering rules. These two functions run at the IP layer of the TCP/IP stack and help protect your system against potential risks that are commonly associated with TCP/IP traffic.">Packet rules concepts</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|