blob: 81c2f2968a0a9a157593db3c7523c41b6fedace2 [file] [log] [blame]
Adam Nielsen7cd3c2e2010-04-04 12:59:00 +02001This creates an LED-trigger that can then be attached to system indicator
2lights, to blink or illuminate them when certain packets pass through the
3system. One example might be to light up an LED for a few minutes every time
4an SSH connection is made to the local machine. The following options control
5the trigger behavior:
6.TP
Jan Engelhardtfdc19be2010-06-04 14:08:58 +02007\fB\-\-led\-trigger\-id\fP \fIname\fP
Adam Nielsen7cd3c2e2010-04-04 12:59:00 +02008This is the name given to the LED trigger. The actual name of the trigger
9will be prefixed with "netfilter-".
10.TP
Jan Engelhardtfdc19be2010-06-04 14:08:58 +020011\fB\-\-led-delay\fP \fIms\fP
Adam Nielsen7cd3c2e2010-04-04 12:59:00 +020012This indicates how long (in milliseconds) the LED should be left illuminated
13when a packet arrives before being switched off again. The default is 0
14(blink as fast as possible.) The special value \fIinf\fP can be given to
15leave the LED on permanently once activated. (In this case the trigger will
16need to be manually detached and reattached to the LED device to switch it
17off again.)
18.TP
Jan Engelhardtfdc19be2010-06-04 14:08:58 +020019\fB\-\-led\-always\-blink\fP
Adam Nielsen7cd3c2e2010-04-04 12:59:00 +020020Always make the LED blink on packet arrival, even if the LED is already on.
21This allows notification of new packets even with long delay values (which
22otherwise would result in a silent prolonging of the delay time.)
23.TP
24Example:
25.TP
26Create an LED trigger for incoming SSH traffic:
Jan Engelhardtfdc19be2010-06-04 14:08:58 +020027iptables \-A INPUT \-p tcp \-\-dport 22 \-j LED \-\-led\-trigger\-id ssh
Adam Nielsen7cd3c2e2010-04-04 12:59:00 +020028.TP
29Then attach the new trigger to an LED:
Jan Engelhardtfdc19be2010-06-04 14:08:58 +020030echo netfilter\-ssh >/sys/class/leds/\fIledname\fP/trigger