70 lines
4.8 KiB
HTML
70 lines
4.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="task" />
|
||
|
|
<meta name="DC.Title" content="Include files in packet rules" />
|
||
|
|
<meta name="abstract" content="You can activate more than one packet rules file on your system by using the Include feature of the Packet Rules Editor." />
|
||
|
|
<meta name="description" content="You can activate more than one packet rules file on your system by using the Include feature of the Packet Rules Editor." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajbrzajbx1creatingnewrulessd.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajbrzajb82filterinterfacessd.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajbrzajb89commentssd.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajbrzajboffiles.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="rzajb88-includes_sd" />
|
||
|
|
<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>Include files in packet rules</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzajb88-includes_sd"><a name="rzajb88-includes_sd"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Include files in packet rules</h1>
|
||
|
|
<div><p>You can activate more than one packet rules file on your system
|
||
|
|
by using the <strong>Include</strong> feature of the Packet Rules Editor.</p>
|
||
|
|
<div class="section"><p>Using multiple files makes it much easier for you to work with
|
||
|
|
your rules. Especially, if you need a large number of rules to control traffic
|
||
|
|
on multiple interfaces. For example, you may want to use a group of rules
|
||
|
|
on multiple interfaces. </p>
|
||
|
|
<p>You can create this group within an individual
|
||
|
|
file. Instead of rewriting the rules every time you want to use them in other
|
||
|
|
files, you can include them in the master file. The master file is the file
|
||
|
|
that can be active at any given time. You only need to use the include feature
|
||
|
|
to add the rules to your master file. </p>
|
||
|
|
<p>When creating include files,
|
||
|
|
you might want to keep your NAT rules for an interface separate from your
|
||
|
|
filter rules for that interface. However, only one file can be active at
|
||
|
|
any given time.</p>
|
||
|
|
<p>When you create a new rules file, you can include any
|
||
|
|
existing files as part of the new file. Before you do this, you should create
|
||
|
|
the new filter rules you want to use. Whenever you create a rule, you should
|
||
|
|
file (group) them by type. This way you do not need to re-create rules that
|
||
|
|
you have used before. You can just include or remove them as needed. </p>
|
||
|
|
<p>For
|
||
|
|
instructions on how to include a file in your rules, use the Packet Rules
|
||
|
|
Editor online help.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzajbrzajbx1creatingnewrulessd.htm" title="Read the checklist that contains an overview of the tasks you must complete to ensure that your rules work properly when activated.">Configure packet rules</a></div>
|
||
|
|
<div class="previouslink"><strong>Previous topic:</strong> <a href="rzajbrzajb82filterinterfacessd.htm" title="Define filter interfaces to establish the filter rules that you want the system to apply to each interface.">Define IP filter interfaces</a></div>
|
||
|
|
<div class="nextlink"><strong>Next topic:</strong> <a href="rzajbrzajb89commentssd.htm" title="Adding comments about your rules files is a way to record how you intend your rules to work.">Add comments in the packet rules</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzajbrzajboffiles.htm" title="While network address translation (NAT) and IP filtering work independently of each other, you can use NAT in conjunction with IP filtering.">Organize NAT rules with IP filter rules</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|