SHOREWALL-STOPPEDRU(5)

💖 NAME 💖

okay so bestie, <pink>stoppedrules</pink> is literally the Shorewall file that governs what traffic flows through the firewall while it's in the <purple>stopped</purple> state. like, the firewall's lil nap-time ruleset. iconic behavior honestly 🛌✨

---

✨ SYNOPSIS ✨

/etc/shorewall[6]/stoppedrules

---

🦋 DESCRIPTION 🦋

This file is used to define the hosts that are accessible when the firewall is stopped or is being stopped. fr fr, it's the guest list for when the bouncer (aka your firewall) is off duty 💅

Warning 🚨 Changes to this file do not take effect until after the next shorewall start, shorewall reload, shorewall restart, or shorewall compile command. so like… don't edit it and then be shocked when nothing happens. it's giving "I changed my profile pic but forgot to hit save." 😭

The columns in the file are as follows (where the column name is followed by a different name in parentheses, the different name is used in the alternate specification syntax). yes queen, two names, one column. it's giving ✨dual identity✨ iykyk

🎀 ACTION - ACCEPT|NOTRACK|DROP

Determines the disposition of the packet. basically: what are we doing with this lil guy? 🤔

• ACCEPT means that the packet will be accepted. come on in bestie, the door's open 🫶
• NOTRACK indicates that no conntrack entry should be created for the packet. <hotpink>NOTRACK does not imply ACCEPT.</hotpink> read that again, it's important!! not tracking ≠ letting it through, no cap 🚫
• DROP was added in Shorewall 4.6.0 and causes the packet to be dropped in the raw table's PREROUTING chain. it's giving "we're not even gonna talk about it" 💀

🌸 SOURCE -

[-|[$FW|interface]|[{$FW|interface}[:address[,address]...]]|[address[,address]...]

$FW matches packets originating on the firewall itself, while interface specifies packets arriving on the named interface. so it's like, is this coming from me or from out there? main character vs. side character energy 🎭

This column may also include a comma-separated list of IP/subnet addresses. If your kernel and iptables include iprange match support, IP address ranges are also allowed. Ipsets and exclusion are also supported. When $FW or interface are specified, the list must be preceded by a colon (":"). don't forget the colon, bestie, she's load-bearing 🫠

If left empty or supplied as -, 0.0.0.0/0 is assumed. i.e. everybody. the whole group chat. 💌

🌈 DEST -

[-|[$FW|interface]|[{$FW|interface}[:address[,address]...]]|[address[,address]...]

$FW matches packets addressed the firewall itself, while interface specifies packets arriving on the named interface. <red>Neither may be specified if the target is NOTRACK or DROP.</red> so if you're dropping or not-tracking, don't go naming a destination, it's just not that kind of party 🙅‍♀️

This column may also include a comma-separated list of IP/subnet addresses. If your kernel and iptables include iprange match support, IP address ranges are also allowed. Ipsets and exclusion are also supported. When $FW or interface are specified, the list must be preceded by a colon (":").

If left empty or supplied as -, 0.0.0.0/0 is assumed. again: everyone, everywhere, all at once ✨

💜 PROTO (Optional) – protocol-name-or-number[,...]

Protocol. Beginning with Shorewall 4.5.12, this column can accept a comma-separated list of protocols. glow-up era, we love to see it 🧚

🍓 DPORT – service-name/port-number-list

Optional. A comma-separated list of port numbers and/or service names from /etc/services. May also include port ranges of the form low-port:high-port if your kernel and iptables include port range support. 🔥

This column was formerly labelled DEST PORT(S). rebranded, but still the same queen 👑

⭐ SPORT – service-name/port-number-list

Optional. A comma-separated list of port numbers and/or service names from /etc/services. May also include port ranges of the form low-port:high-port if your kernel and iptables include port range support.

Beginning with Shorewall 4.5.15, you may place '=' in this column, provided that the DPORT column is non-empty. This causes the rule to match when either the source port or the destination port in a packet matches one of the ports specified in DEST PORTS(S). Use of '=' requires multi-port match in your iptables and kernel. it's giving "either/or" and honestly? slay 🎯

This column was formerly labelled SOURCE PORT(S).

---

🫶 FILES 🫶

• /etc/shorewall/stoppedrules
• /etc/shorewall6/stoppedrules

two homes, one vibe 🏠🏠

---

👑 SEE ALSO 👑

• https://shorewall.org/starting_and_stopping_shorewall.htm[1]
• https://shorewall.org/configuration_file_basics.htm#Pairs[2]
• shorewall(8)

---

💅 NOTES 💅

1. https://shorewall.org/starting_and_stopping_shorewall.htm https://shorewall.org/starting_and_stopping_shorewall.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!! this was a Configuration Files moment, dropped on 09/24/2020, and you were just reading SHOREWALL-STOPPEDRU(5) 🦋💖 stay stoppin' (or don't), ily, bye!! ✨