From: Patrick McHardy <kaber@trash.net>
To: Adam Nielsen <a.nielsen@shikadi.net>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Netfilter Developer Mailing List
<netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH 1/2 v2] New netfilter target to trigger LED devices
Date: Wed, 12 Nov 2008 12:17:37 +0100 [thread overview]
Message-ID: <491ABB51.7010500@trash.net> (raw)
In-Reply-To: <491AB8B6.5080708@shikadi.net>
Adam Nielsen wrote:
>>> Add a new "LED" target to iptables, which allows LEDs to blink in
>>> response to matching rules.
>>
>> I did not have a look in deep into your patch but the first questions
>> that comes to my mind is, how many people can benefit from this LED
>> target? What is its real application?
>
> Well granted its purpose is somewhat trivial, but if you do have
> devices on your system that appear in the LED class it could be quite
> useful.
>
> Linux running on an embedded router for example, could blink specific
> LEDs on the device's front panel depending on the traffic being
> routed. You wouldn't be limited to one LED per interface either, you
> could have an LED dedicated to OpenVPN traffic only for instance. Or
> you could have a couple of LEDs for different classes of traffic,
> which would tell you at a glance whether your device is being hammered
> by HTTP traffic or BitTorrent transfers.
>
> Hopefully once more devices start appearing in the LED class, having
> a target like this will help people put them to good use.
Well, its better than the patch from one or two years ago that
added LED-triggers to netif_receive_skb() or dev_queue_xmit() :)
I don't have a problem taking this patch if the LED-people agree
that this is a good approach.
prev parent reply other threads:[~2008-11-12 11:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 11:31 [PATCH 1/2 v2] New netfilter target to trigger LED devices Adam Nielsen
2008-11-11 12:19 ` Jan Engelhardt
2008-11-12 10:32 ` Adam Nielsen
2008-11-12 11:01 ` Jan Engelhardt
2008-11-12 11:10 ` Adam Nielsen
2008-11-12 11:53 ` Jan Engelhardt
2008-11-12 10:42 ` Pablo Neira Ayuso
2008-11-12 11:06 ` Adam Nielsen
2008-11-12 11:17 ` Patrick McHardy [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=491ABB51.7010500@trash.net \
--to=kaber@trash.net \
--cc=a.nielsen@shikadi.net \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.