What's new

Beta Asuswrt-Merlin 388.2 Beta is now available for Wifi 6 models

  • 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.
@Indi
Did you ever do a setup with a factory reset after flashing beta2?
Please add a signature with you router model
 
Running on beta2 from not long after it was published. Networking seems to be stable. Still had the UI crashing but found out that when I removed a reverse proxy in front of it, the issues where gone. The reverse proxy was running on a synology nas which was pointing to https://<ip>:8443 of the router. The router does also have its own dns name with a Let's Encrypt cert and DDNS. Maybe something was interfering with each other. Never had this issue before 388.2_x.

It can be reproduced with using the reverse proxy, and clicking through the UI randomly. It can take minutes befor it happens. When the crash has occured the following is logged:

Code:
Apr 10 15:07:55 kernel: potentially unexpected fatal signal 11.
Apr 10 15:07:55 kernel: CPU: 2 PID: 8737 Comm: httpds Tainted: P           O    4.1.52 #2
Apr 10 15:07:55 kernel: Hardware name: Broadcom-v8A (DT)
Apr 10 15:07:55 kernel: task: ffffffc02d095540 ti: ffffffc023710000 task.ti: ffffffc023710000
Apr 10 15:07:55 kernel: PC is at 0x4d4c0
Apr 10 15:07:55 kernel: LR is at 0x4d484
Apr 10 15:07:55 kernel: pc : [<000000000004d4c0>] lr : [<000000000004d484>] pstate: 80010010
Apr 10 15:07:55 kernel: sp : 00000000ff9f8e10
Apr 10 15:07:55 kernel: x12: 00000000000c42c0
Apr 10 15:07:55 kernel: x11: 0000000000000001 x10: 00000000ff9f907b
Apr 10 15:07:55 kernel: x9 : 000000000074f168 x8 : 0000000000000000
Apr 10 15:07:55 kernel: x7 : 00000000ff9f8f34 x6 : 00000000ff9f907e
Apr 10 15:07:55 kernel: x5 : 00000000f721eab8 x4 : 0000000000000000
Apr 10 15:07:55 kernel: x3 : 00000000000a0fe6 x2 : 00000000e1fbec00
Apr 10 15:07:55 kernel: x1 : 00000000000006b1 x0 : 0000000000000000
Apr 10 15:08:13 watchdog: restart httpd
Apr 10 15:08:13 rc_service: watchdog 1721:notify_rc stop_httpd
Apr 10 15:08:14 rc_service: watchdog 1721:notify_rc start_httpd
Apr 10 15:08:14 RT-AX86U: start https:8443
Apr 10 15:08:14 RT-AX86U: start httpd:80
Apr 10 15:08:14 httpd: Succeed to init SSL certificate...8443
Apr 10 15:08:14 httpd: Succeed to init SSL certificate...80
 
Last edited:
It can be reproduced with using the reverse proxy, and clicking through the UI randomly. It can take minutes befor it happens. When the crash has occured the following is logged:
What "reverse proxy"?
 
Just my observations.......may just be my unit but........

Previously had to use Asus beta FW for a stable router.
Lately the Official release 388.22525 has been the most stable release to date for me.
Every other release lost wan/lan even Merlins.

Just tried 388.2 beta2 and it crashes wan/lan like all previous problem FW's for me and also had a problem giving out IP's.
The wifi5ghz seemed weak as my TV couldn't see it,reverted back to 22525 and it connects np.
22237 was a crasher for me but 22525 is stable

syslogs attached are from stable to 388.2beta2 back to stable
Looked over the logs, gotta admit they looked similar to mine. Noticed that the 2.4Ghz and 5Ghz are bouncing around channels and bandwidth 80/160 before things start to go south between one MAC and the router just before the reboot.

What I've done and it's worked well for me is to fix channels, pick one instead of auto.
Auto worked well for me under 384/386 families but under 388, setting the radios to fixed channels has solved a lot of WiFi instability issues.
The WiFi driver being used by ASUS in this GPL seems to be a little more sensitive to radar/interference too. My 5Ghz radio is almost always on 36/100 at 160mhz but occasionally will flip to 149 at 80Mhz before switching back, which is how it's supposed to work.

The other thing, that's hidden from the logs, at least the ones I can see, is IPV6. I've had to disable it for now. Made my router sluggish in this release, on and off with some wired results on WiFi, GUI very sluggish/crashing, Router Ookla speedtest results acting weird, packet losses, and assigning multiple IPv6 addresses or none, to my devices, before the router giving after a few back to back "Router kernel: Hardware name: Broadcom-v8A (DT)" and rebooting.

Since doing both of these, so far so good. 100% with no weird speedtest results or packet loss or GUI crashs and all the scripts I use running.
 
Not sure what to call this but its not accurate. I have an NAS connected via lan port aggregation/trunking. In other words wired. The router reports it connected wirelessly although there's no wireless stats. See pix.

Screenshot 2023-04-10 142703.jpg
 
I may be way out here but is the NAS connected to an ap/mesh node?
 
Not sure what to call this but its not accurate. I have an NAS connected via lan port aggregation/trunking. In other words wired. The router reports it connected wirelessly although there's no wireless stats. See pix.

