However the necessary packages (+ additional packages I thought might be missing, which I came up with while trying to find an answer) are installed:
root@OpenWrt:~# opkg install kmod-ipt-led
Package kmod-ipt-led (4.14.63-1) installed in root is up to date.
root@OpenWrt:~# opkg install iptables-mod-led
Package iptables-mod-led (1.6.2-1) installed in root is up to date.
root@OpenWrt:~# opkg install kmod-ipt-led
Package kmod-ipt-led (4.14.63-1) installed in root is up to date.
root@OpenWrt:~#
Any ideas what the issue might be?
Thanks!
EDIT:
By the way: Manually adding netfilter-ssh via echo (as shown in the wiki article) doesn't work as well - I tried it already (even tried to edit the sys file directly - same result)
Hello lleachii,
thank your for investigating this. Please find my answers below.
You don't explain what LED you're trying to customize...I'm guessing you want to change the behavior of the switch WAN LED?
I would have assumed, that it does not matter, which LED I want to customize, as I can see that the triggers are equal on each of them; In case it does: /sys/class/leds/rango:white:sata
from your post above, there are LEDs available
Correct
you don't state what event you're trying to cause a trigger upon
I want to use netfilter-ssh (as stated in my initial post), but the trigger is not available, as seen in the initial post. I simply want the LED to be steady, when an SSH connection to the router is active.
If you're referring to an LED on the switch, it's likely not able to be customized
No, I don't want to configure an LED on the switch (assuming switch-LEDs are the ones showing the connectivity of WAN/LAN ports)
I'm totally lost as to why you think these would make a light work.
It is not about the LED, but about the missing trigger
I totally understood the general procedure of how to achieve it. The problem simply is, that these (=netfilter-ssh or for example your netfilter-banip) triggers are not available for any LED.
Please see the following example output for one LED:
As you can see manually setting the LED to a trigger, which is available for the LED, works perfectly fine.
My problem is basically, that I am missing these netfilter-* triggers and I don't understand whether it is possible to have them (or whether it is actually depended on anything particular [like hardware model or whatever - which I wouldn't assume however]) and if so, how to "get" them.
Yes, I understood that from the OP, which is why I gave an example with the [netfilter-banip] default addition to the LED trigger file. That is something I manually set and use on a mamba when I need the facility.
You do not "get" the netfilter-xxx triggers, you have to add them as a new default with the echo statement and a xxxx of your choosing. But, there is a bit of a chicken and egg issue, you cannot add the new netfilter-xxxx trigger to the LED trigger file until the iptable -j LED --led-trigger-id xxxx addition exists; I do not know why this is the case.
(even tried to edit the sys file directly - same result)