StanL
May 19, 2023, 3:13pm
1
I'm using a WAX202 router with two wan sources. One is connected via the WAN port and the other is over a vlan trunk on the LAN1 port as br-lan.9.
I would love to be able to set one of my LED to be controlled by VLAN 9 so I can tell when the connection fails. As it is, the LED only tells me of activity over the port in general, which is fairly useless.
Have a look here, it should help:
1 Like
StanL
May 19, 2023, 5:36pm
3
Sorry, but I don't see any mention of VLAN there.
It's easy to control a LED with the VLAN activity, but you want to turn it OFF "when the connection fails"?
You need a script for this. This subject has been discussed lately.
I am writing to request support for changing the WAN LED to amber when the internet connection is not present in my TP-Link Archer C6 V3 running OpenWRT. I have followed the instructions in the other forums but that didn't seems to be helping me.
I would be grateful if you could provide me with any advice on how I can resolve this issue. If there is any additional information I need to provide, please let me know.
Thank you for your time and consideration.
StanL
May 19, 2023, 6:23pm
5
Still, I want to change LAN1's port to only show activity for br-lan.9, not all activity.
Maybe it's possible with a script, but I still see no one mentioning a way of having an LED respond to a VLAN instead of all activity on that port.
On every router that I have used, the ports LED are controlled automaticaly. It may be possible to control them by directly adressing the GPIO. But it's tough , and you'll need documentation about your device. I had an issue once that is closed to your.
Hello all.
I have successfully compiled, installed and configured a custom LEDE 17.01.7 for a Netgear WNR3500v2 (not the L version). I was even able to unlock it's 64MB RAM, so the device works smoothly. It is meant to be just a backup device.
My question is related to the LEDs configuration.
The LAN and wireless LEDs are directly controlled by the broadcom chipset. The POWER and WAN LEDs are static orange. I would like to configure rules for the POWER LED (static green) and WAN LED (blinking…
StanL
May 19, 2023, 10:35pm
7
Thanks. That's above my skill set ATM.
2 Likes
And mine too. I understand the problem, and may find how to solve this, but it'll need a huge amount of time for such a tiny result. Not worthy.
StanL
May 20, 2023, 10:28am
9
Maybe I should move this to feature request then.
1 Like
Have a look at this as an example. As you can see it is possible to control LAN LEDs when you know the GPIO configuration.
committed 09:24PM - 20 May 23 UTC
The PHY name has been changed to "mt7530-0" since IRQ support
was added to MT753… 0 driver.
Fixes: f9cfe7af1f1f ("kernel: backport MT7530 IRQ support")
Signed-off-by: DENG Qingfang <dqfext@gmail.com>
(node names, added color, function+function-enumerator properties)
Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
Djfe
June 27, 2023, 10:01pm
11
The next release won't allow you to control the lan leds on most devices of the ramips-mt7621 target at all (in software)
committed 04:31AM - 08 Jan 23 UTC
The pins of the MT7530 switch that translate to GPIO 0, 3, 6, 9 and 12 has
got a… function, by default, which does the same thing as the netdev
trigger. Because of bridge offloading on DSA, the netdev trigger won't see
the frames between the switch ports whilst the default function will.
Do not use the GPIO function on switch pins on devices that fall under this
category.
Keep it for:
mt7621_belkin_rt1800.dts: There's only one LED which is for the wan
interface and there's no bridge offloading between the "wan" interface and
other interfaces.
mt7621_yuncore_ax820.dts: There's no bridge offloading between the "wan"
and "lan" interfaces.
Signed-off-by: Arınç ÜNAL <arinc.unal@arinc9.com>
Until the Linux Kernel brings the functionality to control/set up switch controlled LEDs (hw offloading)
Until then the switch will control them by default (showing activity only)
I just wrote down the reasons in another github issue
opened 08:46AM - 12 Jun 23 UTC
bug
### Describe the bug
Since 23.05-rc1 it is no longer possible to disable the LA… N Leds on the Netgear WAX202.
Under "/sys/class/leds/" I can see differences depending on the version.
With 22.03.x this was still possible and under /sys/class/leds there was also e.g. "green:lan1". The "green:lanX" directories no longer exist under 23.05-rc1.
Below are the differences of the directories between 22.03.5 and 23.05-rc1.
Output 23.05-rc1 version:
ls /sys/class/leds/
blue:net blue:wifi5g green:power green:wifi5g mt76-phy1 orange:lan2 orange:power
blue:wifi2g green:net green:wifi2g mt76-phy0 orange:lan1 orange:lan3
Output 22.03.5:
ls /sys/class/leds/
blue:net blue:wifi5g green:lan2 green:net green:wifi2g orange:lan1 orange:lan3
blue:wifi2g green:lan1 green:lan3 green:power green:wifi5g orange:lan2 orange:power
Unfortunately, the LAN LEDs cannot be deactivated via green:net.
### OpenWrt version
r23069-e2701e0f33
### OpenWrt target/subtarget
ramips/mt7621
### Device
Netgear WAX202
### Image kind
Official downloaded image
### Steps to reproduce
Upgrade from 22.03.5 with disabled LAN Leds to 23.05-rc1 and the LAN Leds are blinking
### Actual behaviour
LAN Led cannot be disabled and lights/flashes green as soon as a LAN cable is connected.
### Expected behaviour
LAN Led should be able to be deactivated again
### Additional info
_No response_
### Diffconfig
_No response_
### Terms
- [X] I am reporting an issue for OpenWrt, not an unsupported fork.
There are more accurate explanations somewhere in github issues, but this should suffice