From ba4db1dd41fa7903b28c17da314cd22cf164e0c7 Mon Sep 17 00:00:00 2001 From: Tom Eastep Date: Sun, 22 Nov 2009 09:52:13 -0800 Subject: [PATCH] Move Logging section forward in the HOWTOs --- docs/three-interface.xml | 102 +++++++++++++++++++-------------------- docs/two-interface.xml | 102 +++++++++++++++++++-------------------- 2 files changed, 102 insertions(+), 102 deletions(-) diff --git a/docs/three-interface.xml b/docs/three-interface.xml index 6fc9d169c..10086d34c 100644 --- a/docs/three-interface.xml +++ b/docs/three-interface.xml @@ -689,6 +689,57 @@ root@lists:~# +
+ Logging + + Shorewall does not maintain a log itself but rather relies on your + system's logging configuration. + The following commands rely + on knowing where Netfilter messages are logged: + + + + shorewall show log (Displays the last 20 + Netfilter log messages) + + + + shorewall logwatch (Polls the log at a + settable interval + + + + shorewall dump (Produces an extensive report + for inclusion in Shorewall problem reports) + + + + It is important that these commands work properly because when you + encounter connection problems when Shorewall is running, the first thing + that you should do is to look at the Netfilter log; with the help of + Shorewall FAQ 17, you can usually + resolve the problem quickly. + + Most commonly, Netfilter messages are logged to + /var/log/messages. Recent + SuSE/OpenSuSE releases come preconfigured with + syslog-ng and log netfilter messages to + /var/log/firewall. + + + + If you are running a distribution that logs netfilter messages to a + log other than /var/log/messages, then modify the + LOGFILE setting in /etc/shorewall/shorewall.conf to + specify the name of your log. + + + The LOGFILE setting does not control where the Netfilter log is + maintained -- it simply tells the /sbin/shorewall + utility where to find the log. + +
+
Port Forwarding (DNAT) @@ -945,57 +996,6 @@ ACCEPT net $FW tcp 80
-
- Logging - - Shorewall does not maintain a log itself but rather relies on your - system's logging configuration. - The following commands rely - on knowing where Netfilter messages are logged: - - - - shorewall show log (Displays the last 20 - Netfilter log messages) - - - - shorewall logwatch (Polls the log at a - settable interval - - - - shorewall dump (Produces an extensive report - for inclusion in Shorewall problem reports) - - - - It is important that these commands work properly because when you - encounter connection problems when Shorewall is running, the first thing - that you should do is to look at the Netfilter log; with the help of - Shorewall FAQ 17, you can usually - resolve the problem quickly. - - Most commonly, Netfilter messages are logged to - /var/log/messages. Recent - SuSE/OpenSuSE releases come preconfigured with - syslog-ng and log netfilter messages to - /var/log/firewall. - - - - If you are running a distribution that logs netfilter messages to a - log other than /var/log/messages, then modify the - LOGFILE setting in /etc/shorewall/shorewall.conf to - specify the name of your log. - - - The LOGFILE setting does not control where the Netfilter log is - maintained -- it simply tells the /sbin/shorewall - utility where to find the log. - -
-
Some Things to Keep in Mind diff --git a/docs/two-interface.xml b/docs/two-interface.xml index 978b41475..18a47771e 100644 --- a/docs/two-interface.xml +++ b/docs/two-interface.xml @@ -640,6 +640,57 @@ root@lists:~#
+
+ Logging + + Shorewall does not maintain a log itself but rather relies on your + system's logging configuration. + The following commands rely + on knowing where Netfilter messages are logged: + + + + shorewall show log (Displays the last 20 + netfilter log messages) + + + + shorewall logwatch (Polls the log at a + settable interval + + + + shorewall dump (Produces an extensive report + for inclusion in Shorewall problem reports) + + + + It is important that these commands work properly because when you + encounter connection problems when Shorewall is running, the first thing + that you should do is to look at the Netfilter log; with the help of + Shorewall FAQ 17, you can usually + resolve the problem quickly. + + Most commonly, Netfilter messages are logged to + /var/log/messages. Recent + SuSE/OpenSuSE releases come preconfigured with + syslog-ng and log netfilter messages to + /var/log/firewall. + + + + If you are running a distribution that logs netfilter messages to a + log other than /var/log/messages, then modify the + LOGFILE setting in /etc/shorewall/shorewall.conf to + specify the name of your log. + + + The LOGFILE setting does not control where the Netfilter log is + maintained -- it simply tells the /sbin/shorewall + utility where to find the log. + +
+
Port Forwarding (DNAT) @@ -864,57 +915,6 @@ ACCEPT loc $FW tcp 80 #Allow Weblet to work
-
- Logging - - Shorewall does not maintain a log itself but rather relies on your - system's logging configuration. - The following commands rely - on knowing where Netfilter messages are logged: - - - - shorewall show log (Displays the last 20 - netfilter log messages) - - - - shorewall logwatch (Polls the log at a - settable interval - - - - shorewall dump (Produces an extensive report - for inclusion in Shorewall problem reports) - - - - It is important that these commands work properly because when you - encounter connection problems when Shorewall is running, the first thing - that you should do is to look at the Netfilter log; with the help of - Shorewall FAQ 17, you can usually - resolve the problem quickly. - - Most commonly, Netfilter messages are logged to - /var/log/messages. Recent - SuSE/OpenSuSE releases come preconfigured with - syslog-ng and log netfilter messages to - /var/log/firewall. - - - - If you are running a distribution that logs netfilter messages to a - log other than /var/log/messages, then modify the - LOGFILE setting in /etc/shorewall/shorewall.conf to - specify the name of your log. - - - The LOGFILE setting does not control where the Netfilter log is - maintained -- it simply tells the /sbin/shorewall - utility where to find the log. - -
-
Some Things to Keep in Mind