Netgate SG-3100 LEDs

lohphat

Because my SG-3100 is out in the open the flashing blue LED is distracting, so I simply entered a cron entry to turn the LED off after 20 minutes post-startup.

*/20 	* 	* 	* 	* 	root 	/usr/sbin/gpioctl 2 duty 0

tjsober

I just set up my new SG-3100 and all seems to be working fine. The right side diamond LED slowly flashes. However when I go to Diagnostics - Halt System and the system shuts down, I lose my connection as expected but the LED continues to slow-blink. I was expecting it to shut off. Is this normal?

jimp

@tjsober said in Netgate SG-3100 LEDs:

I just set up my new SG-3100 and all seems to be working fine. The right side diamond LED slowly flashes. However when I go to Diagnostics - Halt System and the system shuts down, I lose my connection as expected but the LED continues to slow-blink. I was expecting it to shut off. Is this normal?

There is an issue we're addressing on 2.4.4 where the OS is not completely halting on shutdown that may be related. The fix is partially in snapshots now but should be completely done shortly.

msf2000

I observe the same behavior of the last blue LED.... system shutdown does not stop the LED slow flashing. As a workround, i use ssh to shutdown if needed, which allows me to see when the OS is actually halted.

I agree with @tjsober that it would be helpful if the last blue LED went dark once the system was properly halted. Perhaps this is something the watchdog timer can do?

msf2000

@wgstarks

Got a working tcsh shell script. It updates the left LED to green, amber, red, or blue, depending on the gateway status of the WAN port. Should be easy to customize.

#!/bin/tcsh
#
# This script updates the SG-3100 device's first LED with gateway status
#
#   php /usr/local/sbin/pfSsh.php playback gatewaystatus
#
set gw = `/usr/local/bin/php /usr/local/sbin/pfSsh.php playback gatewaystatus | grep WAN `
set gwping = `echo $gw | awk '{ ORS="  "; print $6 }' `
set gwstatus = `echo $gw | awk '{ ORS="  "; print $7 }' `

# based on gwstatus, set color of first LED
# led a  -  led b  -  led c
# 6 7 8  -  3 4 5  -  0 1 2 

switch ($gwstatus)
case "none":
case "Online": 
    /usr/sbin/gpioctl 6 duty 0
    /usr/sbin/gpioctl 7 duty 128
    /usr/sbin/gpioctl 8 duty 0
    breaksw
case "down": 
case "Offline":
    /usr/sbin/gpioctl 6 duty 128
    /usr/sbin/gpioctl 7 duty 0
    /usr/sbin/gpioctl 8 duty 0
    breaksw
case "highloss":
case "loss": 
case "highdelay":
case "delay":
case "Warning": 
    /usr/sbin/gpioctl 6 duty 128
    /usr/sbin/gpioctl 7 duty 32
    /usr/sbin/gpioctl 8 duty 0
    breaksw
default:
    /usr/sbin/gpioctl 6 duty 0
    /usr/sbin/gpioctl 7 duty 0
    /usr/sbin/gpioctl 8 duty 128
endsw

wgstarks

@msf2000 said in Netgate SG-3100 LEDs:

@wgstarks
Got a working tcsh shell script.

How/where should I install this? Needs to run at boot I'm guessing?

msf2000

@wgstarks

Yes, upload the shell script as a file. (Root's home directory is fine.) Then, install the "Cron" package. Add the shell script as a cron job to run every minute.

wgstarks

@msf2000
Thanks. Looks like it's working.

dpasadis

@wgstarks It would be great if the lights could serve 2 purposes:
(1) show boot status during a power-on or reboot (like they do now)
(2) show network activity on 3 network segments the rest of the time (WAN, LAN, OPT1)

If #2 was implemented, a glance at the firewall would tell us a lot about what's going on. It would be greatly appreciated.

wgstarks

@dpasadis said in Netgate SG-3100 LEDs:

@wgstarks It would be great if the lights could serve 2 purposes:
(1) show boot status during a power-on or reboot (like they do now)
(2) show network activity on 3 network segments the rest of the time (WAN, LAN, OPT1)

If #2 was implemented, a glance at the firewall would tell us a lot about what's going on. It would be greatly appreciated.

This isn’t my code. It was provided by @msf2000.

msf2000

@dpasadis

You could install the "ShellCmd" package and have the LED script run on bootup, if you'd like.
Just rotate the device 180 degrees, and you'll see the network traffic. ;)

The script I wrote was more for users to see that the firewall is working, instead of power-cycling the pfsense unnecessarily when their internet is slow.

dpasadis

Thanks msf2000. I appreciate your contribution.

I like your first suggestion (and your second for different reasons).

I've done a lot of work on operating systems, including Unix/Linux, so I might be able to figure out #1 without spending a crazy amount of time on it. If I get a good result, I'll share it here.

Mr_AJ

Cool thread!

z4xh

I wrote some more comprehensive documentation on my blog, which explains the timings in more depth. https://www.zacharyschneider.ca/blog/post/2019/12/customizing-leds-netgate-sg-3100

Hope it helps!

jchonchi

I took some of the information in this article and wrote a script that sets the LED colors based on network interface state and bandwidth usage.

KnowbuddyYuno

@jchonchi Sounds useful. Does the script work as intended?

I'm a complete moron when it comes to coding, so my risk tolerance is near zero.

styxl

@jchonchi i am using the script, works like charm. Thanks

jchonig

Very helpful thread.

I re-wrote msf2000s script as a sh script and generalized it a bit.

I use the left (circult) and middle (square) LEDs to monitor my two WAN connections.

I also toned it down a bit so I don't need sunblock.

You can find it here

bldnightowl

@msf2000 This was working for a long time in 2.4.5 -- but doesn't seem to anymore in 21.02.

wgstarks

@bldnightowl said in Netgate SG-3100 LEDs:

@msf2000 This was working for a long time in 2.4.5 -- but doesn't seem to anymore in 21.02.

After reading the release notes I’m guessing this is the reason-


Several abandoned and deprecated packages have been removed, including:

OpenBGPD (use FRR instead)
Quagga OSPF (use FRR instead)
routed
blinkled
gwled