Release Asuswrt-Merlin 384.19 is now available

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.
Status
Not open for further replies.

RMerlin

Asuswrt-Merlin dev
Question though, did the OpenVPN Client Connection Retry attempts setting for infinite change from -1 to 0 ? It says "Connection Retry attempts (0 for infinite)" in the GUI but I have -1 set.
-1 was a bogus value. Unlimited should be set to 0 instead of -1, this was fixed with the OpenVPN rewrite.
 

dave14305

Part of the Furniture
Am concerned about the "REMOTE_CONNECTION_TURNED_ON" as the router remote connection is off in the Admin/System
I enable the setting “Disable Asusnat tunnel” to eliminate this daemon. Double-negative warning: enable the setting to disable the daemon. :)
 

ugandy

Senior Member
I enable the setting “Disable Asusnat tunnel” to eliminate this daemon. Double-negative warning: enable the setting to disable the daemon. :)
do we know what;s the use of the "asusnat tunnel"?
thx

EDIT: found this:
"Only enable Asusnat tunnel if you use IFTTT or Alexa or ASUS application on cell phones."
"ASUS NAT tunnel make it possible to access router in the wan side of router, even under NAT."
"Some features use it, such as ASUS router APP."
 
Last edited:

JT Strickland

Senior Member
I'm almost ashamed to tell this on myself, but I didn't think I hit the "apply" button at the bottom when I selected to format the jffs on next boot. I guess because the check change got a couple of router responses it was good to go. Wrong. I can't believe I made such a rookie mistake. Wait a minute, I am a rookie. Regardless, that was a very stoopid one.

Everything seems to back up or on the way to recovery now, and I am sure glad. Got a new usb drive out of it.
Thanks for the upgrade, Merlin and associates, and Thanks for the help, Everybody!
Rest of you rookies, don't forget to hit that apply button!
 

truglodite

Regular Contributor
Well I seemed to have run in to bad luck upgrading my ac86u to .19 today. After rebooting I can't even log into the webgui, as it keeps acting weird with invalid certs and improperly loading pages... now I even have an improperly loaded captcha keeping me out. I can ssh in still, but none of my scripts are working. I took a backup of jffs before upgrading.

Untitled.png


How do I procede from here to fix this partially bricked 86u?

Thanks,
Kevin

[edit: I tried removing the usb drive and rebooting... still not working. Please help... kids distance learning means we are really depending on this damn thing to work well.]
 
Last edited:

Hawk

Senior Member
Eric, I just wanted to confirm regarding low space warning on JFFS, did you manage to fix it so it display different warning when unmounted. I am still getting low space warning when it is unmounted. I started by upgrading to 384.19 and then factory reset, after initial configuration I was getting message that it is low on space, instead of different message.

Also my system log is getting bombarded by these, looks like debugging, log level is set to notice and default log level is also notice.

Aug 16 14:57:34 kernel: CONSOLE: 073994.608 ampdu_dbg: wl0.0 b8:d7:af:69:7f:64 scb:00437af0 tid:0
Aug 16 14:57:34 kernel: CONSOLE: 073994.608 ampdu_dbg: wl0.0 dead_cnt 2 tx_in_transit 1 aqmqmap 0x41 aqmfifo_status 0x0
Aug 16 14:57:34 kernel: CONSOLE: 073994.608 ampdu_dbg: ifsstat 0xaf nav_stat 0x0 txop 92973
Aug 16 14:57:34 kernel: CONSOLE: 073994.608 ampdu_dbg: pktpend: 0 0 0 0 0 ap 1
Aug 16 14:57:34 kernel: CONSOLE: 073994.608 ampdu_dbg: txall 22 txbcn 20 txrts 0 rxcts 0 rsptmout 0 rxstrt 32
Aug 16 14:57:34 kernel: CONSOLE: 073994.608 ampdu_dbg: cwcur0-3 f f 7 3 bslots cur/0-3 3 0 0 0 0 ifs_boff 0
Aug 16 14:57:34 kernel: CONSOLE: 073994.608 ampdu_dbg: again1 ifsstat 0xaf nav_stat 0x0
Aug 16 14:57:34 kernel: CONSOLE: 073994.608 ampdu_dbg: again2 ifsstat 0xaf nav_stat 0x0
Aug 16 14:57:34 kernel: CONSOLE: 073994.608 wl0: wlc_ampdu_handle_ba_session_on: cleaning up ini tid 0 due to no progress for 2 secs tx_in_transit 1
Aug 16 14:57:41 kernel: CONSOLE: 052347.772 iov:SCB_DEAUTH
Aug 16 14:57:42 kernel: dhd_flow_rings_delete_for_peer: ifindex 0
Aug 16 14:57:42 kernel: dhd_prot_flow_ring_delete: Send Flow Delete Req RING ID 131 for peer 88:a4:79:50:37:4f prio 6 ifindex 0
Aug 16 14:57:42 kernel: dhd_prot_flow_ring_delete: Send Flow Delete Req RING ID 201 for peer 88:a4:79:50:37:4f prio 4 ifindex 0
Aug 16 14:57:42 kernel: dhd_prot_flow_ring_delete: Send Flow Delete Req RING ID 202 for peer 88:a4:79:50:37:4f prio 5 ifindex 0
Aug 16 14:57:42 kernel: dhd_prot_flow_ring_delete: Send Flow Delete Req RING ID 260 for peer 88:a4:79:50:37:4f prio 0 ifindex 0
Aug 16 14:57:42 kernel: dhd_prot_flow_ring_delete: Send Flow Delete Req RING ID 266 for peer 88:a4:79:50:37:4f prio 3 ifindex 0
Aug 16 14:57:42 kernel: dhd_prot_flow_ring_delete_response_process: Flow Delete Response status = 0
Aug 16 14:57:42 kernel: dhd_prot_flow_ring_delete_response_process: Flow Delete Response status = 0
Aug 16 14:57:42 kernel: dhd_prot_flow_ring_delete_response_process: Flow Delete Response status = 0
Aug 16 14:57:42 kernel: dhd_prot_flow_ring_delete_response_process: Flow Delete Response status = 0
Aug 16 14:57:42 kernel: dhd_prot_flow_ring_delete_response_process: Flow Delete Response status = 0
Aug 16 14:57:42 kernel: CONSOLE: 074003.225 wl0.0: wlc_send_bar: for b8:d7:af:69:7f:64 seq 0xca0 tid 0
Aug 16 14:57:42 kernel: CONSOLE: 052348.893 wl1: wlc_ratelinkmem_update_link_entry_onsize, 00428b24, 00429114, STA: 88:a4:79:50:37:4f Skip updating linkmem that is or will be deleted
Aug 16 14:57:42 kernel: CONSOLE: 052348.893 wl1: wlc_ratelinkmem_update_link_entry_onsize, 00428b24, 00429114, STA: 88:a4:79:50:37:4f Skip updating linkmem that is or will be deleted
Aug 16 14:57:42 kernel: CONSOLE: 052348.893 wl1: wlc_ratelinkmem_update_link_entry_onsize, 00428b24, 00429114, STA: 88:a4:79:50:37:4f Skip updating linkmem that is or will be deleted
Aug 16 14:57:43 kernel: CONSOLE: 052348.893 wl1: wlc_ratelinkmem_update_link_entry_onsize, 00428b24, 00429114, STA: 88:a4:79:50:37:4f Skip updating linkmem that is or will be deleted
Aug 16 14:57:43 kernel: CONSOLE: 074003.825 wlc_ap_authresp: status 0
Aug 16 14:58:06 kernel: CONSOLE: 052371.883 wl1: wlc_ratelinkmem_update_link_entry_onsize, 00428b24, 00429114, STA: 88:a4:79:50:37:4f Skip updating linkmem that is or will be deleted
Aug 16 14:58:34 kernel: CONSOLE: 052399.771 ampdu_dbg: wl1.0 44:4a:db:08:76:f3 scb:0042a9b4 tid:0
Aug 16 14:58:34 kernel: CONSOLE: 052399.771 ampdu_dbg: wl1.0 dead_cnt 2 tx_in_transit 1 aqmqmap 0x41 aqmfifo_status 0x0
Aug 16 14:58:34 kernel: CONSOLE: 052399.771 ampdu_dbg: ifsstat 0xaf nav_stat 0x0 txop 107165
Aug 16 14:58:34 kernel: CONSOLE: 052399.771 ampdu_dbg: pktpend: 0 0 0 0 0 ap 1
Aug 16 14:58:34 kernel: CONSOLE: 052399.771 ampdu_dbg: txall 10 txbcn 10 txrts 0 rxcts 0 rsptmout 0 rxstrt 91
Aug 16 14:58:34 kernel: CONSOLE: 052399.771 ampdu_dbg: cwcur0-3 f f 7 3 bslots cur/0-3 5 0 0 0 0 ifs_boff 0
Aug 16 14:58:34 kernel: CONSOLE: 052399.771 ampdu_dbg: again1 ifsstat 0xaf nav_stat 0x0
Aug 16 14:58:34 kernel: CONSOLE: 052399.771 ampdu_dbg: again2 ifsstat 0xaf nav_stat 0x0
Aug 16 14:58:34 kernel: CONSOLE: 052399.771 wl1: wlc_ampdu_handle_ba_session_on: cleaning up ini tid 0 due to no progress for 2 secs tx_in_transit 1
Aug 16 14:58:53 kernel: CONSOLE: 052418.694 addba timed out 0
Aug 16 14:58:54 kernel: CONSOLE: 052419.690 addba timed out 1
Aug 16 14:58:55 kernel: CONSOLE: 052420.686 addba timed out 2
Aug 16 14:58:55 kernel: CONSOLE: 052420.862 wl1.0: wlc_send_bar: for 44:4a:db:08:76:f3 seq 0xdef tid 0
Aug 16 14:59:28 kernel: CONSOLE: 074108.287 ampdu_dbg: wl0.0 b8:d7:af:69:7f:64 scb:00437af0 tid:0
Aug 16 14:59:28 kernel: CONSOLE: 074108.287 ampdu_dbg: wl0.0 dead_cnt 2 tx_in_transit 1 aqmqmap 0x44 aqmfifo_status 0x1
Aug 16 14:59:28 kernel: CONSOLE: 074108.287 ampdu_dbg: ifsstat 0xaf nav_stat 0x0 txop 98216
Aug 16 14:59:28 kernel: CONSOLE: 074108.287 ampdu_dbg: pktpend: 0 0 0 0 2 ap 1
Aug 16 14:59:28 kernel: CONSOLE: 074108.287 ampdu_dbg: txall 20 txbcn 20 txrts 0 rxcts 0 rsptmout 0 rxstrt 82
Aug 16 14:59:28 kernel: CONSOLE: 074108.287 ampdu_dbg: cwcur0-3 f f 7 3 bslots cur/0-3 9 0 0 0 0 ifs_boff 0
Aug 16 14:59:28 kernel: CONSOLE: 074108.287 ampdu_dbg: again1 ifsstat 0xaf nav_stat 0x0
Aug 16 14:59:28 kernel: CONSOLE: 074108.287 ampdu_dbg: again2 ifsstat 0xaf nav_stat 0x0
Aug 16 14:59:28 kernel: CONSOLE: 074108.287 FIFO-4 TXPEND = 2 TX-DMA4 =>
Aug 16 14:59:28 kernel: CONSOLE: 074108.287 wl0: wlc_ampdu_handle_ba_session_on: cleaning up ini tid 0 due to no progress for 2 secs tx_in_transit 1
Aug 16 14:59:28 kernel: CONSOLE: 074108.554 wl0.0: wlc_send_bar: for b8:d7:af:69:7f:64 seq 0xcb7 tid 0
 
