As long as there is a compliance packet arrives, LED lights on XY, this effect how to achieve?
I have a lot of ways to compare this: use log target to send kernel log, rsyslogd intercept, redirect to filter, invoke shell operation LED light. It's a lot of fun, but isn't that what UNIX advocates?
What is the most direct way? I think it should be to write an event target, as long as the match through the NetLink to the data packet to user space, with this event target, even log can be distributed through the listen daemon of user space, After all, printk out of the information is not finally through the syslog system call to get syslog daemon it?
Is it just because it's easier to maintain a timer because it doesn't make sense to go to the process event in the kernel? And, the name is not good, this problem I feel more serious, although it really does not affect the function. Even if I could design a kernel-state event mechanism to trigger and handle events, I would not assume that the mechanism was associated with any particular object, and the receiver of the event could of course be led, but wouldn't it be the horn, the power?
The flashing and extinguishing of LED lights has also become a iptables target, strong sweat
