What's new

Beta Asuswrt-Merlin 386.7 Beta is now available

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Status
Not open for further replies.
Are you running pixelserv- tls with diversion?
Yes. :rolleyes:
Update: Not the first time the AXE11000 has done this "lock up", earlier on 386.7 Alpha & 386.5 level. Disabled pixelserv-tls to see what now may occur. Thks.
 
Last edited:
Dirty flashed from Alfa to Beta on RT-AC68, everything working perfectly,,, any clues at to what would cause these in Logs? :


Jun 13 23:37:46 acsd: selected channel spec: 0xe03a (52/80)
Jun 13 23:37:46 acsd: Adjusted channel spec: 0xe03a (52/80)
Jun 13 23:37:46 acsd: selected channel spec: 0xe03a (52/80)
Jun 13 23:37:46 acsd: acs_set_chspec: 0xe03a (52/80) for reason APCS_CSTIMER
Jun 13 23:39:05 roamast: [EXAP]Deauth old sta in 0 0: 1C:14:B0:23:6E:D3
Jun 13 23:39:05 roamast: eth1: disconnect weak signal strength station [1c:14:b0:23:6e:d3]
Jun 13 23:39:05 roamast: eth1: remove client [1c:14:b0:23:6e:d3] from monitor list
Jun 14 01:47:27 acsd: selected channel spec: 0xe02a (36/80)
Jun 14 01:47:27 acsd: Adjusted channel spec: 0xe02a (36/80)
Jun 14 01:47:27 acsd: selected channel spec: 0xe02a (36/80)
Jun 14 01:47:27 acsd: acs_set_chspec: 0xe02a (36/80) for reason APCS_CSTIMER
 
That is the Auto settings used to pick the Control Channel used, along with the Channel Bandwidth.
 
After disable-enable switch routine, like 5-6-7 times, I managed to fetch IPv6.
Works.
I guess some kind of a bug in Merlin's Beta.
To be checked
I've found (here in Canada on my DSL over phone lines ISP with native v6) it's often best to reboot the modem when the outer needs rebooting. and to let the modem completely boot and settle for a moment before booting the router.
 
hope ASUS will allow us to use 2.5G WAN as LAN in GT-AX6000. 2.5G WAN is meaningless for 99% consumer. Fingers Crossed
 
Hello, AC88U here. I got this on log every few hours, i dont know why.

Jun 14 15:00:32 WAN_Connection: Fail to connect with some issues.
Jun 14 15:00:32 DualWAN: skip single wan wan_led_control - WANRED off
Jun 14 15:02:03 WAN_Connection: WAN was restored.
 
Flawless Upgrade: 386.5_2, flashing 386.7 on top of it with a dirty upgrade.
Thanks, Merlin!!
 
No its not when you reboot using the reboot button it counts to 100% not 6%.
The router goes offline partway through the "System REBOOT" cycle. This has always been the case (i.e., counting up to some percentage much less than 100%) as long as I have been using AiMesh.
 
IPv6 "native" and "stateless" with comcast working without issues.
DNS filtering "enabled" and no issues.
I haven't attempted OpenVPN Server (yet), but running wireguard/Pi-Hole without issues.
 
Adding the IPv6 column to the DNS Filter page makes dealing with conflicting IPv6 and IPv4 geolocations (thanks to having different clients use tunnel broker and a SmartDNS on the same network) sooo much easier!
 
Upgrade RT-AX88U & RT-AC3100 from V386.5_2 Final to V386.7 Beta1 via dirty firmware upgrade. 40+ devices (includes gaming, streaming, downloads, many IOT devices, etc.) and all appears to be working for main AX88U & backup AC3100 routers. Still postponing adding RT-AX58U with V386.5 XXX into AiMesh 2.0, until Guest Network #01 issue is fixed, as Guest network is #01, and IOT devices is #02 currently in my setup.
 
Beta 1 appears to have resolved my constant issues with DNS over TLS on my RT-AC86U!! Usually within an hour of enabling it I'd loose most DNS resolution and have to disable it again. So far 24 hours and no problems. Hopefully it stays working after release. thx ;)
- Later that day it broke so I spoke too soon.
 
Last edited:
Running the beta since Sunday on all my routers and haven't seen any issues. Also, no problems running pixelserv -tls and diversion.
 
Upgrade RT-AX88U & RT-AC3100 from V386.5_2 Final to V386.7 Beta1 via dirty firmware upgrade. 40+ devices (includes gaming, streaming, downloads, many IOT devices, etc.) and all appears to be working for main AX88U & backup AC3100 routers. Still postponing adding RT-AX58U with V386.5 XXX into AiMesh 2.0, until Guest Network #01 issue is fixed, as Guest network is #01, and IOT devices is #02 currently in my setup.
Do you have the same IP's in your guest #2 clients as shown in the wireless log?
 
RT-AC86u (AiMesh with wireless backhaul between two rt-ac86u) upgraded today from 386.5_2 to 386.7_beta1. No severe issues only one observation - when I set my ipv6 dns server (local pihole) in LAN-DHCP page I get the following error:
Asus set the max length of that variable to 15 chars instead of 39, probably because it was copy/pasted from the IPv4 variable.

I cannot change length validation, so I reported the issue upstream.
 
Asus set the max length of that variable to 15 chars instead of 39, probably because it was copy/pasted from the IPv4 variable.

I cannot change length validation, so I reported the issue upstream.
@RMerlin despite the the asuswrt LTS edition, I will still utilize your custom scripts and leverage the best out of what your firmware offers despite the LTS web ui. I appreciate your current efforts and thank you for reporting this concern upstream.
 
Also the top LED still automatically turns on after reboot even it was OFF previously. Have to turn it off again on Auro RGB tab under System Status
I can't test it because my GT-AX11000 has no RGB. Can you see before and after the reboot what is the current value for aurargb_disable?

Code:
nvram get aurargb_enable
 
Status
Not open for further replies.

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top