AC68U - issue with AIprotection and standard firmware?

[chemoul]

Hi,

I've recently activated AIProtection on my AC68U and it seems to cause it to crash periodically. I then can't log into the admin interface and need to power cycle the router.

It also seems to reset the system logs to August 1, I've attached a snipped below.
I'm just wondering if these is a known issue with the latest Asus firmware and whether Merlin's firmware might help?

Thanks for your help!

Aug 1 10:00:59 miniupnpd[768]: shutting down MiniUPnPd
Aug 1 10:00:59 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_vlan3880)!
Aug 1 10:00:59 wan: finish adding multi routes
Aug 1 10:00:59 rc_service: ip-up 792:notify_rc stop_upnp
Aug 1 10:00:59 rc_service: waitting "start_firewall" via ip-up ...
Aug 1 10:01:00 miniupnpd[844]: version 1.9 started
Aug 1 10:01:00 miniupnpd[844]: HTTP listening on port 53923
Aug 1 10:01:00 miniupnpd[844]: Listening for NAT-PMP/PCP traffic on port 5351
Aug 1 10:01:00 rc_service: ip-up 792:notify_rc start_upnp
Aug 1 10:01:00 rc_service: waitting "stop_upnp" via ip-up ...
Aug 1 10:01:00 miniupnpd[844]: shutting down MiniUPnPd
Aug 1 10:01:01 WAN Connection: WAN was restored.
Aug 1 10:01:02 ddns update: ez-ipupdate: starting...
Aug 1 10:01:02 miniupnpd[849]: version 1.9 started
Aug 1 10:01:02 miniupnpd[849]: HTTP listening on port 42608
Aug 1 10:01:02 miniupnpd[849]: Listening for NAT-PMP/PCP traffic on port 5351
Aug 1 10:01:02 ddns update: connected to nwsrv-ns1.asus.com (103.10.4.108) on port 80.
Aug 1 10:01:03 ntp: start NTP update
Jan 11 18:01:05 ddns update: Asus update entry:: return: HTTP/1.1 200 OK^M Date: Thu, 11 Jan 2018 08:01:04 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
Jan 11 18:01:05 ddns update: retval= 0, ddns_return_code (,200)
Jan 11 18:01:05 ddns update: asusddns_update: 0
Jan 11 18:01:05 rc_service: ntp 847:notify_rc restart_upnp
Jan 11 18:01:05 miniupnpd[849]: shutting down MiniUPnPd
Jan 11 18:01:05 miniupnpd[858]: version 1.9 started
Jan 11 18:01:05 miniupnpd[858]: HTTP listening on port 49250
Jan 11 18:01:05 miniupnpd[858]: Listening for NAT-PMP/PCP traffic on port 5351
Jan 11 18:01:06 rc_service: ntp 847:notify_rc restart_diskmon
Jan 11 18:01:06 disk_monitor: Finish
Jan 11 18:01:07 ddns: ddns update ok
Jan 11 18:01:08 disk monitor: be idle
Jan 11 18:01:10 kernel: * Make sure sizeof(struct sw_struct)=160 is consistent
Jan 11 18:01:10 kernel: sizeof forward param = 160
Jan 11 18:01:16 rc_service: ip-up 792:notify_rc start_firewall
Jan 11 18:01:17 miniupnpd[858]: shutting down MiniUPnPd
Jan 11 18:01:17 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_vlan3880)!
Jan 11 18:01:18 miniupnpd[974]: version 1.9 started
Jan 11 18:01:18 miniupnpd[974]: HTTP listening on port 59475
Jan 11 18:01:18 miniupnpd[974]: Listening for NAT-PMP/PCP traffic on port 5351
Jan 11 18:01:19 miniupnpd[974]: upnp_event_recv: recv(): Connection reset by peer

 

[indark]

dont really experience any issue with both official (aimesh) / merlin firmware
but whenever you have issue with the firmware try factory reset and power cycle (unplug the router for at least 30 sec, in case you just turn it off n on) it
it helps to avoid most of weird issue when switch between firmware/major firmware update
at least that does it for me all the time