RT-AC88U help please

[thanh]

I current use Firmware Version:3.0.0.4_384_45717 on AC88U Aimesh router connect RT-AC3100 ,RT-AC68P,AC-AC68U as Aimesh node all working good cover wifi but then last Saturday I update new Firmware 3.0.0.4_384_81116 - Reboot router after done.
After few hour all going bad?signal off and on,Aimesh node some time on and off line?move Aimesh around get closed together same problem?I have to go back old firmware 3.0.0.4_384_45717 then all work fine but light for update keep linking?I don't know better do update or not?
Thank you

 

[Ken Atkinson]

I current use Firmware Version:3.0.0.4.384_45717 on AC88U Aimesh router connect RT-AC3100 ,RT-AC68P,AC-AC68U as Aimesh node all working good cover wifi but then last Saturday I update new Firmware 3.0.0.4_384_81116 - Reboot router after done.
After few hour all going bad?signal off and on,Aimesh node some time on and off line?move Aimesh around get closed together same problem?I have to go back old firmware 3.0.0.4_384_45717 then all work fine but light for update keep linking?I don't know better do update or not?
Thank you

A new firmware for 88u will probably be out in a week or so a lot of other models have had a update so I'd wait for new one then try that


Sent from my ONEPLUS A6013 using Tapatalk

 

[Ken Atkinson]

A new firmware for 88u will probably be out in a week or so a lot of other models have had a update so I'd wait for new one then try that


Sent from my ONEPLUS A6013 using Tapatalk

Also do a factory reset after update

Sent from my ONEPLUS A6013 using Tapatalk

 

[thanh]

Factory reset after update every time?I use to just reboot
Thank you for reply

 

[Ken Atkinson]

Factory reset after update every time?I use to just reboot
Thank you for reply

While not always needed a factory reset ensures nvram settings get applied correctly and recommended if skipping a update

Sent from my ONEPLUS A6013 using Tapatalk

 

[RoninChaos]

Can you save your settings, do a factory reset and then apply the settings again or do you have to do a new setup each time?

 

[L&LD]

Can you save your settings, do a factory reset and then apply the settings again or do you have to do a new setup each time?

By applying the saved settings, you negate the cleansing effect of the factory reset.

 

[thanh]

only when i update to 3.0.0.4.384_81116 -Factory reset then do new setup(this firmware get me nut?hitcup alot i have to go back 3.0.0.4_384_45717 much better,more stable )

 

[RoninChaos]

Setting up port forwarding and the Aimesh every time there’s a firmware update seems like a real pain if I’m doing a factory reset each time. .

 

[Grisu]

You dont need to do factory reset except you get strange problems.
And before you change firmware save config, so you can go back to last firmware and restore settings.

 

[thanh]

