OpenWrt Forum Archive

Topic: Wrt1900AC v1 - WAN led doesn't work

The content of this topic has been archived on 21 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Hi.

I want to make the orange internet led ("mamba:amber:wan"), blink when there is internet traffic (tx rx), but it doesn't work. I'm I doin' something wrong? I'm using trunk 48016.

config led
        option default '0'
        option name 'WAN'
        option sysfs 'mamba:white:wan'
        option trigger 'none'

config led
        option default '0'
        option name 'WAN_AMBER'
        option sysfs 'mamba:amber:wan'
        option trigger 'netdev'
        option mode 'tx rx'
        option dev 'eth1'

PS: The white led doesn't work either.

(Last edited by angelos on 2 Jan 2016, 22:51)

I'm on my own build base trunk with kernel 4.1.13, and the orange wan light works fine. I just made the change in Luci with no problem.

Are you on the release candidate kernel (4.4.x RC)? because I think I remember reading about issues dealing with the lights.

@davidc502
I use the official release from downloads.openwrt.org (Dec. 31 2015, kernel 4.1.13).

I just noticed something which is also strange.
If I do a "/etc/init.d/network restart", sometimes (not always) the led (white or orange) turns on but doesn't blink, it just stays always on.

Are the devs aware of it or should I open a ticket?
Or just wait for a newer snapshot?

------

@ anomeome
So... I just wait for the fix?

(Last edited by angelos on 2 Jan 2016, 23:06)

angelos wrote:

@davidc502
I use the official release from downloads.openwrt.org (Dec. 31 2015, kernel 4.1.13).

I just noticed something which is also strange.
If I do a "/etc/init.d/network restart", sometimes (not always) the led (white or orange) turns on but doesn't blink, it just stays always on.

Are the devs aware of it or should I open a ticket?
Or just wait for a newer snapshot?

------

@ anomeome
So... I just wait for the fix?

If it's not a big deal you may want to hold off putting in a ticket.

By the way, it's the very far Right hand side light that should turn Orange and blink right? That's the one that's blinking orange for me.

I have not had this issue with 4.1, but I'm not currently using a trunk build. I have used the 4.1 trunk without issue in the past. I tried an arokh r48014-2 build yesterday that as far as I noticed had all leds were working. 4.1/nand

This is the second from the left I believe.

(Last edited by anomeome on 2 Jan 2016, 23:17)

OK guys, I'll think I'll wait for a newer build and see how it goes and if it's fixed.

Yes, I'm talking about the second from the left.
The last from left / first from right is the WPS which works fine, I put a timer and made it blink every one second.

My whole led config:

config led
    option default '0'
    option name 'POWER'
    option sysfs 'mamba:white:power'
    option trigger 'default-on'

config led
    option default '0'
    option name 'WAN'
    option sysfs 'mamba:white:wan'
    option trigger 'none'

config led
    option default '0'
    option name 'WAN_AMBER'
    option sysfs 'mamba:amber:wan'
    option trigger 'netdev'
    option dev 'eth1'
    option mode 'tx rx'

config led
    option default '0'
    option name 'WLAN_2G'
    option sysfs 'mamba:white:wlan_2g'
    option trigger 'phy0radio'

config led
    option default '0'
    option name 'WLAN_5G'
    option sysfs 'mamba:white:wlan_5g'
    option trigger 'phy1radio'

config led
    option default '0'
    option name 'USB2'
    option sysfs 'mamba:white:usb2'
    option trigger 'usbdev'

config led
    option default '0'
    option name 'USB3_1'
    option sysfs 'mamba:white:usb3_1'
    option trigger 'usbdev'

config led
    option default '0'
    option name 'USB3_2'
    option sysfs 'mamba:white:usb3_2'
    option trigger 'usbdev'

config led
    option default '0'
    option name 'ESATA'
    option sysfs 'mamba:white:esata'
    option trigger 'none'

config led
    option default '0'
    option name 'WPS'
    option sysfs 'mamba:white:wps'
    option trigger 'none'

config led
    option default '0'
    option name 'WPS_AMBER'
    option sysfs 'mamba:amber:wps'
    option trigger 'timer'
    option delayon '500'
    option delayoff '500'

(Last edited by angelos on 3 Jan 2016, 00:41)

The second one from the left doesn't blink unless it's trying to establish a connection. A solid amber light indicates a possible configuration issue or internet issue.

It's the far right had led that should blink with internet Activity or Traffic.

Second from left is wan/hearbeat/activity indicator

