<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
                 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
<!-- For license information see sanewall-manual-info.xml.in -->
<refentry id="helpcmd-iptables">

<refmeta>
<refentrytitle>iptables helper: sanewall-iptables</refentrytitle>
<manvolnum>5</manvolnum>
</refmeta>

<refnamediv>
<refdescriptor>sanewall-iptables</refdescriptor>
<refname>sanewall-iptables</refname>
<refpurpose>include custom iptables commands</refpurpose>
</refnamediv>

<refsynopsisdiv>
  <cmdsynopsis>
    <command>iptables</command>
    <arg rep="repeat" choice="plain"><replaceable>argument</replaceable></arg>
  </cmdsynopsis>
</refsynopsisdiv>

<refsect1><title>Description</title>
  <para>
    The <command>iptables</command> helper command passes all of its
    arguments to the real <command>iptables(8)</command> at the appropriate
    point during run-time.
  </para>
  <note><para>
    When used in an <command>interface</command> or <command>router</command>,
    the result will not have a direct relationship to the enclosing definition
    as the parameters passed are only those you supply.
  </para></note>
  <para>
    You should not use <command>/sbin/iptables</command> directly
    in a <application>Sanewall</application> configuration as it will
    run before <application>Sanewall</application> activates its
    firewall. This means they it be applied to the running firewall,
    not the new firewall, so will be removed when the new firewall
    is activated.
  </para>
  <para>
    The <command>iptables</command> helper is provided to allow you to
    hook in commands safely.
  </para>
</refsect1>

<refsect1><title>See Also</title>
  <simplelist type="vert">
    <member><xref linkend="sanewall"/></member>
    <member><xref linkend="sanewall.conf"/></member>
    <member>administration tool for IPv4 firewalls: iptables(8)</member>
  </simplelist>
</refsect1>

</refentry>
