What's new

Release Asuswrt-Merlin 388.1 is now available for all supported 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!

Update succesful from Beta2 to 388.1. All scripts working also.
 
Flashed new firmware. First I noticed is speedtest is not accured. When I test it through web speed is 945/500 like it should, and when I test it via router UI it's around 600-700 download and upload is 497Mbps
There have been problems with the speed test on these routers for a while now. It's well documented.
 
Is there any benefit with Merlin when running in AI Mesh AP mode?
Some people find that the stock Asus firmware works best on mesh nodes. That being said my mesh node is using Asuswrt-merlin and it works just fine.
 
Everything going fine here as well on my AX86U.

Just curious: Are there any changes from beta4?
Read the change log included with the firmware or visit the GitHub site for more detailed information.
 
Last edited:
Upgraded my GT-AXE11000 to 388.1. No changes were made to my configuration.

Using it in AP mode.

Now any clients on 5GHz are being disconnected after a few minutes.

The errors I see in the logs are:

Dec 4 12:51:44 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind XX:XX:XX:XX:XX:XX, status: 0, reason: Station requesting (re)association is not authenticated with responding station (9)
Dec 4 12:51:44 wlceventd: wlceventd_proc_event(486): eth7: Disassoc XX:XX:XX:XX:XX:XX, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 4 12:51:44 hostapd: eth7: STA XX:XX:XX:XX:XX:XX IEEE 802.11: disassociated


Clients on the 2.4GHz seem to be OK.

I need to go back to 386.7.2 as there are no issues on 5GHz with this version of the firmware.

Anyone else seen this kind of behavior?
In the first post of this thread it states:
I implemented some upgrade code that will at least fix/prevent the most problematic issues, but if you notice any odd behaviour following the upgrade, be ready to do a factory default reset, and to manually reconfigure your router.
Don't be afraid to follow his instructions here.
 
Read the change log included with e firmware or visit the GitHub site for more detailed information.
Your link to the commits section in GitHub nailed it. Thanks!
 
Noticed when I am connected to a wireguard VPN that the Bandwidth Monitor shows all my traffic (UP and Down) as UPload with zero download.
Disconnect the WG VPN and it goes back to normal with both Upload and Download values displayed.
Not a big issue just and observation.
 
Noticed when I am connected to a wireguard VPN that the Bandwidth Monitor shows all my traffic (UP and Down) as UPload with zero download.
Disconnect the WG VPN and it goes back to normal with both Upload and Download values displayed.
Not a big issue just and observation.
This is an long standing issue that I've known and experienced myself for years. Asus just hasn't fixed it or can't fix it.
 
Thanks,flashed dirty in ax88u works great,on wireguard vpn client there is no option to delete or reset the client,only disable enable how do i remove config from wrg1?
 
A good idea to run Asus factory firmware on the AiMesh nodes. And, do not force Ethernet backhaul as setting to wired backhaul can cause problems.
^this is a very good advice. put default fw to my mesh router, instantly solved both visual and ofc technical the connection between ax88u and ax86s. thank you very much ! also thanks for everyone involved in this dev that makes our life a little more .. fun :)

Image 002.png
 
My 58U and mesh 58U's all working great.
Thank You!
 
Thanks,flashed dirty in ax88u works great,on wireguard vpn client there is no option to delete or reset the client,only disable enable how do i remove config from wrg1?
Import another config file. There is no data clear feature, or default feature.
 
Dirty upgrade after 90 days from 386.7_2 to 388.1 on RT-AX3000 (aka RT-AX58U), power cycled after 30 minutes and smooth sailing after 12 hours. Thank you Merlin!
 
Thank you @RMerlin !

Probably not 388.1 related, but anyone having issue with Skynet? Flashed from 388.1 beta4, factory reset, manual/minimal configuration, saved config and jffs (but didnt reimport because i thought no scripts after reboot jffs), re-flash 388.1 and import saved config wihout jffs enabled.

Will move to add-on forum. Just curious if anyone having same issue
 
Thank you @RMerlin !

Probably not 388.1 related, but anyone having issue with Skynet? Flashed from 388.1 beta4, factory reset, manual/minimal configuration, saved config and jffs (but didnt reimport because i thought no scripts after reboot jffs), re-flash 388.1 and import saved config wihout jffs enabled.

Will move to add-on forum. Just curious if anyone having same issue
A reset to defaults erases the JFFS. Importing a save JFFS usually has no negative impact to router stability after a reset. Skynet uses space on your USB drive as well as Entware. This combined with JFFS being erased could have caused your Skynet issue.
 
A reset to defaults erases the JFFS. Importing a save JFFS usually has no negative impact to router stability after a reset. Skynet uses space on your USB drive as well as Entware. This combined with JFFS being erased could have caused your Skynet issue.
Working now - changing from NextDNS to Quad9 TLS. Odd. Maybe something to do with CG-Nat or iptables.
 
Dirty upgrade, all running fine : getting this in logs, any ideas?

Dec 4 13:12:37 bsd: bsd: Sending act Frame to XX:XX:XX:XX:XX:XX with transition target eth7 ssid XX:XX:XX:XX:XX:XX
Dec 4 13:12:37 bsd: bsd: BSS Transit Response: ifname=eth6, event=156, token=1e, status=4, mac=00:00:00:00:00:00
Dec 4 13:12:37 bsd: bsd: BSS Transit Response: STA reject
Dec 4 13:12:37 bsd: bsd: Skip STA:XX:XX:XX:XX:XX:XX reject BSSID

(macs XX out, but seem to be related to asus router)


Edit: seems to be google speaker related, all working ok so ignoring.
 
Last edited:
First of all, thanks to all the developers/members who contributed to this new update, especially @RMerlin.

Due to the AX56U's processor -if I'm not mistaken- the download bandwidth of my OpenVPN clients on my devices was decreasing. So the addition of the Wireguard client feature was a very good development for me.

My VPN provider provides a DNS address of 10.26.xx.xx for ad blocking (normally the DNS is 10.9.xx.xx). I used to be able to use ad-blocking DNS without any problems by adding the line "dhcp-option DNS 10.26.xx.xx" to the configurations of my 2 OVPN clients. The DNS IP addresses I saw on the DNS leak sites were the Public IP address that appeared on my OVPN clients.

This is where I have a problem -if this is a real problem-. When no OVPN clients are running and 2 Wireguard clients are running, or when OVPN-1 and WG-1 clients are running, the DNS redirects seem to be broken. When I set the DNS addresses on WG-1 and 2 to 10.26.xx.xx, WG-2's DNS queries are made from WG-1, or when I turn off WG-2 and run OVPN-1 ("exclusive" and "dhcp-option" DNS set to 10.26.xx.xx), OVPN-1's DNS queries are made from WG-1.

The new DNSFilter is set to "Enable" and "no redirection".

Everything else seems to be working fine.
 

Similar threads

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