SHOREWALL-PROXYARP(5)
π SHOREWALL-PROXYARP π
okay bestie, welcome to the proxyarp page from the Shorewall configuration files manual, section 5. yes we're reading a manpage for fun now, that's just the era we're in, and honestly? iconic. π
β¨ NAME β¨
proxyarp β the Shorewall Proxy ARP file, fr fr π
πΈ SYNOPSIS πΈ
/etc/shorewall/proxyarp
π¦ DESCRIPTION π¦
IPv4 only. no IPv6 here, she said what she said. π
This file is literally where you define Proxy ARP. You get one entry per IP address you wanna proxy. One. Entry. Per. Address. That's the whole vibe. β¨
The columns in the file go like this, bestie, in order:
ADDRESSβ address β this is just the IP Address. that's it. that's the column. π«ΆINTERFACEβ interface β (Optional as of Shorewall 4.4.16, yes she got an upgrade π ) this is the local interface where the system with the ip address fromADDRESSis connected. You only actually need this column whenHAVEROUTEis set toNo(orno), or when it's just left empty. lowkey conditional queen. πEXTERNALβ interface β the External Interface that gets used to access this system from the Internet. πHAVEROUTEβ[-|Yes|No]β so here's the tea: if there's already a route from the firewall to the host whose address you gave, you putYesoryesin this column. If there isn't, you putnoorNo, or just leave the column empty, and Shorewall will add the route for you, bestie, she's got you. π«Ά BUT β if Shorewall adds the route, whether it sticks around depends on the value of thePERSISTENTcolumn containingYes. Otherwise?shorewall stoporshorewall clearwill delete that route. no cap. πPERSISTENTβ[-|Yes|No]β this one only matters ifHAVEROUTEisNoorno. If it is, then this column decides whether the route Shorewall added survives ashorewall stopor ashorewall clear. If this column containsYesoryes, the route persists β¨. If the column is empty, or containsNoorno, then the route gets deleted byshorewall stoporshorewall clear. it's giving permanence issues. π
π EXAMPLE π
Example 1:
So picture this: a host with IP 155.186.235.6 is connected to interface eth1, and we want hosts attached via eth0 to be able to reach it using that address. slay. π
#ADDRESS INTERFACE EXTERNAL
155.186.235.6 eth1 eth0
π FILES π
/etc/shorewall/proxyarp
π SEE ALSO π
- https://shorewall.org/ProxyARP.htm[1]
- https://shorewall.org/configuration_file_basics.htm#Pairs[2]
shorewall(8)
π§ NOTES π§
- https://shorewall.org/ProxyARP.htm https://shorewall.org/ProxyARP.htm
- https://shorewall.org/configuration_file_basics.htm#Pairs https://shorewall.org/configuration_file_basics.htm#Pairs
and that's the whole page bestie, you ate that π β¨ This one's from the Configuration Files crew, dated 09/24/2020, and it's filed under SHOREWALL-PROXYARP(5) β go forth and proxy those ARPs, main character. ππΈπ¦
π¦ where this page comes from
- alpine 3.22: shorewall-doc 5.2.8-r1 Β· GPL-2.0-or-later
- alpine 3.23: shorewall-doc 5.2.8-r1 Β· GPL-2.0-or-later
- alpine 3.24: shorewall-doc 5.2.8-r1 Β· GPL-2.0-or-later
- debian bookworm: shorewall 5.2.8-2 Β· GPL-2.0-or-later
- debian trixie: shorewall 5.2.8-6 Β· GPL-2.0-or-later
- fedora 43: shorewall 5.2.8-17.fc43 Β· GPL-2.0-or-later
- fedora 44: shorewall 5.2.8-18.fc44 Β· GPL-2.0-or-later
- nixos 26.05: shorewall 5.2.8
- nixpkgs unstable: shorewall 5.2.8
- ubuntu noble: shorewall 5.2.8-5 Β· GPL-2.0-or-later
- ubuntu questing: shorewall 5.2.8-6
- ubuntu resolute: shorewall 5.2.8-6build1 Β· GPL-2.0-or-later
- ubuntu stonking: shorewall 5.2.8-6build1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms