What's new

RT-AC88U Firmware Update (2020/03/30)

  • 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!

ok, I understand and suppose that is what I need to do. Whish there was an easy way to list all the settings that I have (or have changed) in order to remember to do them all with the new firmware.

Would you also go through this same procedure upgrading from one Merlin to the next, or only do the reset in case you face problems after the upgrade?

People tend to have their preferred personal setup. If so you can do this once. Write up a step by step list of your settings in Word for example, alternatively or in combination with screen dumps. Then you will have a "quick" to do list to follow the next time.

Most people go for @Grisu approach "only in case of strange problems. But if you change from stock to Merlin or back might be better anyway."

Personally I do it everytime. A lot of these faults/strange behavior doesn't reveal itself in days after upgrading. So just to be done with it, and know for sure I started out fresh, I do it everytime I change fw. If I then experience problems, I discard that fw. And I don't have to reset and start all over again with that very same fw. I'm not saying that's the right way for you or anyone else for that matter, but it's right for me...

Best of luck whatever you decide!
 
Last edited:
This update hasn't shown up yet in the firmware update of my RT-AC3100. Can I use this same firmware update?
I'm using the one with 4 lan ports instead of the AC88U which has 8 lan ports.
 
This update hasn't shown up yet in the firmware update of my RT-AC3100. Can I use this same firmware update?

No.

Sent from my SM-T720 using Tapatalk
 
No.

Sent from my SM-T720 using Tapatalk

I see. I'll wait for the official update.
This update would be useful since I use video conference while working from home.
I've been looking for it in the current QOS but there's no classification for it in my current firmware.

Thanks.
 
Hi,
Got back to 384.15 and have now a 24 h full working Media Bridge again.
The only drawback is that now I cannot quite a never-ending office meeting with the excuse "I lost my connection" :)
Hope 384.17 can solve this issue for MB.
Regards.
 
Hi,
Got back to 384.15 and have now a 24 h full working Media Bridge again.
The only drawback is that now I cannot quite a never-ending office meeting with the excuse "I lost my connection" :)
Hope 384.17 can solve this issue for MB.
Regards.

Oops, lamentably I was too optimistic and it did not last even 48 h with 384.15:
Code:
Apr 16 16:05:26 rc_service: psta_monitor 227:notify_rc restart_wlcmode 0
Apr 16 16:05:27 FTP_Server: daemon is stopped
Apr 16 16:05:28 wsdd2[1082]: Terminated received.
Apr 16 16:05:28 kernel: Interface wl1.1 doesn't exist
Apr 16 16:05:28 kernel: Interface wl1.2 doesn't exist
Apr 16 16:05:28 kernel: Interface wl1.3 doesn't exist
Apr 16 16:05:29 Samba_Server: smb daemon is stopped
Apr 16 16:05:29 kernel: gro disabled
Apr 16 16:05:34 watchdog: restart httpd
Apr 16 16:05:34 rc_service: watchdog 224:notify_rc stop_httpd
Apr 16 16:05:34 rc_service: waitting "restart_wlcmode 0" via psta_monitor ...
Apr 16 16:05:36 rc_service: psta_monitor 227:notify_rc restart_wireless
Apr 16 16:05:36 rc_service: waitting "restart_wlcmode 0" via psta_monitor ...
Apr 16 16:05:42 rc_service: preinit 1:notify_rc restart_dms
Apr 16 16:05:42 rc_service: waitting "restart_wlcmode 0" via psta_monitor ...
Apr 16 16:05:48 rc_service: skip the event: stop_httpd.
Apr 16 16:05:48 rc_service: watchdog 224:notify_rc start_httpd
Apr 16 16:05:48 rc_service: waitting "restart_wlcmode 0" via psta_monitor ...
Apr 16 16:05:51 rc_service: skip the event: restart_wireless.
Apr 16 16:05:57 rc_service: skip the event: restart_dms.
Apr 16 16:05:57 RT-AC68U: start https:8443
Apr 16 16:05:57 RT-AC68U: start httpd:80
Apr 16 16:05:59 kernel: gro enabled with interval 2
Apr 16 16:06:00 Samba_Server: daemon is started
Apr 16 16:06:00 wsdd2[13338]: error: wsdd-mcast-v4: wsd_send_soap_msg: send
Apr 16 16:06:00 RT-AC68U: start https:8443
Apr 16 16:06:00 RT-AC68U: start httpd:80
Apr 16 16:06:06 rc_service: psta_monitor 227:notify_rc restart_wlcmode 1
Apr 16 16:06:06 FTP_Server: daemon is stopped
Apr 16 16:06:07 wsdd2[13338]: Terminated received.
Apr 16 16:06:09 Samba_Server: smb daemon is stopped
Apr 16 16:06:09 kernel: gro disabled
Apr 16 16:06:09 kernel: Interface wl1.3 doesn't exist
Apr 16 16:06:17 kernel: Interface wl1.1 doesn't exist
Apr 16 16:06:18 ntpd: Stopped ntpd
Apr 16 16:06:18 ntpd: Started ntpd
Apr 16 16:06:18 rc_service: preinit 1:notify_rc restart_dms
Apr 16 16:06:18 rc_service: waitting "restart_wlcmode 1" via psta_monitor ...
Apr 16 16:06:32 rc_service: skip the event: restart_dms.
Apr 16 16:06:32 RT-AC68U: start https:8443
Apr 16 16:06:32 RT-AC68U: start httpd:80
Apr 16 16:06:32 kernel: gro enabled with interval 2
Apr 16 16:06:33 Samba_Server: daemon is started
Apr 16 16:07:36 rc_service: httpd 13438:notify_rc restart_logger

