proxyarp - Shorewall Proxy ARP file
This file is used to define Proxy ARP. There is one entry in this file for each
IP address to be proxied.
The columns in the file are as follows.
(Optional as of Shorewall 4.4.16)
Local interface where system with the ip
address in ADDRESS is connected. This column is only required when HAVEROUTE
is set to No ( no) or is left empty.
External Interface to be used to access this
system from the Internet.
If there is already a route from the firewall
to the host whose address is given, enter Yes or yes in this
column. Otherwise, enter no or No or leave the column empty and
Shorewall will add the route for you. If Shorewall adds the route, its
persistence depends on the value of the PERSISTENT column contains
Yes; otherwise, shorewall stop or shorewall clear will
delete the route.
If HAVEROUTE is No or no, then
the value of this column determines if the route added by Shorewall persists
after a shorewall stop or a shorewall clear. If this column
contains Yes or yes then the route persists; If the column is
empty or contains No or no then the route is deleted by
shorewall stop or shorewall clear.
Host with IP 18.104.22.168 is connected to
interface eth1 and we want hosts attached via eth0 to be able to access it
using that address.
#ADDRESS INTERFACE EXTERNAL
22.214.171.124 eth1 eth0
shorewall(8), shorewall-accounting(5), shorewall-actions(5),
shorewall-blacklist(5), shorewall-hosts(5), shorewall_interfaces(5),
shorewall-ipsets(5), shorewall-maclist(5), shorewall-masq(5),
shorewall-nat(5), shorewall-netmap(5), shorewall-params(5),
shorewall-policy(5), shorewall-providers(5), shorewall-rtrules(5),
shorewall-routestopped(5), shorewall-rules(5), shorewall.conf(5),
shorewall-secmarks(5), shorewall-tcclasses(5), shorewall-tcdevices(5),
shorewall-mangle(5), shorewall-tos(5), shorewall-tunnels(5),