View attachment 49208
Network Map issue. Is present in the Asus firmware, too.
 
Network Map issue. Is present in the Asus firmware, too.
My ax86u router is correctly reporting my port-aggregated qnap connection as wired.
 
I'm just reporting this as something I noticed. I can easily work around this issue but in one of the alpha threads I saw someone having the same issue. I have been doing this to put several devices in the same domain without the browser saying it is insecure or I need to use ports like 8443. Maybe it helps if you publish the final release and you get more of these reports. Can't imagine that I'm the only one doing this, but maybe I do. Let's move on to the more important stuff :)
 
Last edited:
Running on beta2 from not long after it was published. Networking seems to be stable. Still had the UI crashing but found out that when I removed a reverse proxy in front of it, the issues where gone. The reverse proxy was running on a synology nas which was pointing to https://<ip>:8443 of the router. The router does also have its own dns name with a Let's Encrypt cert and DDNS. Maybe something was interfering with each other. Never had this issue before 388.2_x.

It can be reproduced with using the reverse proxy, and clicking through the UI randomly. It can take minutes befor it happens. When the crash has occured the following is logged:

Code:
Apr 10 15:07:55 kernel: potentially unexpected fatal signal 11.
Apr 10 15:07:55 kernel: CPU: 2 PID: 8737 Comm: httpds Tainted: P           O    4.1.52 #2
Apr 10 15:07:55 kernel: Hardware name: Broadcom-v8A (DT)
Apr 10 15:07:55 kernel: task: ffffffc02d095540 ti: ffffffc023710000 task.ti: ffffffc023710000
Apr 10 15:07:55 kernel: PC is at 0x4d4c0
Apr 10 15:07:55 kernel: LR is at 0x4d484
Apr 10 15:07:55 kernel: pc : [<000000000004d4c0>] lr : [<000000000004d484>] pstate: 80010010
Apr 10 15:07:55 kernel: sp : 00000000ff9f8e10
Apr 10 15:07:55 kernel: x12: 00000000000c42c0
Apr 10 15:07:55 kernel: x11: 0000000000000001 x10: 00000000ff9f907b
Apr 10 15:07:55 kernel: x9 : 000000000074f168 x8 : 0000000000000000
Apr 10 15:07:55 kernel: x7 : 00000000ff9f8f34 x6 : 00000000ff9f907e
Apr 10 15:07:55 kernel: x5 : 00000000f721eab8 x4 : 0000000000000000
Apr 10 15:07:55 kernel: x3 : 00000000000a0fe6 x2 : 00000000e1fbec00
Apr 10 15:07:55 kernel: x1 : 00000000000006b1 x0 : 0000000000000000
Apr 10 15:08:13 watchdog: restart httpd
Apr 10 15:08:13 rc_service: watchdog 1721:notify_rc stop_httpd
Apr 10 15:08:14 rc_service: watchdog 1721:notify_rc start_httpd
Apr 10 15:08:14 RT-AX86U: start https:8443
Apr 10 15:08:14 RT-AX86U: start httpd:80
Apr 10 15:08:14 httpd: Succeed to init SSL certificate...8443
Apr 10 15:08:14 httpd: Succeed to init SSL certificate...80

I always avoid using my NAS to run other network services as it only increases the risk for NAS vulnerabilities and the valuable data stored on it. It’s best kept really locked down via its own firewall rules (internal IPs only) with minimal services to reduce the attack surface. There has been many vulnerabilities found on them in the last 1-2 years.
 
I always avoid using my NAS to run other network services as it only increases the risk for NAS vulnerabilities and the valuable data stored on it. It’s best kept really locked down via its own firewall rules (internal IPs only) with minimal services to reduce the attack surface. There has been many vulnerabilities found on them in the last 1-2 years.
Thanks for your concern, but these urls/dns names are for internal use only.
 
Just my observations.......may just be my unit but........

Previously had to use Asus beta FW for a stable router.
Lately the Official release 388.22525 has been the most stable release to date for me.
Every other release lost wan/lan even Merlins.

Just tried 388.2 beta2 and it crashes wan/lan like all previous problem FW's for me and also had a problem giving out IP's.
The wifi5ghz seemed weak as my TV couldn't see it,reverted back to 22525 and it connects np.
22237 was a crasher for me but 22525 is stable

syslogs attached are from stable to 388.2beta2 back to stable

Every Merlin release I have tried on XT8s have all dropped nodes/reverted to "weak connections". I'll try the official 22525, thanks.
 
"my port-aggregated qnap connection as wired."

That's great.

I've looked through setup options and don't see anything that would trigger the mis-read of wireless.
 
I updated my ax86u to beta 2 and my torguard vpn stopped working. It's making a connection but it says public ip is unknown. Has anyone else experienced this vpn issue?
 
I updated my ax86u to beta 2 and my torguard vpn stopped working. It's making a connection but it says public ip is unknown. Has anyone else experienced this vpn issue?
You log will tell you what the problem is.
 
Status
Not open for further replies.

Sign Up For SNBForums Daily Digest

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