I have no idea what this mean?
Nov 30 04:15:22 kernel: EMF_ERROR: Interface wds1.1 doesn't exist
Nov 30 04:15:22 kernel: Register interface [wds1.1] MAC: 1c:b7:88.*******
Nov 30 04:15:22 kernel: EMF_ERROR: Interface wds1.1 doesn't exist
Nov 30 04:15:22 kernel: Register interface [wds1.1] MAC: 1c:b7:2c:********
Nov 30 04:16:14 kernel: EMF_ERROR: Interface wds1.1 doesn't exist
Nov 30 04:16:30 kernel: Register interface [wds1.1] MAC: 1c:b7:2c:*******
Nov 30 04:17:15 kernel: EMF_ERROR: Interface wds1.1 doesn't exist
Nov 30 04:17:27 kernel: Register interface [wds1.1] MAC: 1c:b7:2c*******
Nov 30 04:18:14 kernel: EMF_ERROR: Interface wds1.1 doesn't exist
Nov 30 04:18:14 kernel: Register interface [wds1.1] MAC: 1c:b7:2c********
Nov 30 04:18:50 WATCHDOG: [FAUPGRADE][auto_firmware_check5834)]period_retry = 0
Nov 30 04:18:51 WATCHDOG: [FAUPGRADE][auto_firmware_check5860)]retrieve firmware information
Nov 30 04:18:51 WATCHDOG: [FAUPGRADE][auto_firmware_check5874)]no need to upgrade firmware
Nov 30 04:19:12 kernel: EMF_ERROR: Interface wds1.1 doesn't exist
Nov 30 04:19:12 kernel: Register interface [wds1.1] MAC: 1c:b7:2c:74:20:0c
Nov 30 04:19:21 WATCHDOG: [FAUPGRADE][auto_firmware_check5834)]period_retry = 1
Nov 30 04:19:21 WATCHDOG: [FAUPGRADE][auto_firmware_check5860)]retrieve firmware information
Nov 30 04:19:21 WATCHDOG: [FAUPGRADE][auto_firmware_check5874)]no need to upgrade firmware
Nov 30 04:19:51 WATCHDOG: [FAUPGRADE][auto_firmware_check5834)]period_retry = 2
Nov 30 04:19:52 WATCHDOG: [FAUPGRADE][auto_firmware_check5860)]retrieve firmware information
Nov 30 04:19:52 WATCHDOG: [FAUPGRADE][auto_firmware_check5874)]no need to upgrade firmware
Nov 30 04:20:11 kernel: EMF_ERROR: Interface wds1.1 doesn't exist
Nov 30 04:20:11 kernel: Register interface [wds1.1] MAC: 1c:b7:2c*******
------------------------------------------
Nov 30 05:50:49 kernel: EMF_ERROR: Interface wds1.1 doesn't exist
Nov 30 05:50:49 kernel: Register interface [wds1.1] MAC: 1c:b7:2c:*******
Nov 30 05:51:54 kernel: EMF_ERROR: Interface wds1.1 doesn't exist
Nov 30 05:51:54 kernel: Register interface [wds1.1] MAC: 1c:b7:2c:*********
Nov 30 05:52:55 kernel: EMF_ERROR: Interface wds1.1 doesn't exist
Nov 30 05:52:55 kernel: Register interface [wds1.1] MAC: 1c:b7:2************
Nov 30 05:53:56 kernel: EMF_ERROR: Interface wds1.1 doesn't exist
Nov 30 05:53:56 kernel: Register interface [wds1.1] MAC: 1c:b7:2*********
Nov 30 05:54:55 kernel: Register interface [wds1.1] MAC: 1c:b7:2c:******
Nov 30 05:55:56 kernel: EMF_ERROR: Interface wds1.1 doesn't exist
Nov 30 05:55:56 kernel: Register interface [wds1.1] MAC: 1c:b7:2*********
-------------------------------------
Nov 30 06:26:46 kernel: Register interface [wds1.1] MAC: 1c:b7:2c*****
Nov 30 06:27:47 kernel: EMF_ERROR: Interface wds1.1 doesn't exist
Nov 30 06:27:47 kernel: Register interface [wds1.1] MAC: 1c:b7:**************
Nov 30 06:28:48 kernel: EMF_ERROR: Interface wds1.1 doesn't exist
Nov 30 06:28:48 kernel: Register interface [wds1.1] MAC: 1c:b7:2c*************
Nov 30 06:29:51 kernel: EMF_ERROR: Interface wds1.1 doesn't exist
Nov 30 06:34:50 kernel: net_ratelimit: 9359 callbacks suppressed
Nov 30 06:34:51 kernel: EMF_ERROR: Interface wds1.2 doesn't exist
Nov 30 06:34:51 kernel: EMF_ERROR: Interface wds0.2 doesn't exist
Nov 30 06:34:55 kernel: net_ratelimit: 9752 callbacks suppressed
Nov 30 06:35:00 kernel: net_ratelimit: 9732 callbacks suppressed
Nov 30 06:35:36 kernel: net_ratelimit: 2687 callbacks suppressed
Nov 30 08:01:26 kernel: EMF_ERROR: Interface wds0.16 doesn't exist
I have RT-AC88U Aimesh router firmware 3.0.0.4.384_45717-gadd52a8
RT-AC3100 Aimesh node 3.0.0.4.384_81116-g709c838 on wifi
RT-AC68U Aimesh node 3.0.0.4.385_10000-gd8ccd3c on wifi
RT-AC68P Aimesh node 3.0.0.4.385_10000-gd8ccd3c on wire

 

