On Wed, 4 Jun 2025 18:51:23 +0200
Phil Sutter <phil@xxxxxx> wrote:
> Thanks! I think we need to update the synopsis as well. What do you
> think of my extra (attached) to yours?
Good. See the attachment for a bit of style improvement. Removed
the quotes I put around eth0 to look uniform with the previous
examples. Also did not like how 'Note that' sounds, as if anonymous
chains are something unimportant or accidental.
diff --git a/doc/statements.txt b/doc/statements.txt
index ac8b15ec..0b8c4ccb 100644
--- a/doc/statements.txt
+++ b/doc/statements.txt
@@ -39,10 +39,10 @@ resumes with the next base chain hook, not the rule following the queue verdict.
call stack, meaning that after the new chain evaluation will continue at the last
chain instead of the one containing the goto statement.
-Note that an alternative to specifying the name of an existing, regular chain
-in 'CHAIN' is to specify an anonymous chain ad-hoc. Like with anonymous sets,
-it can't be referenced from another rule and will be removed along with the
-rule containing it.
+An alternative to specifying the name of an existing, regular chain in 'CHAIN'
+is to specify an anonymous chain ad-hoc. Like with anonymous sets, it can't be
+referenced from another rule and will be removed along with the rule containing
+it.
.Using verdict statements
-------------------
@@ -53,7 +53,7 @@ filter input iif eth0 ip saddr 192.168.0.0/24 jump from_lan
filter input iif eth0 drop
# jump and goto statements support anonymous chain creation
-filter input iif "eth0" jump { ip saddr 192.168.0.0/24 drop ; udp dport domain drop ; }
+filter input iif eth0 jump { ip saddr 192.168.0.0/24 drop ; udp dport domain drop ; }
-------------------
PAYLOAD STATEMENT
