What's new

Release Asuswrt-Merlin 3004.388.6 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!

Today I saw that I have the new version available
RT-AX86U_3004_388.6_2, I currently have the AX86U_3004_388.6, my surprise is that after Internet about 4 or 5 times the update (uploading the file manually) the router restarts but at no time does it appear that I have the new version 2 , it's like the new one doesn't apply, has this happened to anyone?
1.) Make sure you have downloaded the correct FW version for your model router
2.) Make sure you reboot your router first
3.) After it comes back up, make sure your external USB drive has been disconnected/unmounted through the UI
4.) Upload the firmware through the UI page

-or-

Just download MerlinAU, and let it do it all for you! :)
 
Since 388.6_2 I am struggling with these every few days:

Code:
Mar 20 11:27:33 pppd[4070]: No response to 10 echo-requests
Mar 20 11:27:33 pppd[4070]: Serial link appears to be disconnected.
Mar 20 11:27:33 pppd[4070]: Connect time 2835.2 minutes.
Mar 20 11:27:33 pppd[4070]: Sent 3033842545 bytes, received 3652098767 bytes.

After that the connection to the internet is gone. Although after a few seconds the connecting is automatically restored, it keeps irritating to lose my internet connection
 
I'm curious if any of you with wifi issues have tried the second build of 388.7_alpha1.

On my GT-AX6000 main/AP combo, I had zero wifi issues when updating from 388.6_beta1 to the second build of 388.7_alpha1. Also no wifi issues on my new RT-AX86U Pro main/AP combo which began operation using the second build of 388.7_alpha1. For both setups, wireless authentication is set to WPA2-Personal, and PMF is set to Disabled for both 2.4 GHz and 5 GHz.
 
I'm curious if any of you with wifi issues have tried the second build of 388.7_alpha1.
I haven't had any problems with the WiFi for 4 days.
2.4 GHz with WPA2 and PMF disabled. 5GHz with WPA3 and PMF enabled as it is mandatory.
 
I'm curious if any of you with wifi issues have tried the second build of 388.7_alpha1.

On my GT-AX6000 main/AP combo, I had zero wifi issues when updating from 388.6_beta1 to the second build of 388.7_alpha1. Also no wifi issues on my new RT-AX86U Pro main/AP combo which began operation using the second build of 388.7_alpha1. For both setups, wireless authentication is set to WPA2-Personal, and PMF is set to Disabled for both 2.4 GHz and 5 GHz.
You haven't said what issues you're having. Also, if you are indeed having issues, maybe post this to the alpha thread as it's not related to the 388.6 release.

EDIT
I see you have but no mention of problems there.
Post in thread '[ 3004.388.7 alpha 1 Build(s) ] Testing available build(s)' https://www.snbforums.com/threads/3...s-testing-available-build-s.89304/post-900741
 
Last edited:
You haven't said what issues you're having. Also, if you are indeed having issues, maybe post this to the alpha thread as it's not related to the 388.6 release.

No wifi issues with either of my setups. I was only suggesting that 388.7 alpha1 may be a solution to the wifi issue people described with 388.6_2.
 
Out of curiosity, I did a bit of reading on PMF and WPA3. It turns out that any newly certified wifi device must support WPA3 and require PMF for WPA3, so it seems that if WPA2/WPA3 is selected, then PMF should be set to "Capable".
 
Out of curiosity, I did a bit of reading on PMF and WPA3. It turns out that any newly certified wifi device must support WPA3 and require PMF for WPA3, so it seems that if WPA2/WPA3 is selected, then PMF should be set to "Capable".
For my 5ghz I have WPA2/WPA3 with PMF set to Capable. I have no wireless problems that I can detect.
 
For my 5ghz I have WPA2/WPA3 with PMF set to Capable. I have no wireless problems that I can detect.
Same setup here, all AX devices connected with WPA3. None of the WPA2 devices complain.
 
1.) Make sure you have downloaded the correct FW version for your model router
2.) Make sure you reboot your router first
3.) After it comes back up, make sure your external USB drive has been disconnected/unmounted through the UI
4.) Upload the firmware through the UI page

-or-

Just download MerlinAU, and let it do it all for you! :)
I have done all that and it hasn't worked
 
I have done all that and it hasn't worked
What does it do? What are the error messages? Can you show screenshots? Have you tried running MerlinAU?
 
allwise said:


This latest release (3004.388.6) breaks my GT-AX6000


I'm here to report 388.6_2 breaks my GT-AX6000 (as did 388.6).
(using rog version)

1. Breaks Aimesh outright - No existing nodes are recognized. Rollback to 388.4 restores node. (Single RT-AX3000 ainode running latest ASUS factory FW)
2. Breaks Blink - "sync module" does not connect. Blink has a "sync module" that connects normally over 2.4g wireless as 192.168.101.232. My home subnet is 192.168.1.x/24
3. dnsmasq broken: Flooded log with error below: Line 79 is dns-forward-max=5096. It is in fact repeated from above ~line 15

Apr 21 12:16:22 inadyn[3477]: [response_update]HTTP/1.1 200 OK^M Date: Sun, 21 Apr 2024 16:16:22 GMT^M Server: Apache^M Content-Length: 0^M Connection: close^M Content-Type: text/html; charset=UTF-8^M ^M
Apr 21 12:16:36 dnsmasq[3562]: illegal repeated keyword at line 79 of /etc/dnsmasq.conf
Apr 21 12:16:36 dnsmasq[3562]: FAILED to start up
Apr 21 12:17:06 dnsmasq[4234]: illegal repeated keyword at line 79 of /etc/dnsmasq.conf
Apr 21 12:17:06 dnsmasq[4234]: FAILED to start up
Apr 21 12:17:37 dnsmasq[4351]: illegal repeated keyword at line 79 of /etc/dnsmasq.conf
Apr 21 12:17:37 dnsmasq[4351]: FAILED to start up
Apr 21 12:18:08 dnsmasq[4439]: illegal repeated keyword at line 79 of /etc/dnsmasq.conf
Apr 21 12:18:08 dnsmasq[4439]: FAILED to start up


ALL issues restore to normal after rollback to 388.4
 
dnsmasq broken: Flooded log with error below: Line 79 is dns-forward-max=5096. It is in fact repeated from above ~line 15
That duplicate was added by you, not by the firmware. dnsmasq does not support duplicate keywords.

Review your custom config and installed scripts, and remove that duplicate entry you are adding.
 
Check your dnsmasq.conf file. I can't remember which version made the change, but there were some changes made to basic .conf files within the last several months where keywords that were previously defaulted and not in the basic .conf file were now included. I saw it in minidlna.conf. If you're using /usr/sbin/helper.sh and the pc_append function in .postconf files, be sure and precede it with a pc_delete for that same keyword, so you don't have duplicates. Sometimes the program will use the last value encountered in the .conf file, but not always.
 
Last edited:
That duplicate was added by you, not by the firmware. dnsmasq does not support duplicate keywords.

Review your custom config and installed scripts, and remove that duplicate entry you are adding.

Confirmed. I forgot about /jffs/configs where I had dnsmasq.conf.add file.
 

Similar threads

Sign Up For SNBForums Daily Digest

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