shorewall_code/manpages/shorewall-proxyarp.xml

128 lines
4.2 KiB
XML
Raw Normal View History

<?xml version="1.0" encoding="UTF-8"?>
<refentry>
<refmeta>
<refentrytitle>shorewall-proxyarp</refentrytitle>
<manvolnum>5</manvolnum>
</refmeta>
<refnamediv>
<refname>proxyarp</refname>
<refpurpose>Shorewall Proxy ARP file</refpurpose>
</refnamediv>
<refsynopsisdiv>
<cmdsynopsis>
<command>/etc/shorewall/proxyarp</command>
</cmdsynopsis>
</refsynopsisdiv>
<refsect1>
<title>Description</title>
<para>This file is used to define Proxy ARP.</para>
<para>The columns in the file are as follows.</para>
<variablelist>
<varlistentry>
<term><emphasis role="bold">ADDRESS</emphasis></term>
<listitem>
<para>IP Address.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis role="bold">INTERFACE</emphasis></term>
<listitem>
<para>Local interface where system is connected.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis role="bold">EXTERNAL</emphasis></term>
<listitem>
<para>External Interface to be used to access this system.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis role="bold">HAVEROUTE</emphasis></term>
<listitem>
<para>If there is already a route from the firewall to the host
whose address is given, enter <emphasis role="bold">Yes</emphasis>
or <emphasis role="bold">yes</emphasis> in this column. Otherwise,
enter <emphasis role="bold">no</emphasis> or <emphasis
role="bold">No</emphasis> or leave the column empty and Shorewall
will add the route for you. If Shorewall adds the route,the route
will be persistent if the <emphasis
role="bold">PERSISTENT</emphasis> column contains <emphasis
role="bold">Yes</emphasis>; otherwise, <emphasis
role="bold">shorewall stop</emphasis> or <emphasis
role="bold">shorewall clear</emphasis> will delete the route.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis role="bold">PERSISTENT</emphasis></term>
<listitem>
<para>If HAVEROUTE is <emphasis role="bold">No</emphasis> or
<emphasis role="bold">no</emphasis>, then the value of this column
determines if the route added by Shorewall persists after a
<emphasis role="bold">shorewall stop</emphasis> or a <emphasis
role="bold">shorewall clear</emphasis>. If this column contains
<emphasis role="bold">Yes</emphasis> or <emphasis
role="bold">yes</emphasis> then the route persists; If the column is
empty or contains <emphasis role="bold">No</emphasis> or <emphasis
role="bold">no</emphasis> then the route is deleted at
<command>shorewall stop</command> or <command>shorewall
clear</command>.</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1>
<title>Example</title>
<variablelist>
<varlistentry>
<term>Example 1:</term>
<listitem>
<para> Host with IP 155.186.235.6 is connected to interface eth1 and
we want hosts attached via eth0 to be able to access it using that
address.</para>
<programlisting> #ADDRESS INTERFACE EXTERNAL
155.186.235.6 eth1 eth0</programlisting>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1>
<title>FILES</title>
<para>/etc/shorewall/proxyarp</para>
</refsect1>
<refsect1>
<title>See ALSO</title>
<para>shorewall(8), shorewall-accounting(5), shorewall-actions(5),
shorewall-blacklist(5), shorewall-hosts(5), shorewall-interfaces(5),
shorewall-ipsec(5), shorewall-maclist(5), shorewall-masq(5),
shorewall-nat(5), shorewall-netmap(5), shorewall-params(5),
shorewall-policy(5), shorewall-providers(5), shorewall-route_routes(5),
shorewall-routestopped(5), shorewall-rules(5), shorewall.conf(5),
shorewall-tcclasses(5), shorewall-tcdevices(5), shorewall-tcrules(5),
shorewall-tos(5), shorewall-tunnels(5), shorewall-zones(5)</para>
</refsect1>
</refentry>