Blacklistedcard
Senior Member
AX88U is fine
+1 its also there on my AX88U.
AX88U is fine
Beta 3 is running fairly smooth on my AC2900 (incl. Client networks 1 on 2,4 and on 5 GHz)
Strange thing is CPU temperature, it's reads about 15 degrees Celsius higher than it did on 384.19 without workload. Wifi temps seem OK.
i run LE in a docker container on a VM on my server, and if/when the cert renews it SSH's to the router and replaces the certs and restarts httpd. I recommend if anyone else really wants to use LE on their router they consider similar approaches - a docker container is much better maintained/updated that needing a new f/w when LE change somethingAsus first told me the fix was included in the last GPL they sent, and now they just told me it hasn't yet and they need to build newer GPLs.
Seriously guys, screw LE. There is no point in using a LE certificate on a router that is accessed over your LAN. LE in Asuswrt has been unreliable since day 1. It was buggy, then it broke when LE switched to ACMEv2, and now it broke again when LE switched to a new root certificate. Who knows what will break again 6 months from now... Everything works just fine with a self-signed certificate.
Hello. I would like to report a performance regression.
386.1 Beta 2 and beta 3 has Wi-Fi 6 performance regression on the ax86u.
On stock asus firmware as well as 386 beta 1, I’m getting 920+ mbps down (speed test on two different Wi-Fi 6 clients, about 8 feet from the router).
However, starting on beta2, and continued on to beta 3, Wi-Fi performance has degraded about 75-90 mbps. I just downgraded back to beta1 and performance instantly increased by 80 mbps. The Wi-Fi 6 client didn’t move at all. Nothing changed except the firmware running on the router.
Wifi is working fine with my own RT-AX88U and four wireless clients.
I am not worried. The kind of sophistication involved in this type of attack mean you generally target multi-billion dollar targets, not an open source project that has about 150K potential targets, most of which being home-based and therefore worth pennies at best.
If you are worried, feel free to scan the source code yourself, it's all on my Github.
Wifi is a closed source component which merlin has no access to the code.
So odd. I'm having the same connectivity issue with my AX88U. Wifi is fine, but I can no longer access internet from any client with beta 3. I'm at a loss as to why only some of us are seeing this problem. Reverting back to stock 386 solved the problem. Beta 2 did not have the issue.
Hi Merlin and hi all,
I installed the 386.1 beta 3 on my RT-AC86U, but I still have the problem above.
Is it a bug or is it just a problem with my router? How can I solve it?
Thank you very much.
Bye.
I have been pounding my AX88U with beta 3. No problems with my 23 clients connecting to the internet.
Maybe not exactly right
No one can check the binary files from asus, because there is no signature.
That is what makes it odd. At least 1-2 other people are reporting internet connectivity issues, but apparently many others are not having it. I wonder if something weird is going on with the address translation....
I also have this problem with Traffic Analyzer/Traffic Monitor/Statistics with RT-AC86U.
I reverted back to ASUS firmware 3.0.0.4.386_40451 which doesn't have the problem but would prefer to use Merlin!
rm /jffs/.sys/TrafficAnalyzer/TrafficAnalyzer.db
Stop Traffic Analyzer, delete the database, then restart it.
Code:rm /jffs/.sys/TrafficAnalyzer/TrafficAnalyzer.db
My first guess is some of these people failed to follow the instructions of doing a factory default reset after running an alpha firmware, so their WAN MTU is most likely invalid. They should check their MTU to ensure it`s set to 1500 (IP) or 1492 (PPPoE). They should also check any existing VPN client configuration issues.
DNS issues are also a likely cause. Too often I see people configuring no WAN DNS servers expecting DoT to be able to replace them. No WAN DNS = no NTP clock sync = no working TLS = no working DoT. WAN interface need to have at least one working DNS server configured.
Asus hasn`t made any significant code change to WAN handling in 41350, except for adding PPPoA support for DSL models, which should only affect DSL products.
Did you check the MTU on the WAN page after the upgrade? Set it for 1500, mine was blank after the upgrade. I also always restart the cable modem after a firmware upgrade.So odd. I'm having the same connectivity issue with my AX88U. Wifi is fine, but I can no longer access internet from any client with beta 3. I'm at a loss as to why only some of us are seeing this problem. Reverting back to stock 386 solved the problem. Beta 2 did not have the issue.
I would prefer to use Merlin too, but the difference in CPU temperature is huge. What could be causing that?
Thanks. I definitely did a complete factory default reset after I moved to the asus stock firmware, when they posted a 386 prod version for the AX88U. I'll check the MTU.
The only other change I noticed was with a new setting for secure Plugandplay in the WAN section. I'm not sure why that would be an issue.
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!