So I was able to get this working…
The LED driver is loading under VyOS and indicated here:
ls -l /sys/class/leds/
lrwxrwxrwx 1 root root 0 Jan 15 14:30 apu4:green:led1 -> …/…/devices/pci0000:00/PRP0001:02/leds/apu4:green:led1
lrwxrwxrwx 1 root root 0 Jan 15 14:30 apu4:green:led2 -> …/…/devices/pci0000:00/PRP0001:02/leds/apu4:green:led2
lrwxrwxrwx 1 root root 0 Jan 15 14:30 apu4:green:led3 -> …/…/devices/pci0000:00/PRP0001:02/leds/apu4:green:led3
Once I found the above, I tried setting up triggering for eth0 and eth1 but the trigger file did not contain the netdev option.
[none] disk-activity disk-read disk-write ide-disk cpu cpu0 cpu1 cpu2 cpu3 panic mmc0
Doing some more searching I came across the LED info on the Arch Linux Wiki:
It led me to the section which talked about there being additional LED kernel modules which are not loaded by default and the netdev was one of them. After doing a “modprobe ledtrig-netdev”, the netdev showed up in the trigger file and I was able to follow sample setup in the wiki by updating the LED directory names and get the LED’s to show eth0 and eth1 traffic.
I added the ledtrig-netdev module to /etc/modules/modules.conf file, but have yet to test to see if it persists after updates or if there is somewhere else I need to add it.
For the Wierguard tracking, I will probably end up running a ping script or something to trigger the LED where if ping is successful, turn the LED on and if it fails, then turn it off.
Hopefully this will help some others on getting the LED’s working under VyOS.