Last edited:

Hawk

Senior Member
Well I seemed to have run in to bad luck upgrading my ac86u to .19 today. After rebooting I can't even log into the webgui, as it keeps acting weird with invalid certs and improperly loading pages... now I even have an improperly loaded captcha keeping me out. I can ssh in still, but none of my scripts are working. I took a backup of jffs before upgrading.

View attachment 25486

How do I procede from here to fix this partially bricked 86u?

Thanks,
Kevin

[edit: I tried removing the usb drive and rebooting... still not working. Please help... kids distance learning means we are really depending on this damn thing to work well.]
You best course of action would be factory reset, especially because you are not able to access GUI. I know not the most convenient method out there but it will get you going.


ASUS router Hard Factory Reset - Method 2

1. Turn the router off.
2. Press and hold the "WPS" button and turn the router on.
3. Power light is on (keep holding the WPS button).
4. Release the WPS button after the power light is off.
5. Reboot your router by manually pressing the power button.
6. Configure your router from scratch.
 

Diamond67

Senior Member
How exactly you do the dirty updates on the router?
Dirty update means that you don't reset the router settings after firmware update and start from scratch, but instead install the new firmware "on top of the current fw" and leave it that way without resetting. Normally that works nicely. But if you happen to have some weird problems after updating you could restore the router to its factory defaults.

