However, not for the switch ports. Apparently there is another way to do this;
et robowr 0x0 0x18 0x1ff
et robowr 0x0 0x18 0x0
et robowr 0x0 0x1a 0x0
But when this gives me:
-sh: et: not found
Is there any other way to kill these LEDs? Or to get "et" (no idea what this is) on the router?
Also, NetGear seems to have support in their official firmware to turn the LEDs off, so there must be a way todo this. Thanks.
...trying tomato USB firmware made the trick, the command doesn't seems to be unavailable and I'm abe to switch off Ethernet leds...
...Those et commands run without error on the latest version (mine is 26160)...
Thank you for the tips guys - I was on an older build of DD-WRT (24200M). I'm up-to-speed on how to get the latest build for the R7000 now.
I'm also able to run the 3 et robowr commands now - however, what I'm finding is if the 1st ethernet port is connected to my media center, the corresponding LED comes on, if I go with one of the other 3 - it stays off.
I've got a switch in one of the other ports (with some connected devices on the other end), a receiver in another and an XBOX360 (though I didn't get around to turning it on).
So in short, my 2 remaining questions are:
Can someone share where I might best look to understand how the et robowr command works, and whether I could use it to turn each ethernet LED on / off individually.
Has anyone else noticed ethernet port 1's LED remaining active after running the sequence of LED off commands?
(If you choose to continue poke around at GPIO stuffs keep in mind that R7000 and your device are quite different.) _________________ reenignE esreveR
Resistance is NOT futile... It's Voltage divided by Current!
_.-:Curently Deployed Devices:-._
Loc_1.0: R6400 -- v3.0-r48494 std (03/15/22)
Loc_2.0: R6300v2 -- Kong PTB 35550M 03-28-2018
Loc_3.0: R6300v2 -- Kong PTB 35030M 02-19-2018
Loc_4.0: R6300v2 -- Kong PTB 28600M 12-31-2015 (Radios OFF) & 5 Ubiquity UniFi APs
Loc_4.1: E4200 -- BrainSlayer K2.6 30880
Others: too many others to list