OK, here is a pic...
http://s9.postimg.org/5nm979iu7/1900acv1.jpg

I'm talking about the Internet led, which I want to make it blink when there is transmit/receive traffic.

(Last edited by angelos on 2 Jan 2016, 23:41)

Right (wait... left), which has worked on every build I've tried < 4.4rc.

(Last edited by anomeome on 2 Jan 2016, 23:45)

The far right hand side (Past the 4) is the up/down arrow -- that's the activity light for WAN.

Not being argumentative here -- lol

Uploading picture

(Last edited by davidc502 on 2 Jan 2016, 23:57)

OK, as I said before, I'll wait for a newer build and see how it goes.

A last question (at the moment).
To go to a newer snapshot...
Should I flash OEM firmware first and then OpenWrt again, or just use a sysupgrade image?
I think I've read that the factory image works too if I want to "jump" to a newer version, is it safe?

So david, your router flashes the wps led for wan activity? Is this your image, or did you mod the led setting? I did not think this was the default behaviour. The behaviour I've noticed with < 4.4 builds was the internet led coming on when a link was established, then solid(openwrt), and with stock firmware it blinks, but appears to be a heartbeat rather than an activity indicator.

I currently have to flash back to stock before moving forward with an openwrt image. This changed recently as I used to just flash forward openwrt images. YMMV

Cracks me up... When I think about it, I've only used Factory FW for a day or two before going to OpenWrt, and never looked back.. After some reading, yes that is the wps LED... the kinda up/down arrow, which I thought made perfect sense for "activity" LOL

So yes, it's the WPS, which I like better than the "Internet" light. Now, I have them both which is kind of cool.

Technically, my build is as "snapshot" of current trunk 4.1.13.

Thanks for pointing that out.

The below change in Luci is what gave me the blinking WPS LED for WAN Activity.

Reading below it does say "WPS" Doh!!!  I was wondering what the hell that meant when I chose it.

LED

(Last edited by davidc502 on 3 Jan 2016, 00:27)

So if you have working leds than the op should have them as well. This must be a configuration issue?

Here is what the blinking Orange WPS LED looks like.

LED

anomeome wrote:

So if you have working leds than the op should have them as well. This must be a configuration issue?

system config for WPS led to blink orange with WAN send/recieve.

config led 'led_wan'
        option name 'WAN'
        option trigger 'netdev'
        option dev 'eth1'
        option mode 'tx rx'
        option sysfs 'mamba:amber:wps'
        option default '1'

config if you want "WAN" light to blink Orange with WAN Transmit/Recieve

config led 'led_wan'
        option name 'WAN'
        option trigger 'netdev'
        option dev 'eth1'
        option mode 'tx rx'
        option default '0'
        option sysfs 'mamba:amber:wan'

(Last edited by davidc502 on 3 Jan 2016, 01:24)

Just an update to this, I was having the same problem with WAN led not working but with the WRT1900ACS v2 which is the same hardware as the WRT1900AC v2 (both taking the cobra image) with the only exception the CPU speed is faster in the ACS at 1.6Ghz.

I built my image from CC 15.05 source and in make menuconfig you need to select:
Kernel modules -> Led modules -> kmod-leds-pca963x
else after flashing you'll only see two leds in led config:
cobra:white:power and cobra:white:sata.

Now I have the whole lot and WAN led worked straight away.

This fire was put out a long time back. I don't know if you have a reason for hanging back at CC, but if so you should at least build to 15.05.1 and get the latest mwlwifi in your build. Since you do your own build, to take advantage of the HW (BM,CESA etc) available, I would suggest a move to DD or LEDE.

This is the first result that comes up in a google search for "wrt1900acs wan led", i'm hanging back with CC as its labeled as a stable version. Its actually 15.05.1 i'm using, but the git repo at dev.openwrt.org is labeled as 15.05 and seems to have all the patches etc...  I haven't had any problems with it and is stable for what i'm using it for with public wifi hotspots etc...

I'm waiting for LEDE to release a stable version too plus some of my hardware wont run Trunk/DD/LEDE with the packages I require due insufficient flash eg the tplink tl-wa801/901 series which only has 4mb, CC with my packages fits on these routers but only with something like < 50kb to spare.

Edit: I just tried the latest development version of LEDE and its the same you need to manually select kmod-leds-pca963x in make menuconfig when building for the WRT1900AC(S)

(Last edited by chessman on 28 Aug 2016, 01:04)

The discussion might have continued from here.