I can also confirm GT-AX6000 has issue with 2.5G LAN LED remaining lit when LEDs are disabled.
The same here. The 2.5G LAN LED only switches off when I unplug the utp cable.
I can also confirm GT-AX6000 has issue with 2.5G LAN LED remaining lit when LEDs are disabled.
Channel utilisation was not working properly on wifi SoC that use the WL interface, only on the more modern interfaces that use DHD. It was permanently reporting 100%, therefore it was disabled from these unsupported wifi interfaces. The RT-AX86U uses different Wifi chips for the 2.4 GHz and the 5 GHz, only the 5 GHz is supported. That's why it's showing on the 5 GHz but not on the 2.4 GHz. This is working as intended.Merlin did some adjustments right before building Beta 1 regarding utilization, so guess that made it disappear from a few models. Hope it can be fixed/reverted!
In a nutshell, the newer 3006 versions enable the new "extended" or "Pro" features that Asus is introducing: configurable VLANs, etc.Can anybody point me in the direction of resources to learn about the differences between 3004 and 3006 versions?
(are they linux kernel related? a move from k4.x to k6.x, for instance?)
I notice on the 'Addons/scMerlin' page, the temperatures are blank.
They appear on the 'Tools/SysInfo' page.
That problem is fixed with an update to scMerlin. The update is currently in beta. To try it out, check this post: https://www.snbforums.com/threads/s...rol-menu-for-asuswrt-merlin.67481/post-853223
Thanks. Had the same issue on alpha so that’s where I got 20% day. Not happening on 388.2.This firmware hasn't been out for 24 hours yet. Do you have a USB drive attached to the router? Monitor the size of thenetworkmap
process usingtop
.
Jul 27 22:41:38 acsd: eth6: Selecting 5g band ACS policy
Jul 27 22:41:38 acsd: acs_init_run(1111): acs_start eth6 cannot select chanspec with the wrong info
Jul 27 22:41:41 acsd: eth6: Selecting 5g band ACS policy
Jul 27 22:41:41 acsd: acs_init_run(1111): acs_start eth6 cannot select chanspec with the wrong info
Jul 27 22:41:44 acsd: eth6: Selecting 5g band ACS policy
Jul 27 22:41:44 acsd: acs_init_run(1111): acs_start eth6 cannot select chanspec with the wrong info
Jul 27 22:41:47 acsd: eth6: Selecting 5g band ACS policy
Updating the Linux kernel is impossible on these routers, the kernel they ship with is the only kernel they will ever run as it's tied to Broadcom's SDK.Can anybody point me in the direction of resources to learn about the differences between 3004 and 3006 versions?
(are they linux kernel related? a move from k4.x to k6.x, for instance?)
Yes it does work in the Alpha I can confirm.Strange. The alpha1 version showed real values in the formatted display
It means the router isn't aware that your DDNS is up to date, so it gets re-started by the watchdog. What's in your ddns-start script?But those watchdog spamming events are the first time I'm seeing them.
It means the router isn't aware that your DDNS is up to date, so it gets re-started by the watchdog. What's in your ddns-start script?
inadyn --once -f "/jffs/inadyn.conf" -e "/sbin/ddns_custom_updated 1" --continue-on-error "/sbin/ddns_custom_updated 1"
This is normal. If your ddns update does not set the ddns_updated nvram to 1, then the watchdog is going to call it again. This is what the "-e "/sbin/ddns_custom_updated 1"" parameter is for, it sets the variable to 1 to inform the watchdog that the update was completed.Edit 2 - even if I comment that inadyn line, ddns-start keeps being called every 30 seconds with my IP as arg
nvram get ddns_updated
--loglevel=debug
Channel utilisation was not working properly on wifi SoC that use the WL interface, only on the more modern interfaces that use DHD. It was permanently reporting 100%, therefore it was disabled from these unsupported wifi interfaces. The RT-AX86U uses different Wifi chips for the 2.4 GHz and the 5 GHz, only the 5 GHz is supported. That's why it's showing on the 5 GHz but not on the 2.4 GHz. This is working as intended.
I haven't tested that specific model. The reports of invalid values were all happening on wl-based radios, so I assumed that all wl-based radios were equally affected. It's possible that the RT-AX58U, being based on a newer SDK, might properly support it even on that older API. I will need to confirm that.And what about the RT-AX58U? From what I could tell, 2.4 GHz utilization does report accurately and not stuck at 100% like the RT-AX86U
Thanks for the help and explanation.This is normal. If your ddns update does not set the ddns_updated nvram to 1, then the watchdog is going to call it again. This is what the "-e "/sbin/ddns_custom_updated 1"" parameter is for, it sets the variable to 1 to inform the watchdog that the update was completed.
What's the content of ddns_updated?
Code:nvram get ddns_updated
Also, try enabling debugging in inadyn to confirm it does not exit with an error (some providers can incorrectly return a "200 OK" but contain an error message, which will confuse inadyn). Add this:
Code:--loglevel=debug
Then review the content of syslog after the next update.
Thanks for the help and explanation.
nvram var has the value of 1, which is correct.
Regarding debug mode, I've reviewed the logs line by line and everything is correct. It returns a 200 OK https response, with no error attached.
It also compares my IP with the IP on that cloudflare hosted domain, and it sees that they both are the same.
Then, the nvram var is correctly populated with 1. Process completed, everything went fine, and then, after 30 seconds, ddns watchdog is called again.
@RMerlin I just sent you a pm (for the sake of private log content) with a pastebin link with the unfiltered logs. For me, everything's ok.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!