[thanh]

I has to reboot router because so slow get in?after reboot look like this?
Nov 30 09:19:22 rc_service: ntp 532:notify_rc restart_diskmon
Nov 30 09:19:22 rc_service: waitting "start_firewall" via udhcpc ...
Nov 30 09:19:23 kernel: xhci_hcd 0000:00:0c.0: Failed to enable MSI-X
Nov 30 09:19:23 kernel: xhci_hcd 0000:00:0c.0: failed to allocate MSI entry
Nov 30 09:19:23 kernel: usb usb1: No SuperSpeed endpoint companion for config 1 interface 0 altsetting 0 ep 129: using minimum values
Nov 30 09:19:23 syslog: module ledtrig-usbdev not found in modules.dep
Nov 30 09:19:23 syslog: module leds-usb not found in modules.dep
Nov 30 09:19:23 kernel: Register interface [wds1.2] MAC: 1c:b7*********
Nov 30 09:19:23 kernel: SCSI subsystem initialized
Nov 30 09:19:24 kernel: Register interface [wds1.3] MAC: 1c:**************
Nov 30 09:19:24 acsd: selected channel spec: 0x100b (11)
Nov 30 09:19:24 acsd: Adjusted channel spec: 0x100b (11)
Nov 30 09:19:24 acsd: selected channel spec: 0x100b (11)
Nov 30 09:19:24 miniupnpd[376]: shutting down MiniUPnPd
Nov 30 09:19:25 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Nov 30 09:19:25 kernel: nf_conntrack_rtsp v0.6.21 loading
Nov 30 09:19:25 kernel: nf_nat_rtsp v0.6.21 loading
Nov 30 09:19:26 miniupnpd[726]: version 1.9 started
Nov 30 09:19:26 miniupnpd[726]: HTTP listening on port 43823
Nov 30 09:19:26 miniupnpd[726]: Listening for NAT-PMP/PCP traffic on port 5351
Nov 30 09:19:26 rc_service: udhcpc 511:notify_rc start_upnp
Nov 30 09:19:26 rc_service: waitting "stop_upnp" via udhcpc ...
Nov 30 09:19:26 miniupnpd[726]: shutting down MiniUPnPd
Nov 30 09:19:27 kernel: Register interface [wds0.1] MAC: 1c:b7:2c:74:20:08
Nov 30 09:19:27 start_ddns: update WWW.ASUS.COM dyndns, wan_unit 0
Nov 30 09:19:27 disk_monitor: Finish
Nov 30 09:19:28 miniupnpd[735]: version 1.9 started
Nov 30 09:19:28 miniupnpd[735]: HTTP listening on port 53371
Nov 30 09:19:28 miniupnpd[735]: Listening for NAT-PMP/PCP traffic on port 5351
Nov 30 09:19:28 disk monitor: be idle
Nov 30 09:19:28 ddns update: ez-ipupdate: starting...
Nov 30 09:19:28 ddns update: asus_private() interface =eth0
Nov 30 09:19:28 ddns update: g_asus_ddns_mode == 2
Nov 30 09:19:29 ddns update: connected to nwsrv-ns1.asus.com (103.10.4.108) on port 443.
Nov 30 09:19:30 ddns update: Asus update entry:: return: HTTP/1.1 200 OK^M Date: Sat, 30 Nov 2019 17:19:29 GMT^M Server: Apache^M X-Powered-By: PHP/5.6.30^M Content-Length: 0^M Connection: close^M Content-Type: text/html; charset=UTF-8^M ^M
Nov 30 09:19:30 ddns update: retval= 0, ddns_return_code (,200)
Nov 30 09:19:30 ddns update: asusddns_update: 0
Nov 30 09:19:30 ddns: ddns update ok
Nov 30 09:19:30 ddns update: exit_main
Nov 30 09:19:33 kernel: EMF_ERROR: Interface wds1.1 doesn't exist
Nov 30 09:19:43 kernel: SHN Release Version: 2.0.1 d32a874
Nov 30 09:19:43 kernel: UDB Core Version: 0.2.18 r3508378
Nov 30 09:19:43 kernel: sizeof forward pkt param = 192
Nov 30 09:19:43 watchdog: start ddns.
Nov 30 09:19:43 rc_service: watchdog 317:notify_rc restart_ddns
Nov 30 09:19:43 start_ddns: update WWW.ASUS.COM dyndns, wan_unit 0
Nov 30 09:19:44 ddns update: ez-ipupdate: starting...
Nov 30 09:19:44 ddns update: asus_private() interface =eth0
Nov 30 09:19:44 ddns update: g_asus_ddns_mode == 2
Nov 30 09:19:44 BWDPI: fun bitmap = ff
Nov 30 09:19:44 A.QoS: qos_count=0, qos_check=0
Nov 30 09:19:46 kernel: Register interface [wds1.1] MAC: 1c:b7:2c:74:20:0c
Nov 30 09:19:47 ddns update: connected to nwsrv-ns1.asus.com (103.10.4.108) on port 443.
Nov 30 09:19:47 ddns update: Asus update entry:: return: HTTP/1.1 200 OK^M Date: Sat, 30 Nov 2019 17:19:47 GMT^M Server: Apache^M X-Powered-By: PHP/5.6.30^M Content-Length: 0^M Connection: close^M Content-Type: text/html; charset=UTF-8^M ^M
Nov 30 09:19:47 ddns update: retval= 0, ddns_return_code (,200)
Nov 30 09:19:47 ddns update: asusddns_update: 0
Nov 30 09:19:47 ddns: ddns update ok
Nov 30 09:19:47 ddns update: exit_main
Nov 30 09:19:50 rc_service: udhcpc 511:notify_rc start_firewall
Nov 30 09:19:51 miniupnpd[735]: shutting down MiniUPnPd
Nov 30 09:19:51 dhcp client: bound 24.17.134.32 via 24.17.128.1 during 79900 seconds.
Nov 30 09:19:52 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Nov 30 09:19:52 miniupnpd[1185]: version 1.9 started
Nov 30 09:19:52 miniupnpd[1185]: HTTP listening on port 59410
Nov 30 09:19:52 miniupnpd[1185]: Listening for NAT-PMP/PCP traffic on port 5351
Nov 30 09:19:59 crond[311]: time disparity of 827294 minutes detected
Nov 30 09:20:37 acsd: selected channel spec: 0x1004 (4)
Nov 30 09:20:37 acsd: Adjusted channel spec: 0x1004 (4)
Nov 30 09:20:37 acsd: selected channel spec: 0x1004 (4)
Nov 30 09:20:38 acsd: eth1: NONACSD channel switching to channel spec: 0x1004 (4)
Nov 30 09:20:44 WATCHDOG: [FAUPGRADE][auto_firmware_check5834)]period_retry = 0
Nov 30 09:20:44 WATCHDOG: [FAUPGRADE][auto_firmware_check5840)]periodic_check AM 5:31
Nov 30 09:20:45 WATCHDOG: [FAUPGRADE][auto_firmware_check5860)]retrieve firmware information
Nov 30 09:20:45 WATCHDOG: [FAUPGRADE][auto_firmware_check5874)]no need to upgrade firmware
Nov 30 09:21:13 hour monitor: ntp sync fail, will retry after 120 sec