diff --git a/manpages/shorewall-rules.xml b/manpages/shorewall-rules.xml
index ff02dac57..5de7ffc7f 100644
--- a/manpages/shorewall-rules.xml
+++ b/manpages/shorewall-rules.xml
@@ -413,57 +413,56 @@
The older syntax where the macro name and the target are
separated by a slash (e.g. FTP/ACCEPT) is still allowed but is
deprecated.
-
- The ACTION may
- optionally be followed by ":" and a syslog log level (e.g,
- REJECT:info or DNAT:debug). This causes the packet to be
- logged at the specified level. Note that if the ACTION involves destination network
- address translation (DNAT, REDIRECT, etc.) then the packet is
- logged before the destination
- address is rewritten.
-
- If the ACTION names an
- action declared in shorewall-actions(5) or
- in /usr/share/shorewall/actions.std then:
-
-
-
- If the log level is followed by "!' then all rules
- in the action are logged at the log level.
-
-
-
- If the log level is not followed by "!" then only
- those rules in the action that do not specify logging are
- logged at the specified level.
-
-
-
- The special log level none! suppresses logging by the
- action.
-
-
-
- You may also specify ULOG or NFLOG (must be in upper case) as a log
- level.This will log to the ULOG or NFLOG target for routing to
- a separate log through use of ulogd (http://www.netfilter.org/projects/ulogd/index.html).
-
- Actions specifying logging may be followed by a log tag
- (a string of alphanumeric characters) which is appended to the
- string generated by the LOGPREFIX (in shorewall.conf(5)).
-
- Example: ACCEPT:info:ftp would include 'ftp ' at the end
- of the log prefix generated by the LOGPREFIX setting.
+
+ The ACTION may optionally be
+ followed by ":" and a syslog log level (e.g, REJECT:info or
+ DNAT:debug). This causes the packet to be logged at the specified
+ level. Note that if the ACTION
+ involves destination network address translation (DNAT, REDIRECT,
+ etc.) then the packet is logged before the destination address is
+ rewritten.
+
+ If the ACTION names an
+ action declared in shorewall-actions(5) or in
+ /usr/share/shorewall/actions.std then:
+
+
+
+ If the log level is followed by "!' then all rules in the
+ action are logged at the log level.
+
+
+
+ If the log level is not followed by "!" then only those
+ rules in the action that do not specify logging are logged at
+ the specified level.
+
+
+
+ The special log level none! suppresses logging by the
+ action.
+
+
+
+ You may also specify ULOG or
+ NFLOG (must be in upper case) as a
+ log level.This will log to the ULOG or NFLOG target for routing to a
+ separate log through use of ulogd (http://www.netfilter.org/projects/ulogd/index.html).
+
+ Actions specifying logging may be followed by a log tag (a
+ string of alphanumeric characters) which is appended to the string
+ generated by the LOGPREFIX (in shorewall.conf(5)).
+
+ Example: ACCEPT:info:ftp would include 'ftp ' at the end of
+ the log prefix generated by the LOGPREFIX setting.
diff --git a/manpages6/shorewall6-rules.xml b/manpages6/shorewall6-rules.xml
index 2b7755185..18b36de08 100644
--- a/manpages6/shorewall6-rules.xml
+++ b/manpages6/shorewall6-rules.xml
@@ -308,55 +308,51 @@
The older syntax where the macro name and the target are
separated by a slash (e.g. FTP/ACCEPT) is still allowed but is
deprecated.
-
-
-
- The ACTION may optionally
- be followed by ":" and a syslog log level (e.g, REJECT:info or
- ACCEPT:debug). This causes the packet to be logged at the
- specified level.
+ The ACTION may optionally be
+ followed by ":" and a syslog log level (e.g, REJECT:info or
+ ACCEPT:debug). This causes the packet to be logged at the specified
+ level.
- If the ACTION names an
- action declared in shorewall6-actions(5) or in
- /usr/share/shorewall6/actions.std then:
+ If the ACTION names an
+ action declared in shorewall6-actions(5) or in
+ /usr/share/shorewall6/actions.std then:
-
-
- If the log level is followed by "!' then all rules in
- the action are logged at the log level.
-
+
+
+ If the log level is followed by "!' then all rules in the
+ action are logged at the log level.
+
-
- If the log level is not followed by "!" then only those
- rules in the action that do not specify logging are logged at
- the specified level.
-
+
+ If the log level is not followed by "!" then only those
+ rules in the action that do not specify logging are logged at
+ the specified level.
+
-
- The special log level none! suppresses logging by the
- action.
-
-
+
+ The special log level none! suppresses logging by the
+ action.
+
+
- You may also specify NFLOG
- (must be in upper case) as a log level.This will log to the NFLOG
- target for routing to a separate log through use of ulogd (http://www.netfilter.org/projects/ulogd/index.html).
+ You may also specify NFLOG
+ (must be in upper case) as a log level.This will log to the NFLOG
+ target for routing to a separate log through use of ulogd (http://www.netfilter.org/projects/ulogd/index.html).
- Actions specifying logging may be followed by a log tag (a
- string of alphanumeric characters) which is appended to the string
- generated by the LOGPREFIX (in shorewall6.conf(5)).
+ Actions specifying logging may be followed by a log tag (a
+ string of alphanumeric characters) which is appended to the string
+ generated by the LOGPREFIX (in shorewall6.conf(5)).
- Example: ACCEPT:info:ftp would include 'ftp ' at the end of
- the log prefix generated by the LOGPREFIX setting.
-
+ Example: ACCEPT:info:ftp would include 'ftp ' at the end of
+ the log prefix generated by the LOGPREFIX setting.