diff options
authorJan Engelhardt <>2010-06-04 14:08:58 +0200
committerJan Engelhardt <>2010-06-04 14:09:19 +0200
commitfdc19bea817086425c1ad2ad6a2b732eb610fb76 (patch)
parent7cd3c2edb1dba13867b80dd29b02d6c945fcd03f (diff)
doc: xt_LED: nroff formatting requirements
Verbatim dashes need to be backslash-prefixed. Signed-off-by: Jan Engelhardt <>
1 files changed, 5 insertions, 5 deletions
diff --git a/extensions/ b/extensions/
index 0226f107..81c2f296 100644
--- a/extensions/
+++ b/extensions/
@@ -4,11 +4,11 @@ system. One example might be to light up an LED for a few minutes every time
an SSH connection is made to the local machine. The following options control
the trigger behavior:
-\fB--led-trigger-id\fP \fIname\fP
+\fB\-\-led\-trigger\-id\fP \fIname\fP
This is the name given to the LED trigger. The actual name of the trigger
will be prefixed with "netfilter-".
-\fB--led-delay\fP \fIms\fP
+\fB\-\-led-delay\fP \fIms\fP
This indicates how long (in milliseconds) the LED should be left illuminated
when a packet arrives before being switched off again. The default is 0
(blink as fast as possible.) The special value \fIinf\fP can be given to
@@ -16,7 +16,7 @@ leave the LED on permanently once activated. (In this case the trigger will
need to be manually detached and reattached to the LED device to switch it
off again.)
Always make the LED blink on packet arrival, even if the LED is already on.
This allows notification of new packets even with long delay values (which
otherwise would result in a silent prolonging of the delay time.)
@@ -24,7 +24,7 @@ otherwise would result in a silent prolonging of the delay time.)
Create an LED trigger for incoming SSH traffic:
-iptables -A INPUT -p tcp --dport 22 -j LED --led-trigger-id ssh
+iptables \-A INPUT \-p tcp \-\-dport 22 \-j LED \-\-led\-trigger\-id ssh
Then attach the new trigger to an LED:
-echo netfilter-ssh >/sys/class/leds/\fIledname\fP/trigger
+echo netfilter\-ssh >/sys/class/leds/\fIledname\fP/trigger