diff --git a/Shorewall/Perl/Shorewall/Config.pm b/Shorewall/Perl/Shorewall/Config.pm
index 1dd6f9d08..dbd911aed 100644
--- a/Shorewall/Perl/Shorewall/Config.pm
+++ b/Shorewall/Perl/Shorewall/Config.pm
@@ -6440,7 +6440,6 @@ sub get_configuration( $$$ ) {
$origin{$_} ||= '';
}
- default_yes_no 'INLINE_MATCHES' , '';
default_yes_no 'BASIC_FILTERS' , '';
default_yes_no 'WORKAROUNDS' , 'Yes';
default_yes_no 'DOCKER' , '';
diff --git a/Shorewall/manpages/shorewall.conf.xml b/Shorewall/manpages/shorewall.conf.xml
index 84d2fb3c3..a0347b7d0 100644
--- a/Shorewall/manpages/shorewall.conf.xml
+++ b/Shorewall/manpages/shorewall.conf.xml
@@ -1141,36 +1141,6 @@ net all DROP infothen the chain name is 'net-all'
-
- INLINE_MATCHES={Yes|No}
-
-
- Added in Shorewall 4.6.0. Traditionally in shorewall-rules(5), a
- semicolon separates column-oriented specifications on the left from
- alternative
- specificaitons on the right.. When INLINE_MATCHES=Yes is
- specified, the specifications on the right are interpreted as if
- INLINE had been specified in the ACTION column. This also applies to
- shorewall-masq(5)
- and shorewall-mangle(5)
- which also support INLINE. If not specified or if specified as the
- empty value, the value 'No' is assumed for backward
- compatibility.
-
- Beginning with Shorewall 5.0.0, it is no longer necessary to
- set INLINE_MATCHES=Yes in order to be able to specify your own
- iptables text in a rule and INLINE_MATCHES=Yes is deprecated.
- Beginning with 5.0.0, you may simply preface your text with a pair
- of semicolons (";;"). If alternate input is also specified in the
- rule, it should appear before the semicolons and may be separated
- from normal column input by a single semicolon or enclosed in curly
- braces ("{....}").
-
-
-
INVALID_DISPOSITION=[A_DROP|A_REJECT|DROP|REJECT|CONTINUE]