You can read detailed instructions of how to dirty update from this message:

 

bbunge

Very Senior Member
Well I seemed to have run in to bad luck upgrading my ac86u to .19 today. After rebooting I can't even log into the webgui, as it keeps acting weird with invalid certs and improperly loading pages... now I even have an improperly loaded captcha keeping me out. I can ssh in still, but none of my scripts are working. I took a backup of jffs before upgrading.

View attachment 25486

How do I procede from here to fix this partially bricked 86u?

Thanks,
Kevin

[edit: I tried removing the usb drive and rebooting... still not working. Please help... kids distance learning means we are really depending on this damn thing to work well.]
I've just had too many issues with my AC86U today on 386.19 even after several factory resets and manual reconfigures. Just went back to Asus 384.81992. Happy router...happy wife!
 

Keith

New Around Here
I no
Eric, I just wanted to confirm regarding low space warning on JFFS, did you manage to fix it so it display different warning when unmounted. I am still getting low space warning when it is unmounted. I started by upgrading to 384.19 and then factory reset, after initial configuration I was getting message that it is low on space, instead of different message.

Also my system log is getting bombarded by these, looks like debugging, log level is set to notice and default log level is also notice.
I am having the same issue, along with the red light being on the RT-AX88U. I had to do factor reset and ran into many issues attempting to re-establish my mesh to my RT-AX58U (Wired). When you are applying the patch on the AX88U should you format the JFFS during the reboot ? I have not tried this because happy wife happy life rule applied, went back to 384.18 no issues.
 

Maverickcdn

Regular Contributor
As I figured the issue I noted earlier was easily resolved, picked up a 3.0 USB reverted back to 3.0 mode and my VPN now starts normally on reboots.

Thanks again Rmerlin for your great work.
 

truglodite

Regular Contributor
You best course of action would be factory reset, especially because you are not able to access GUI. I know not the most convenient method out there but it will get you going.


ASUS router Hard Factory Reset - Method 2

1. Turn the router off.
2. Press and hold the "WPS" button and turn the router on.
3. Power light is on (keep holding the WPS button).
4. Release the WPS button after the power light is off.
5. Reboot your router by manually pressing the power button.
6. Configure your router from scratch.
Did that, after a half hour of frustration learning the new default of ...168.50.1, now I'm at a proper login page that seems to be working... but it's not taking any user/password?!

I've tried admin/admin, administrator/administrator, admin/password, and my original user/pass, and it keeps getting rejected. I must be missing something here.

