The LED control page lets you manually control the physical indicator lights on your router and assign trigger behaviors that reflect network or system activity. Changes write directly to the LinuxDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/KevinCruz-cell/Redes-de-comunicaciones-/llms.txt
Use this file to discover all available pages before exploring further.
sysfs interface and take effect immediately.
Navigate to /router4/leds to access this page.
Available LEDs
The page manages five LEDs. Brightness and current trigger are read on every page load.| LED identifier | Color | Typical purpose |
|---|---|---|
green:lan | Green | LAN port activity |
green:wan | Green | WAN connection status |
green:wlan | Green | Wi-Fi activity |
mt76-phy0 | — | MT76 wireless radio (PHY0) activity |
orange:wan | Orange | WAN error or secondary WAN state |
Actions
Turn on
Sets brightness to maximum (255):Turn off
Sets brightness to zero:Set trigger
Assigns a kernel trigger that controls the LED automatically based on system events:Available triggers
| Trigger | Description |
|---|---|
none | No automatic control — brightness is set manually |
netdev | Blinks on network device activity |
phy0rx | Blinks on wireless receive activity (PHY0) |
phy0tx | Blinks on wireless transmit activity (PHY0) |
timer | Blinks at a fixed interval |
heartbeat | Pulses like a heartbeat to indicate the system is running |
Trigger and brightness settings written via
sysfs are not persistent across reboots. To make LED behavior permanent, configure it through UCI or an init script on the router directly.