华硕RT-AC66U_B1，每隔30分钟断流一次，已疯
平时用还好，但只要使用投屏播放，必然会断流，联系客服找到技术人员，整天要求提供这个提供那个的，就是不解决问题，网上一查，擦，华硕路由器断流的问题遍地都是。。。。每次断流之后就会有： rc_service: service 4636:notify_rc restart_letsencrypt
May 26 20:00:47 rc_service: ntp 596:notify_rc restart_diskmon
May 26 20:00:47 rc_service: waitting "start_firewall" via ip-up ...
May 26 20:00:47 usb: USB ext4 fs at /dev/sda1 mounted on /tmp/mnt/sda1.
May 26 20:00:48 miniupnpd: shutting down MiniUPnPd
May 26 20:00:48 nat: apply nat rules (/tmp/nat_rules_ppp0_eth0)
May 26 20:00:51 rc_service: hotplug 530:notify_rc restart_nasapps
May 26 20:00:51 rc_service: waitting "start_firewall" via ip-up ...
May 26 20:00:54 miniupnpd: version 1.9 started
May 26 20:00:54 miniupnpd: HTTP listening on port 36576
May 26 20:00:54 miniupnpd: Listening for NAT-PMP/PCP traffic on port 5351
May 26 20:00:54 miniupnpd: MiniUPnPd is already running. EXITING
May 26 20:00:54 disk_monitor: Finish
May 26 20:00:55 iTunes: daemon is stoped
May 26 20:00:55 FTP Server: daemon is stoped
May 26 20:00:56 Samba Server: smb daemon is stoped
May 26 20:00:56 kernel: gro disabled
May 26 20:00:56 disk monitor: be idle
May 26 20:00:56 Timemachine: daemon is stoped
May 26 20:00:56 miniupnpd: shutting down MiniUPnPd
May 26 20:00:56 avahi-daemon: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
May 26 20:00:56 kernel: gro enabled with interval 2
May 26 20:00:57 avahi-daemon: Alias name "RT-AC66U_B1" successfully established.
May 26 20:00:57 Samba Server: daemon is started
May 26 20:00:57 miniupnpd: version 1.9 started
May 26 20:00:57 miniupnpd: HTTP listening on port 33850
May 26 20:00:57 miniupnpd: Listening for NAT-PMP/PCP traffic on port 5351
May 26 20:00:58 rc_service: ip-up 537:notify_rc start_upnp
May 26 20:00:58 rc_service: waitting "stop_upnp" via ip-up ...
May 26 20:00:58 miniupnpd: shutting down MiniUPnPd
May 26 20:00:59 start_ddns: update WWW.ASUS.COM dyndns, wan_unit 0
May 26 20:01:00 miniupnpd: version 1.9 started
May 26 20:01:00 miniupnpd: HTTP listening on port 49610
May 26 20:01:00 miniupnpd: Listening for NAT-PMP/PCP traffic on port 5351
May 26 20:01:02 ddns update: ez-ipupdate: starting...
May 26 20:01:02 ddns update: asus_private() interface =ppp0
May 26 20:01:02 ddns update: g_asus_ddns_mode == 2
May 26 20:01:03 watchdog: start ddns.
May 26 20:01:03 rc_service: watchdog 242:notify_rc restart_ddns
May 26 20:01:03 start_ddns: update WWW.ASUS.COM dyndns, wan_unit 0
May 26 20:01:04 ddns update: ez-ipupdate: starting...
May 26 20:01:04 ddns update: asus_private() interface =ppp0
May 26 20:01:04 ddns update: g_asus_ddns_mode == 2
May 26 20:01:08 ddns update: connected to nwsrv-ns1.asus.com (103.10.4.108) on port 443.
May 26 20:01:09 ddns update: Asus update entry:: return: HTTP/1.1 200 OK^M Date: Sun, 26 May 2019 12:01:08 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
May 26 20:01:09 ddns update: retval= 0, ddns_return_code (,200)
May 26 20:01:09 ddns update: asusddns_update: 0
May 26 20:01:09 ddns: ddns update ok
May 26 20:01:09 ddns update: exit_main
May 26 20:01:25 crond: time disparity of 556256 minutes detected
May 26 20:02:03 WATCHDOG: period_retry = 0
May 26 20:02:03 WATCHDOG: periodic_check AM 4:38
May 26 20:02:04 WATCHDOG: retrieve firmware information
May 26 20:02:04 WATCHDOG: user in use
May 26 20:05:01 rc_service: service 1384:notify_rc restart_letsencrypt
May 26 20:05:31 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt ... YN_O2w/16255193765: bad response
May 26 20:05:31 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "http-01", "status": "invalid", "error": { "type": "urn:acme:error:connection", "detail": "Fetching http://xxserver.asuscomm.com/.we ... MzNqpC__e3Bs3tMxzY: Timeout during connect (likely firewall problem)", "status": 400 }, "uri": "https://acme-v01.api.letsencrypt.org/acme/challenge/3YVTjCLJ6UhVCBDG-SNx92HpH3EHcfcRWqvoLYN_O2w/16255193765", "token": "CSpn_jNN4xAvl375SjLqyiqa6MzNqpC__e3B
May 26 20:10:01 rc_service: service 1556:notify_rc restart_letsencrypt
May 26 20:10:38 rc_service: httpds 237:notify_rc restart_cloudsync
May 26 20:10:38 Cloudsync client and Webdav_client and dropbox_client ftp_client sambaclient usb_client google_client: daemon is stoped
May 26 20:10:38 Cloudsync client: manually disabled
May 26 20:10:39 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt ... XxJ0uA/16301234442: bad response
May 26 20:10:39 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "http-01", "status": "invalid", "error": { "type": "urn:acme:error:connection", "detail": "Fetching http://xxserver.asuscomm.com/.we ... rwUqVsMS8o44E8zHEs: Timeout during connect (likely firewall problem)", "status": 400 }, "uri": "https://acme-v01.api.letsencrypt.org/acme/challenge/h59zMxfsFi8uxmL1alQmD7U69uVcwwisZDq8ZXxJ0uA/16301234442", "token": "Rb7-xd4UcFIWQbKVvWy5KokHtrwUqVsMS8o4
May 26 20:15:01 rc_service: service 1720:notify_rc restart_letsencrypt
May 26 20:15:30 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt ... zhJ4IM/16301365038: bad response
May 26 20:15:30 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "http-01", "status": "invalid", "error": { "type": "urn:acme:error:connection", "detail": "Fetching http://xxserver.asuscomm.com/.we ... bMlDTQEUliZf7BelmM: Timeout during connect (likely firewall problem)", "status": 400 }, "uri": "https://acme-v01.api.letsencrypt.org/acme/challenge/KjPITZgszniWYs-HLXrGAe4NkKDuZhEZkME7ZzhJ4IM/16301365038", "token": "nc9X6nOaFBCON2TOrszBMLkQTbMlDTQEUliZ
May 26 20:20:01 rc_service: service 1848:notify_rc restart_letsencrypt
May 26 20:20:33 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt ... cYfn6A/16301516772: bad response
May 26 20:20:33 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "http-01", "status": "invalid", "error": { "type": "urn:acme:error:connection", "detail": "Fetching http://xxserver.asuscomm.com/.we ... bkQzgEWVs2q2oHwyMo: Timeout during connect (likely firewall problem)", "status": 400 }, "uri": "https://acme-v01.api.letsencrypt.org/acme/challenge/LY1FHSUoi0pVjFVZKVw8fHDR2xoFGSTPk8cL_cYfn6A/16301516772", "token": "wr72jm4YU0NgbtTttqRCCOTuLbkQzgEWVs2q
May 26 20:25:02 rc_service: service 1970:notify_rc restart_letsencrypt
May 26 20:25:36 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt ... vKCkyM/16301649727: bad response
May 26 20:25:36 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "http-01", "status": "invalid", "error": { "type": "urn:acme:error:connection", "detail": "Fetching http://xxserver.asuscomm.com/.we ... efZSg_UPMx6gqf6Byo: Timeout during connect (likely firewall problem)", "status": 400 }, "uri": "https://acme-v01.api.letsencrypt.org/acme/challenge/bwDIHk3FDbwU5Bf9RB25JN7VAikBmlyvX3oe-vKCkyM/16301649727", "token": "UMtbz7wxf3_xSEjSeRxM21hEvefZSg_UPMx6
May 26 20:30:01 rc_service: service 2092:notify_rc restart_letsencrypt
May 26 20:30:44 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt ... ybrju0/16301792811: bad response
May 26 20:30:44 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "http-01", "status": "invalid", "error": { "type": "urn:acme:error:connection", "detail": "Fetching http://xxserver.asuscomm.com/.we ... VXiQa1F3cGnf6ca4c8: Timeout during connect (likely firewall problem)", "status": 400 }, "uri": "https://acme-v01.api.letsencrypt.org/acme/challenge/IHWFrDcbaNDpZGwzW3ygh_SY8N964LaKEkDtYybrju0/16301792811", "token": "7nCjQ5si5zrdXA4tJCFCcsh6yVXiQa1F3cGn
May 26 20:35:02 rc_service: service 2214:notify_rc restart_letsencrypt
May 26 20:35:14 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz: bad HTTP: 429
May 26 20:35:14 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "urn:acme:error:rateLimited", "detail": "Error creating new authz :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/", "status": 429 }] (189 bytes)
May 26 20:40:02 rc_service: service 2332:notify_rc restart_letsencrypt
May 26 20:40:16 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz: bad HTTP: 429
May 26 20:40:16 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "urn:acme:error:rateLimited", "detail": "Error creating new authz :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/", "status": 429 }] (189 bytes)
May 26 20:45:02 rc_service: service 2453:notify_rc restart_letsencrypt
May 26 20:45:20 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz: bad HTTP: 429
May 26 20:45:20 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "urn:acme:error:rateLimited", "detail": "Error creating new authz :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/", "status": 429 }] (189 bytes)
May 26 20:50:02 rc_service: service 2573:notify_rc restart_letsencrypt
May 26 20:50:26 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz: bad HTTP: 429
May 26 20:50:26 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "urn:acme:error:rateLimited", "detail": "Error creating new authz :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/", "status": 429 }] (189 bytes)
May 26 20:55:02 rc_service: service 2694:notify_rc restart_letsencrypt
May 26 20:55:17 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz: bad HTTP: 429
May 26 20:55:17 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "urn:acme:error:rateLimited", "detail": "Error creating new authz :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/", "status": 429 }] (189 bytes)
May 26 21:00:02 rc_service: service 2812:notify_rc restart_letsencrypt
May 26 21:00:17 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz: bad HTTP: 429
May 26 21:00:17 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "urn:acme:error:rateLimited", "detail": "Error creating new authz :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/", "status": 429 }] (189 bytes)
May 26 21:05:02 rc_service: service 2937:notify_rc restart_letsencrypt
May 26 21:05:12 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz: bad HTTP: 429
May 26 21:05:12 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "urn:acme:error:rateLimited", "detail": "Error creating new authz :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/", "status": 429 }] (189 bytes)
May 26 21:10:02 rc_service: service 3055:notify_rc restart_letsencrypt
May 26 21:10:12 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz: bad HTTP: 429
May 26 21:10:12 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "urn:acme:error:rateLimited", "detail": "Error creating new authz :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/", "status": 429 }] (189 bytes)
May 26 21:15:01 rc_service: service 3179:notify_rc restart_letsencrypt
May 26 21:15:30 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt ... 8UHHIM/16303009470: bad response
May 26 21:15:30 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "http-01", "status": "invalid", "error": { "type": "urn:acme:error:connection", "detail": "Fetching http://xxserver.asuscomm.com/.we ... zq64PRR8Vd26Ob4VLc: Timeout during connect (likely firewall problem)", "status": 400 }, "uri": "https://acme-v01.api.letsencrypt.org/acme/challenge/tzMBmfNXKFqR4yfPZHLvqm1Wi8hYX0isrVAyA8UHHIM/16303009470", "token": "qca62ezHU3pIeVKfasjruwQ2Xzq64PRR8Vd2
May 26 21:20:02 rc_service: service 3299:notify_rc restart_letsencrypt
May 26 21:20:34 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt ... G1ktvI/16303131900: bad response
May 26 21:20:34 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "http-01", "status": "invalid", "error": { "type": "urn:acme:error:connection", "detail": "Fetching http://xxserver.asuscomm.com/.we ... Aphc2vxw8bDNXPxZtk: Timeout during connect (likely firewall problem)", "status": 400 }, "uri": "https://acme-v01.api.letsencrypt.org/acme/challenge/LXCqs2wCoXeL_cCFxV47NTFw9fd-1TPonFgY1G1ktvI/16303131900", "token": "6Hu_VJUirQ9oYJMYwB0ddvVQ2Aphc2vxw8bD
May 26 21:25:02 rc_service: service 3421:notify_rc restart_letsencrypt
May 26 21:25:31 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt ... fUYqDY/16303257028: bad response
May 26 21:25:31 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "http-01", "status": "invalid", "error": { "type": "urn:acme:error:connection", "detail": "Fetching http://xxserver.asuscomm.com/.we ... av0p4JaGkOKbKZ1lf0: Timeout during connect (likely firewall problem)", "status": 400 }, "uri": "https://acme-v01.api.letsencrypt.org/acme/challenge/rIMd0v42yKK8PMAWTqplubsSniEVc16BBm4MDfUYqDY/16303257028", "token": "ms1-dydjw4Bwb9UTf2P6OP0Twav0p4JaGkOK
May 26 21:30:01 rc_service: service 3541:notify_rc restart_letsencrypt
May 26 21:30:28 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt ... 5SQtE4/16303379875: bad response
May 26 21:30:28 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "http-01", "status": "invalid", "error": { "type": "urn:acme:error:connection", "detail": "Fetching http://xxserver.asuscomm.com/.we ... IRg7Uiqo3ZDaD0uKmI: Timeout during connect (likely firewall problem)", "status": 400 }, "uri": "https://acme-v01.api.letsencrypt.org/acme/challenge/GCMV9hR7RAnfxFGy86UzASTJPnyo0uwSanHzR5SQtE4/16303379875", "token": "m4x1_epfiqY5lj1NlcF2t5mZwIRg7Uiqo3ZD
May 26 21:35:01 rc_service: service 3664:notify_rc restart_letsencrypt
May 26 21:35:32 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt ... M_2Ko8/16303494242: bad response
May 26 21:35:32 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "http-01", "status": "invalid", "error": { "type": "urn:acme:error:connection", "detail": "Fetching http://xxserver.asuscomm.com/.we ... TQUXqolgnp3ejJ09Uk: Timeout during connect (likely firewall problem)", "status": 400 }, "uri": "https://acme-v01.api.letsencrypt.org/acme/challenge/ZWd0wVmEXVkSo4hMIViaLHGdAbYaJ6VcL3xcHM_2Ko8/16303494242", "token": "_V-L5yw7It-Q4oY-3Uet14-QzTQUXqolgnp3
May 26 21:40:01 rc_service: service 3785:notify_rc restart_letsencrypt
May 26 21:40:16 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz: bad HTTP: 429
May 26 21:40:16 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "urn:acme:error:rateLimited", "detail": "Error creating new authz :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/", "status": 429 }] (189 bytes)
May 26 21:45:02 rc_service: service 3906:notify_rc restart_letsencrypt
May 26 21:45:10 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz: bad HTTP: 429
May 26 21:45:10 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "urn:acme:error:rateLimited", "detail": "Error creating new authz :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/", "status": 429 }] (189 bytes)
May 26 21:50:01 rc_service: service 4025:notify_rc restart_letsencrypt
May 26 21:50:15 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz: bad HTTP: 429
May 26 21:50:15 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "urn:acme:error:rateLimited", "detail": "Error creating new authz :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/", "status": 429 }] (189 bytes)
May 26 21:55:01 rc_service: service 4149:notify_rc restart_letsencrypt
May 26 21:55:15 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz: bad HTTP: 429
May 26 21:55:15 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "urn:acme:error:rateLimited", "detail": "Error creating new authz :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/", "status": 429 }] (189 bytes)
May 26 22:00:01 rc_service: service 4272:notify_rc restart_letsencrypt
May 26 22:00:13 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz: bad HTTP: 429
May 26 22:00:13 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "urn:acme:error:rateLimited", "detail": "Error creating new authz :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/", "status": 429 }] (189 bytes)
May 26 22:05:02 rc_service: service 4397:notify_rc restart_letsencrypt
May 26 22:05:10 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz: bad HTTP: 429
May 26 22:05:10 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "urn:acme:error:rateLimited", "detail": "Error creating new authz :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/", "status": 429 }] (189 bytes)
May 26 22:10:02 rc_service: service 4515:notify_rc restart_letsencrypt
May 26 22:10:14 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz: bad HTTP: 429
May 26 22:10:14 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "urn:acme:error:rateLimited", "detail": "Error creating new authz :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/", "status": 429 }] (189 bytes)
May 26 22:15:02 rc_service: service 4636:notify_rc restart_letsencrypt
May 26 22:15:32 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt ... coeLkA/16304463770: bad response
May 26 22:15:32 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "http-01", "status": "invalid", "error": { "type": "urn:acme:error:connection", "detail": "Fetching http://xxserver.asuscomm.com/.we ... k3AusA6HbpTR0m81P8: Timeout during connect (likely firewall problem)", "status": 400 }, "uri": "https://acme-v01.api.letsencrypt.org/acme/challenge/_RnTjlu_RJkXopoc4On0K2czz9ileWUtvHFRrcoeLkA/16304463770", "token": "kq1UZtSQeAVg4N5G8571LjD1tk3AusA6HbpT
把DDNS頁面的let encrypt功能關閉試試看 你的固件版本是多少, 跟涵哥说的,先关闭let's encrypted ,目前是无法使用的,所以你说的那个应该不是这部分的问题
另外你投屏是如何操作?电视机吗?是手机和路由器的无线断开了么
固件版本：3.0.0.4.384_45717
投屏是爱奇艺投屏到小米电视，都是用的5G，断开瞬间电视上会显示缓冲，连接速度1K，然后几秒后断开 个人觉得和版本没有关系，中间换了很多个版本，梅林的也换过。。。
华为，小米，360，甚至是电信光猫自带的WIFI 都没有任何问题
另外有个现象，就是家里的佳能打印机经常会无法连接到 华硕的WIFI，但是只要华硕路由器重启，就可以连上去了，而且信号是满格，同样华为，小米，360，甚至是电信光猫自带的WIFI 都没有任何问题 teli 发表于 2019-5-31 10:37
个人觉得和版本没有关系，中间换了很多个版本，梅林的也换过。。。
华为，小米，360，甚至是电信光猫自带 ...
那你先把上面的let's encrypted的关闭,然后再看下system log吧,出现问题恢复后 你也可以点路由器里面的feedback 反应下,请官方的技术人员分析看看 Sprite 发表于 2019-5-31 10:46
那你先把上面的let's encrypted的关闭,然后再看下system log吧,出现问题恢复后 你也可以点路由器里面的fe ...
谢谢，关了外网进不去了，尴尬。。。。 teli 发表于 2019-5-31 10:55
谢谢，关了外网进不去了，尴尬。。。。
不是关DDNS啊,是把那個选项选到无,默认是let's encrypted的那个
页:
[1]