SHOREWALL-PROXYARP(5)

πŸ“¦
version 5.2.8 Β· 2 versions
  • 5.2.8 Β· alpine 3.22, alpine 3.23, alpine 3.24, debian bookworm, debian trixie, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking (latest)
  • 5.2.3.4 Β· ubuntu jammy
, in alpine 3.22, alpine 3.23, alpine 3.24, debian bookworm, debian trixie, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’– 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 from ADDRESS is connected. You only actually need this column when HAVEROUTE is set to No (or no), 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 put Yes or yes in this column. If there isn't, you put no or No, 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 the PERSISTENT column containing Yes. Otherwise? shorewall stop or shorewall clear will delete that route. no cap. 😭
  • PERSISTENT β€” [-|Yes|No] β€” this one only matters if HAVEROUTE is No or no. If it is, then this column decides whether the route Shorewall added survives a shorewall stop or a shorewall clear. If this column contains Yes or yes, the route persists ✨. If the column is empty, or contains No or no, then the route gets deleted by shorewall stop or shorewall 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 πŸ’œ


🧚 NOTES 🧚

  1. https://shorewall.org/ProxyARP.htm https://shorewall.org/ProxyARP.htm
  2. 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. πŸ‘‘πŸŒΈπŸ¦‹