Expect a new firmware from Asus next week to address the AiProtection issues, for all affected models.
Speaking of firmware releases, do you think any of the following will get fixed?
I have an RT-AC68R, and was running the -5656 firmware release until recently, and finally installed the -4376 release. It works fine for me, but in the System log I get a bunch of entries that I didn't get on the old -5656 version, to wit:
Mar 6 05:59:57 ntp: start NTP update
Mar 6 06:59:59 ntp: start NTP update
Mar 6 08:00:01 ntp: start NTP update
Mar 6 02:00:29 rc_service: rc 18929:notify_rc restart_wrs
Mar 6 08:59:57 ntp: start NTP update
Mar 6 09:59:57 ntp: start NTP update
Mar 6 10:59:57 ntp: start NTP update
Mar 6 11:59:59 ntp: start NTP update
Mar 6 12:59:57 ntp: start NTP update
Mar 6 13:59:57 ntp: start NTP update
Mar 6 14:59:57 ntp: start NTP update
Mar 6 15:59:59 ntp: start NTP update
Mar 6 17:00:01 ntp: start NTP update
Mar 6 17:59:57 ntp: start NTP update
Mar 6 18:59:57 ntp: start NTP update
Mar 6 19:00:00 ntp: start NTP update
Mar 6 19:59:57 ntp: start NTP update
Mar 6 20:59:59 ntp: start NTP update
Mar 6 22:00:01 ntp: start NTP update
Mar 6 16:49:39 kernel: * Make sure sizeof(struct sw_struct)=160 is consistent
Mar 6 16:49:40 kernel: sizeof forward param = 160
Mar 6 16:49:52 kernel: Stop the IPS/AppID engine...
Mar 6 22:49:53 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Mar 6 16:50:12 kernel: * Make sure sizeof(struct sw_struct)=160 is consistent
Mar 6 16:50:12 kernel: sizeof forward param = 160
Mar 6 16:50:24 kernel: Stop the IPS/AppID engine...
Mar 6 22:50:25 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Mar 6 16:53:34 kernel: * Make sure sizeof(struct sw_struct)=160 is consistent
Mar 6 16:53:34 kernel: sizeof forward param = 160
Mar 6 16:53:46 kernel: Stop the IPS/AppID engine...
Mar 6 22:53:47 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Mar 6 22:59:57 ntp: start NTP update
Per a previous forum entry, the kernel messages related to "Make sure sizeof(struct..." and the following line is a debug message left over from the firmware debug process, left in for some reason (sloppy work?). What I'm curious about is the entry:
Mar 6 16:50:24 kernel: Stop the IPS/AppID engine...
Mar 6 22:50:25 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
I thought the NAT process was started during the boot sequence (I have NAT enabled); I have all the QOS stuff turned off, so I'm surprised to see the IPS/App/ID engine process terminated and the nat rules applied out of the blue.
If you can enlighten me about this, I'd appreciate it. Also, if you have any pull with the Asus firmware guys, can you please ask them to fix the NTP update bug? If my router (and everyone else's) is hitting the NTP server every hour, we won't be popular with the NTP server's operators.
Thanks all, and specifically RMerlin.
Peter