Fwiw, the default LED configuration for the Meraki MR24:
config led 'led_wlan1'
option name 'WLAN1'
option sysfs 'mr24:green:wifi1'
option trigger 'phy0assoc'
config led 'led_wlan2'
option name 'WLAN2'
option sysfs 'mr24:green:wifi2'
option trigger 'phy0assoc'
config led 'led_wlan3'
option name 'WLAN3'
option sysfs 'mr24:green:wifi3'
option trigger 'phy0assoc'
config led 'led_wlan4'
option name 'WLAN4'
option sysfs 'mr24:green:wifi4'
option trigger 'phy0tpt'
On Mon, Dec 30, 2019 at 3:22 PM Mike C. <[email protected]> wrote:
> >
> > In this case, it's OpenWrt, not Meraki's software. I am not sure the
> > wifi LEDs are doing anything.
>
>
> I worked for a WiFi AP company in downtown Portland a few years ago. The
> APs ran OpenWrt and used similar LEDs for signal strength, peering,
> error/fault indication.
>
> OpenWrt refers to these as "default LEDs.
>
> The leds section contains settings that apply to non-default leds
>
> "(default leds are usually “power connected” led, “system alive” led, leds
> showing ethernet port activity and leds showing wifi radio status. Their
> settings are defined somewhere else, see development guides)"
>
> Based on that paragraph, Openwrt seems to fully support standard WiFi radio
> status LED functionality across the board.
>
> Refer to:
>
> https://openwrt.org/docs/guide-user/base-system/led_configuration#wifi_activity_triggers
>
>
> Fun fact! You can even have the LEDs signal a message using Morse Code!
>
> Morse Code
>
> The LED signals a message using Morse code. If not installed already,
> install it with:
> _______________________________________________
> PLUG mailing list
> [email protected]
> http://lists.pdxlinux.org/mailman/listinfo/plug
>
_______________________________________________
PLUG mailing list
[email protected]
http://lists.pdxlinux.org/mailman/listinfo/plug
