1SHOREWALL-STOPPEDRU(5) Configuration Files SHOREWALL-STOPPEDRU(5)
2
6 stoppedrules - The Shorewall file that governs what traffic flows
7 through the firewall while it is in the 'stopped' state.
8
10 /etc/shorewall[6]/stoppedrules
11
13 This file is used to define the hosts that are accessible when the
14 firewall is stopped or is being stopped.
15 Warning
17 Changes to this file do not take effect until after the next
18 shorewall start, shorewall reload, shorewall restart, or shorewall
19 compile command.
20 The columns in the file are as follows (where the column name is
22 followed by a different name in parentheses, the different name is used
23 in the alternate specification syntax).
24 ACTION - ACCEPT|NOTRACK|DROP
26 Determines the disposition of the packet.
27 ACCEPT means that the packet will be accepted.
29 NOTRACK indicates that no conntrack entry should be created for the
31 packet. NOTRACK does not imply ACCEPT.
32 DROP was added in Shorewall 4.6.0 and causes the packet to be
34 dropped in the raw table's PREROUTING chain.
35 SOURCE -
37 [-|[$FW|interface]|[{$FW|interface}[:address[,address]...]]|[address[,address]...]
38 $FW matches packets originating on the firewall itself, while
39 interface specifies packets arriving on the named interface.
40 This column may also include a comma-separated list of IP/subnet
42 addresses. If your kernel and iptables include iprange match
43 support, IP address ranges are also allowed. Ipsets and exclusion
44 are also supported. When $FW or interface are specified, the list
45 must be preceded by a colon (":").
46 If left empty or supplied as "-", 0.0.0.0/0 is assumed.
48 DEST -
50 [-|[$FW|interface]|[{$FW|interface}[:address[,address]...]]|[address[,address]...]
51 $FW matches packets addressed the firewall itself, while interface
52 specifies packets arriving on the named interface. Neither may be
53 specified if the target is NOTRACK or DROP.
54 This column may also include a comma-separated list of IP/subnet
56 addresses. If your kernel and iptables include iprange match
57 support, IP address ranges are also allowed. Ipsets and exclusion
58 are also supported. When $FW or interface are specified, the list
59 must be preceded by a colon (":").
60 If left empty or supplied as "-", 0.0.0.0/0 is assumed.
62 PROTO (Optional) – protocol-name-or-number[,...]
64 Protocol.
65 Beginning with Shorewall 4.5.12, this column can accept a
67 comma-separated list of protocols.
68 DPORT – service-name/port-number-list
70 Optional. A comma-separated list of port numbers and/or service
71 names from /etc/services. May also include port ranges of the form
72 low-port:high-port if your kernel and iptables include port range
73 support.
74 This column was formerly labelled DEST PORT(S).
76 SPORT – service-name/port-number-list
78 Optional. A comma-separated list of port numbers and/or service
79 names from /etc/services. May also include port ranges of the form
80 low-port:high-port if your kernel and iptables include port range
81 support.
82 Beginning with Shorewall 4.5.15, you may place '=' in this column,
84 provided that the DPORT column is non-empty. This causes the rule
85 to match when either the source port or the destination port in a
86 packet matches one of the ports specified in DEST PORTS(S). Use of
87 '=' requires multi-port match in your iptables and kernel.
88 This column was formerly labelled SOURCE PORT(S).
90
92 /etc/shorewall/stoppedrules
93 /etc/shorewall6/stoppedrules
95
97 http://www.shorewall.net/starting_and_stopping_shorewall.htm[1]
98 http://www.shorewall.net/configuration_file_basics.htm#Pairs[2]
100 shorewall(8)
102
104 1. http://www.shorewall.net/starting_and_stopping_shorewall.htm
105 http://www.shorewall.net/starting_and_stopping_shorewall.htm
106 2. http://www.shorewall.net/configuration_file_basics.htm#Pairs
108 http://www.shorewall.net/configuration_file_basics.htm#Pairs
109Configuration Files 01/17/2019 SHOREWALL-STOPPEDRU(5)