Edit... basically I think I tried to restore my settings too early. Instead I factory reset, did the basic config to get to the ui, then formatted jffs and rebooted. Then admin/admin worked, and I succesfully restored my settings after that. Restoring jffs seemed to go well, except diversion didn't restore properly (guessing because I had to first reformat my usb).
 
Last edited:

ferdinandpc

Occasional Visitor
Hi, i did a dirty upgrade from 348.18 to 348.19 on ax88u and now it restart randomly. Some times one cpu is 100% and in top show this:
Code:
  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND
   35     2 user   SW       0  0.0   0 24.9 [skb_free_task]
 

Stuey3D

Regular Contributor
RT-AC86U (Main) & RT-AC68U (Node) dirty flash both from 384.18 - 384.19 and mostly gone well, in fact my 86U is now holding onto the DFS channels much better so all good there. However I have noticed a small issue and that is on the Traffic Analyser - Statistic page my monthly usage has pretty much disappeared and restarted from the update day, and under the devices list the top 5 apps per device aren’t being listed however if I click apps it shows up correctly, nothing major that is gonna cause me to loose sleep just wondering if anyone else has the issue, and to feed it back.
 

ankhazam

Regular Contributor
Updated from 384.18 to 384.19 without any issues as usual. This is rather off-topic, but do anyone know what the required settings in order to get VoWiFi to work? Voice over WiFi has never worked for me when using my Asus RT-AX88U and Merlin firmware but when I was over at my parents house the past three days I noticed that their Google WiFi system gave me VoWiFi instantaneously and it was working all the time.

It's no biggie for me, I don't have that much use for VoWiFi. I'm just curious about whats lacking on my RT-AX88U for this to not work. We have the same ISP and I know for a fact that there is no limiting factor from the ISP itself and I have no firewall functionality on my AX88U that should be affecting this.

I can't seem to really locate any meaningful information on what kind of router requirements VoWiFi have? Some people claim that it won't work when you have hardware acceleration running in asus-wrt firmware aka flow cache but I have a hard time understanding why that might be a issue?
Go to WAN -> NAT Passthrough...

For VoWiFi to work for me I had to enable IPSec passthrough as below... try enabling other ones and find which does your carrier use:

1597613552796.png
 

Leguar

Occasional Visitor
Strange things happened, upgrading from 18 to the 19 version.
Have one RT-AX88U and a RT-AC68U as AiMesh (both on 18).
First I upgraded my RT-AX88U and all worked as expected.
Then I upgraded my RT-AC68U (via RT-AX88U).
Then I suddently have no Internet Access.
Went back to v.18 on RT-AX88U, and I have no problems connecting the Internet.
(tried this two times - with same result). Save behavior with my smartphones.
Have no clue what informations is needed - in this case :rolleyes:
 

tommyv2

Regular Contributor
How can I format the JFFS partition on my 86U? When I apply the format JFFS at next boot setting, the browser barks at the admin name change on the page even if I blank the fields, so I don't know if it's applied anything at all. I've tried several browsers and it's always the same thing. My JFFS shows unmounted after many attempts and reboots.

Just to clarify: If I modify anything at all on the Administration page and hit "Apply", it wants to do something with the top area and the admin name, no matter what's in there.]

Is there an SSH way to format/fix the JFFS so I can actually see the commands working? I'm aware the command itself runs at boot time when unmounted.
 
Last edited:

Leguar

Occasional Visitor
First I upgraded my RT-AX88U and all worked as expected.
This statement is not correct. Have tested a little more, and
v. 19 on RT-AX88U is the culprit, where I cannot access the
Internet.
Right now.... back on v. 18 on both routers :-(
 

dave14305

Part of the Furniture
Is there an SSH way to format/fix the JFFS so I can actually see the commands working? I'm aware the command itself runs at boot time when unmounted.
You can try:
Bash:
nvram set jffs2_format=1
nvram commit
service reboot
No guarantees.
 
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