# HG changeset patch
# User Christian Weiske <cweiske@cweiske.de>
# Date 1600718245 -7200
# Node ID 87daef9ed4e7213cf89b58046a4cd1d91adbdb18
# Parent  bb60db2b2cd193a8cc89121ba97b6b691d0a688d
Improve mod_firewall readme

diff -r bb60db2b2cd1 -r 87daef9ed4e7 mod_firewall/README.markdown
--- a/mod_firewall/README.markdown	Mon Sep 21 15:49:54 2020 +0100
+++ b/mod_firewall/README.markdown	Mon Sep 21 21:57:25 2020 +0200
@@ -68,6 +68,12 @@
 If multiple files are specified and they both add rules to the same chains,
 each file's rules will be processed in order, but the order of files is undefined.
 
+Reloading Prosody's configuration also reloads firewall rules.
+
+Make sure that `firewall_scripts` is in the global section of the configuration file
+and not below a virtual host or a component - unless you want per-vhost
+firewall rules.
+
 Conditions
 ----------
 
@@ -587,8 +593,9 @@
   --------------- ------------------------------------------------------------------------------------------------------------------------
   `LOG=message`   Logs the given message to Prosody's log file. Optionally prefix it with a log level in square brackets, e.g. `[debug]`
 
-You can include expressions in log messages, using `$(...)` syntax. For example, to log the stanza that matched the rule, you can use $(stanza),
-or to log just the top tag of the stanza, use $(stanza:top_tag()).
+You can include expressions in log messages, using `$(...)` syntax. For example, to log the stanza that matched the rule, you can use `$(stanza)`,
+or to log just the top tag of the stanza, use `$(stanza:top_tag())`.
+To fetch the sender JID, use `$(stanza.attr.from)`.
 
 Example: