83 lines
6.5 KiB
HTML
83 lines
6.5 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="Verify packet rules" />
|
||
|
|
<meta name="abstract" content="Always verify your rules before you activate them. This helps ensure that the rules will be activated without problems." />
|
||
|
|
<meta name="description" content="Always verify your rules before you activate them. This helps ensure that the rules will be activated without problems." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajbrzajbx1creatingnewrulessd.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajbrzajb89commentssd.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajbactivaterules.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajbrzajb0dexample2.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajbrzajb0eexample3.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajbrzajb0fexample4.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajbrzajb0gexample5.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajbrzajbz1viewsd.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajbrzajbz1viewsd.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="rzajb8a1-verifying_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>Verify packet rules</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzajb8a1-verifying_sd"><a name="rzajb8a1-verifying_sd"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Verify packet rules</h1>
|
||
|
|
<div><p>Always verify your rules before you activate them. This helps ensure
|
||
|
|
that the rules will be activated without problems.</p>
|
||
|
|
<div class="section"><p>When you verify your packet rules, the system checks them for
|
||
|
|
syntax and semantic errors and reports the results in a message window at
|
||
|
|
the bottom of the Packet Rules Editor. For error messages that are associated
|
||
|
|
with a specific file and line number, you can right-click the error and select <span class="uicontrol">Go
|
||
|
|
To Line</span> to highlight the error in the file you are editing.</p>
|
||
|
|
<p>Before
|
||
|
|
using the verify function, you might want to consider viewing your packet
|
||
|
|
rules to check for visible errors. You cannot activate rules that have syntactical
|
||
|
|
errors. The verify function checks for errors of a syntactical nature. The
|
||
|
|
system can not verify whether you have ordered your rules correctly. You must
|
||
|
|
check for rule order manually. Packet rules are order-dependent, which means
|
||
|
|
that, you must order the rules the way that you want them applied.
|
||
|
|
If you order them incorrectly, you will not get the intended result. Ensure
|
||
|
|
that your rules are correct and ordered the way you want them applied before
|
||
|
|
you activate them. </p>
|
||
|
|
<p>For instructions on how to verify packet rules,
|
||
|
|
use the Packet Rules Editor online help.</p>
|
||
|
|
<div class="note"><span class="notetitle">Messages:</span> Whenever you activate your filter rules, the system automatically
|
||
|
|
verifies them. Various warning and error messages might be produced. A warning
|
||
|
|
message is for informational purposes and does not stop the verification process.
|
||
|
|
Read all messages carefully. One message appears saying that your verification
|
||
|
|
and activation were successful. This last sentence can also state that the
|
||
|
|
rule load was unsuccessful if there are severe errors.</div>
|
||
|
|
</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="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 class="nextlink"><strong>Next topic:</strong> <a href="rzajbactivaterules.htm" title="Activating the packet rules that you create is the final step in configuring packet rules.">Activate packet rules</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzajbrzajb0dexample2.htm" title="In this scenario, your company uses static network address translation (NAT) to map its private IP addresses to public addresses.">Scenario: Map IP addresses using NAT</a></div>
|
||
|
|
<div><a href="rzajbrzajb0eexample3.htm" title="In this scenario, your company uses IP filtering to restrict the IP traffic that can access its Web server to HTTP, Telnet, and FTP.">Scenario: Create filter rules to allow HTTP, Telnet, and FTP</a></div>
|
||
|
|
<div><a href="rzajbrzajb0fexample4.htm" title="In this scenario, your company combines network address translation (NAT) and IP filtering together. Your company wants to hide its personal computers and Web server behind a single, public, IP address and to allow other companies to access the Web server.">Scenario: Combine NAT and IP filtering</a></div>
|
||
|
|
<div><a href="rzajbrzajb0gexample5.htm" title="In this scenario, your company uses masquerade network address translation (NAT) to hide the private addresses of your personal computers. At the same time, your company allows your employees to access the Internet.">Scenario: Hide IP addresses using masquerade NAT</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
||
|
|
<div><a href="rzajbrzajbz1viewsd.htm" title="View your filter rules before you activate them to verify that they are correct.">View packet rules</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|