pfSense » pfSense Packages

The capability is you can take any rule ID you have that establishes a connection and you could configure it to be used to enable a LED with a selected color, from rules that have alias with full fleets of IP phones, to rouge laptops, or even devices you want to alarm you if they come online.

It could also be set up with the ability to provide knowledge of when not to reboot equipment do to high availability equipment being used during an unspecified time.

It could be tied into a ring doorbell so when a button is pushed it turns a LED on. The possibilities are endless.

In the 90s I remember so often all the instructors being told to log out for network servicing on their PC systems.

Today the network service would have complete knowledge when systems are no longer using a rule.

VPN connections,

Users logged in your server purchasing goods.

You could set it to any rule.

pfctl -vvss| grep '192.168.1.11' would work great too as it would be IP address based not rule based
also
pfctl -vvss| grep -e 192.168.1.18 -e 192.168.1.11

Multiple IP addresses and or multiple rules

Side note, I recently learned "The Air force one Executive Phone has a light on the back that lights up red when secure."

This kind of add on LED adapting feature would give PfSense the ability to have the red lights turn too for specific access control lists

I wonder if there is another way to do it maybe with the active state tables counters. Thanks for looking into this idea. I have to admit I was impressed that I got it to work correctly with the game system, I did not know efficiency could be degraded.

If anyone knows of a more efficient want to poll the state table, please let me know.

Have a good day

Different way to iterate the variable for multiple cases

You can also use the the case command to iterate over the variable I named state for any item you want to set up for led interactors

@#!/bin/sh
state=$( pfctl -vvss )
res=1
resb=1
case "$state" in
, rule 79)
res=0
;;
esac
case "$state" in
192.168.1.11)
resb=0
;;
esac
if [ $res = 0 ] && [ $resb = 0 ];
then
sysctl -q dev.gpio.2.led.1.pwm=1
gpioctl -f /dev/gpioc2 3 duty 50 >/dev/null
sysctl -q dev.gpio.2.led.2.pwm=1
gpioctl -f /dev/gpioc2 7 duty 0 >/dev/null
gpioctl -f /dev/gpioc2 6 duty 50 >/dev/null
elif [ $res = 0 ];
then
sysctl -q dev.gpio.2.led.1.pwm=1
gpioctl -f /dev/gpioc2 3 duty 0 >/dev/null
sysctl -q dev.gpio.2.led.2.pwm=1
gpioctl -f /dev/gpioc2 7 duty 0 >/dev/null
gpioctl -f /dev/gpioc2 6 duty 50 >/dev/null
elif [ $resb = 0 ];
then
sysctl -q dev.gpio.2.led.2.pwm=1
gpioctl -f /dev/gpioc2 7 duty 0 >/dev/null
gpioctl -f /dev/gpioc2 6 duty 0 >/dev/null
sysctl -q dev.gpio.2.led.1.pwm=1
gpioctl -f /dev/gpioc2 3 duty 50 >/dev/null
else
sysctl -q dev.gpio.2.led.1.pwm=1
gpioctl -f /dev/gpioc2 3 duty 0 >/dev/null
sysctl -q dev.gpio.2.led.2.pwm=1
gpioctl -f /dev/gpioc2 6 duty 0 >/dev/null
gpioctl -f /dev/gpioc2 7 duty 50 >/dev/null

fi@