Regards.
 
Oops, lamentably I was too optimistic and it did not last even 48 h with 384.15:
Code:
Apr 16 16:05:26 rc_service: psta_monitor 227:notify_rc restart_wlcmode 0
Apr 16 16:05:27 FTP_Server: daemon is stopped
Apr 16 16:05:28 wsdd2[1082]: Terminated received.
Apr 16 16:05:28 kernel: Interface wl1.1 doesn't exist
Apr 16 16:05:28 kernel: Interface wl1.2 doesn't exist
Apr 16 16:05:28 kernel: Interface wl1.3 doesn't exist
Apr 16 16:05:29 Samba_Server: smb daemon is stopped
Apr 16 16:05:29 kernel: gro disabled
Apr 16 16:05:34 watchdog: restart httpd
Apr 16 16:05:34 rc_service: watchdog 224:notify_rc stop_httpd
Apr 16 16:05:34 rc_service: waitting "restart_wlcmode 0" via psta_monitor ...
Apr 16 16:05:36 rc_service: psta_monitor 227:notify_rc restart_wireless
Apr 16 16:05:36 rc_service: waitting "restart_wlcmode 0" via psta_monitor ...
Apr 16 16:05:42 rc_service: preinit 1:notify_rc restart_dms
Apr 16 16:05:42 rc_service: waitting "restart_wlcmode 0" via psta_monitor ...
Apr 16 16:05:48 rc_service: skip the event: stop_httpd.
Apr 16 16:05:48 rc_service: watchdog 224:notify_rc start_httpd
Apr 16 16:05:48 rc_service: waitting "restart_wlcmode 0" via psta_monitor ...
Apr 16 16:05:51 rc_service: skip the event: restart_wireless.
Apr 16 16:05:57 rc_service: skip the event: restart_dms.
Apr 16 16:05:57 RT-AC68U: start https:8443
Apr 16 16:05:57 RT-AC68U: start httpd:80
Apr 16 16:05:59 kernel: gro enabled with interval 2
Apr 16 16:06:00 Samba_Server: daemon is started
Apr 16 16:06:00 wsdd2[13338]: error: wsdd-mcast-v4: wsd_send_soap_msg: send
Apr 16 16:06:00 RT-AC68U: start https:8443
Apr 16 16:06:00 RT-AC68U: start httpd:80
Apr 16 16:06:06 rc_service: psta_monitor 227:notify_rc restart_wlcmode 1
Apr 16 16:06:06 FTP_Server: daemon is stopped
Apr 16 16:06:07 wsdd2[13338]: Terminated received.
Apr 16 16:06:09 Samba_Server: smb daemon is stopped
Apr 16 16:06:09 kernel: gro disabled
Apr 16 16:06:09 kernel: Interface wl1.3 doesn't exist
Apr 16 16:06:17 kernel: Interface wl1.1 doesn't exist
Apr 16 16:06:18 ntpd: Stopped ntpd
Apr 16 16:06:18 ntpd: Started ntpd
Apr 16 16:06:18 rc_service: preinit 1:notify_rc restart_dms
Apr 16 16:06:18 rc_service: waitting "restart_wlcmode 1" via psta_monitor ...
Apr 16 16:06:32 rc_service: skip the event: restart_dms.
Apr 16 16:06:32 RT-AC68U: start https:8443
Apr 16 16:06:32 RT-AC68U: start httpd:80
Apr 16 16:06:32 kernel: gro enabled with interval 2
Apr 16 16:06:33 Samba_Server: daemon is started
Apr 16 16:07:36 rc_service: httpd 13438:notify_rc restart_logger

Regards.


Solved.
384.15 + Factory reset + manual config
Back again to where I started.
Waiting for 384.17.
Regards.
 
you are in stock firmware section, go to Merlin subfolder for Merlin specific firmware issues.
 
And not necessarily false either. :)
 

Sign Up For SNBForums Daily Digest

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