Dropouts on third party routers. Please Help!

[jackr1]

I have already swapped one before and had issues again with a brand new one. In the last post i didnt ctually attach the log. It seems to be doing NTP updates then it goes down? Not sure though. What would you do in my shoes, is there another/better router to go for?

Thanks again,

Jack

May 6 09:17:43 ntp: start NTP update
May 6 21:17:44 ntp: start NTP update
May 7 01:09:42 DSL: Link up -> down
May 7 01:09:55 WAN Connection: Ethernet link down.
May 7 01:09:56 nat: apply redirect rules
May 7 01:10:12 DSL: Link down -> up
May 7 01:10:15 WAN Connection: WAN was restored.
May 7 01:10:15 nat: apply nat rules (/tmp/nat_rules_ppp0_vlan3880)
May 7 09:17:45 ntp: start NTP update
May 7 21:17:45 ntp: start NTP update
May 8 09:17:46 ntp: start NTP update
May 8 21:17:47 ntp: start NTP update
May 9 09:17:47 ntp: start NTP update
May 9 21:17:45 ntp: start NTP update
May 10 09:17:46 ntp: start NTP update
May 10 21:17:44 ntp: start NTP update
May 11 09:17:44 ntp: start NTP update
May 11 21:17:42 ntp: start NTP update
May 12 09:17:40 ntp: start NTP update
May 12 14:14:57 kernel: SKIPPED false Type 4 Radar Detection. min_pw=120 pw_delta=0 pri=15378 fm_min=1030 fm_max=0 nconsecq_pulses=5. Time from last detection = 1300951, = 21682min 31sec. Detected pulse index: 9
May 12 21:17:38 ntp: start NTP update
May 13 09:17:39 ntp: start NTP update
May 13 21:17:36 ntp: start NTP update
May 14 09:17:37 ntp: start NTP update
May 14 10:58:55 kernel: SKIPPED false Type 4 Radar Detection. min_pw=121 pw_delta=0 pri=15378 fm_min=1030 fm_max=0 nconsecq_pulses=5. Time from last detection = 161035, = 2683min 55sec. Detected pulse index: 8
May 14 10:58:55 kernel: Type 0 Radar Detection. Detected pulse index=8 fm_min=1030 fm_max=0 nconsecq_pulses=5. Time from last detection = 0, = 0min 0sec
May 14 21:17:35 ntp: start NTP update
May 15 09:17:36 ntp: start NTP update
May 15 21:17:33 ntp: start NTP update
May 16 09:17:31 ntp: start NTP update
May 16 09:54:43 httpd login lock: Detect abnormal logins at 5 times. The newest one was from 185.53.88.184 in login.
May 16 21:17:29 ntp: start NTP update
May 17 09:17:30 ntp: start NTP update
May 17 21:17:30 ntp: start NTP update
May 18 09:17:31 ntp: start NTP update
May 18 20:16:32 rc_service: cfg_server 2306:notify_rc restart_wireless
May 18 20:19:29 rc_service: httpds 24818:notify_rc restart_firewall;restart_qos
May 18 20:19:30 miniupnpd[6240]: shutting down MiniUPnPd
May 18 20:19:30 nat: apply nat rules (/tmp/nat_rules_ppp0_vlan3880)
May 18 20:19:31 miniupnpd[2726]: version 1.9 started
May 18 20:19:31 miniupnpd[2726]: HTTP listening on port 49674
May 18 20:19:31 miniupnpd[2726]: Listening for NAT-PMP/PCP traffic on port 5351
May 18 20:19:31 kernel: SHN Release Version: 2.0.1 890c91d
May 18 20:19:31 kernel: UDB Core Version: 0.2.18
May 18 20:19:31 kernel: tdts_udbfw: Unknown symbol udb_shell_ct_event_handler (err 0)
May 18 20:19:31 kernel: tdts_udbfw: Unknown symbol udb_shell_update_devid_un_bootp (err 0)
May 18 20:19:31 kernel: tdts_udbfw: Unknown symbol udb_shell_policy_match (err 0)
May 18 20:19:31 kernel: tdts_udbfw: Unknown symbol udb_shell_usr_msg_handler (err 0)
May 18 20:19:31 kernel: tdts_udbfw: Unknown symbol udb_shell_wan_detection (err 0)
May 18 20:19:31 kernel: tdts_udbfw: Unknown symbol dev_wan (err 0)
May 18 20:19:31 kernel: tdts_udbfw: Unknown symbol mode (err 0)
May 18 20:19:31 kernel: tdts_udbfw: Unknown symbol tdts_shell_dpi_register_mt (err -2)
May 18 20:19:31 kernel: tdts_udbfw: Unknown symbol tdts_shell_system_setting_udp_conn_max_set (err -2)
May 18 20:19:31 kernel: tdts_udbfw: Unknown symbol udb_shell_unregister_qos_ops (err 0)
May 18 20:19:31 kernel: tdts_udbfw: Unknown symbol udb_shell_get_action (err 0)
May 18 20:19:31 kernel: tdts_udbfw: Unknown symbol udb_shell_update_devid_un_http_ua (err 0)
May 18 20:19:31 kernel: tdts_udbfw: Unknown symbol udb_shell_do_fastpath_action (err 0)
May 18 20:19:31 kernel: tdts_udbfw: Unknown symbol tdts_shell_dpi_unregister_mt (err -2)
May 18 20:19:31 kernel: tdts_udbfw: Unknown symbol udb_shell_update_qos_data (err 0)
May 18 20:19:31 kernel: tdts_udbfw: Unknown symbol tdts_shell_system_setting_tcp_conn_max_set (err 0)
May 18 20:19:31 kernel: tdts_udbfw: Unknown symbol udb_shell_register_qos_ops (err 0)
May 18 20:19:31 kernel: tdts_udbfw: Unknown symbol udb_shell_reg_func_find_ct (err 0)
May 18 20:19:31 BWDPI: fun bitmap = 3
May 18 20:19:32 kernel: HTB: quantum of class 10001 is big. Consider r2q change.
May 18 20:19:32 kernel: HTB: quantum of class 20001 is big. Consider r2q change.
May 18 20:19:32 kernel: HTB: quantum of class 10009 is big. Consider r2q change.
May 18 20:19:32 kernel: HTB: quantum of class 20009 is big. Consider r2q change.
May 18 20:19:53 kernel: SHN Release Version: 2.0.1 890c91d
May 18 20:19:53 kernel: UDB Core Version: 0.2.18
May 18 20:19:53 kernel: sizeof forward pkt param = 192
May 18 20:19:53 BWDPI: fun bitmap = 3
May 18 20:20:40 kernel: HTB: quantum of class 10001 is big. Consider r2q change.
May 18 20:20:40 kernel: HTB: quantum of class 20001 is big. Consider r2q change.
May 18 20:20:40 kernel: HTB: quantum of class 10009 is big. Consider r2q change.
May 18 20:20:40 kernel: HTB: quantum of class 20009 is big. Consider r2q change.
May 18 20:20:40 rc_service: bwdpi_check 238:notify_rc start_firewall
May 18 20:20:40 miniupnpd[2726]: shutting down MiniUPnPd
May 18 20:20:41 nat: apply nat rules (/tmp/nat_rules_ppp0_vlan3880)
May 18 20:20:41 miniupnpd[3444]: version 1.9 started
May 18 20:20:41 miniupnpd[3444]: HTTP listening on port 44363
May 18 20:20:41 miniupnpd[3444]: Listening for NAT-PMP/PCP traffic on port 5351
May 18 20:21:13 kernel: SHN Release Version: 2.0.1 890c91d
May 18 20:21:13 kernel: UDB Core Version: 0.2.18
May 18 20:21:13 kernel: sizeof forward pkt param = 192
May 18 20:21:13 BWDPI: fun bitmap = 3
May 18 20:21:35 kernel: HTB: quantum of class 10001 is big. Consider r2q change.
May 18 20:21:35 kernel: HTB: quantum of class 20001 is big. Consider r2q change.
May 18 20:21:35 kernel: HTB: quantum of class 10009 is big. Consider r2q change.
May 18 20:21:35 kernel: HTB: quantum of class 20009 is big. Consider r2q change.
May 18 20:21:35 rc_service: bwdpi_check 238:notify_rc start_firewall
May 18 20:21:35 miniupnpd[3444]: shutting down MiniUPnPd
May 18 20:21:35 nat: apply nat rules (/tmp/nat_rules_ppp0_vlan3880)
May 18 20:21:36 miniupnpd[3801]: version 1.9 started
May 18 20:21:36 miniupnpd[3801]: HTTP listening on port 43047
May 18 20:21:36 miniupnpd[3801]: Listening for NAT-PMP/PCP traffic on port 5351
May 18 20:21:55 kernel: SHN Release Version: 2.0.1 890c91d
May 18 20:21:55 kernel: UDB Core Version: 0.2.18
May 18 20:21:56 kernel: sizeof forward pkt param = 192
May 18 20:21:56 BWDPI: fun bitmap = 3
May 18 20:24:41 kernel: HTB: quantum of class 10001 is big. Consider r2q change.
May 18 20:24:41 kernel: HTB: quantum of class 20001 is big. Consider r2q change.
May 18 20:24:41 kernel: HTB: quantum of class 10009 is big. Consider r2q change.
May 18 20:24:41 kernel: HTB: quantum of class 20009 is big. Consider r2q change.
May 18 20:24:41 rc_service: bwdpi_check 238:notify_rc start_firewall
May 18 20:24:41 miniupnpd[3801]: shutting down MiniUPnPd
May 18 20:24:42 nat: apply nat rules (/tmp/nat_rules_ppp0_vlan3880)
May 18 20:24:42 miniupnpd[4328]: version 1.9 started
May 18 20:24:42 miniupnpd[4328]: HTTP listening on port 38350
May 18 20:24:42 miniupnpd[4328]: Listening for NAT-PMP/PCP traffic on port 5351
May 18 21:17:29 ntp: start NTP update
May 19 02:39:58 rc_service: watchdog 211:notify_rc stop_aae
May 19 02:39:58 rc_service: watchdog 211:notify_rc start_mastiff
May 19 02:39:58 rc_service: waitting "stop_aae" via watchdog ...
May 19 02:39:58 NAT Tunnel: AAE Service is stopped
May 19 02:39:58 NAT Tunnel: AAE Service is stopped
May 19 02:39:59 NAT Tunnel: AAE Service is stopped
May 19 02:39:59 AAE: AAE Service is started
May 19 02:40:01 Mastiff: init
May 19 08:31:29 rc_service: watchdog 211:notify_rc stop_aae
May 19 08:31:29 rc_service: watchdog 211:notify_rc start_mastiff
May 19 08:31:29 rc_service: waitting "stop_aae" via watchdog ...
May 19 08:31:29 NAT Tunnel: AAE Service is stopped

[TimCurtis]

@jackr1 

Something very strange going on with your setup.

Is there any chance the router is overheating or close to some interference generating device?

Other than that I've absolutely no idea although I still think it worthwhile trying Asus support & see what they make of those logs.

[hammy30]

Are you anywhere near an airfield?
It looks as though the DFS system in the router is occasionally detecting RADAR pulses and it should change Channels to avoid interference. It is possible the router takes too long to find an acceptable channel to use( this is on the 5GHz Band).