Archer C1200 периодически перезагружается после выключения компьютера

AC1200 Двухдиапазонный Wi-Fi гигабитный роутер
Ответить
andrey.vorobev
Сообщения: 2
Зарегистрирован: 08 янв 2019, 00:41

Archer C1200 периодически перезагружается после выключения компьютера

Сообщение andrey.vorobev » 08 янв 2019, 00:55

Название темы: Archer C1200 периодически перезагружается после выключения компьютера
Аппаратная версия устройства: EU V1.0
Провайдер: NetByNet
Тип подключения: Dynamic IP
Логи оборудования: Hardware Version: Archer C1200 v1.0
Software Version: 1.1.3 Build 20180124 rel.52299

2019-01-08 00:47:54 locale[14909]: <6> 283051 Language is changed to 'ru_RU'
2019-01-08 00:47:26 locale[14568]: <6> 283051 Language is changed to 'ru_RU'
2019-01-08 00:47:25 locale[14540]: <6> 283051 Language is changed to 'ru_RU'
2019-01-08 00:46:32 led-controller[693]: <6> 288051 Start to run LAN1_ON
2019-01-08 00:46:32 led-controller[693]: <7> 288004 LAN1_ON is found
2019-01-08 00:46:32 led-controller[693]: <7> 288003 Led rule name is LAN1_ON
2019-01-08 00:46:32 led-controller[693]: <7> 288001 Receive data length = 132
2019-01-08 00:46:32 led-controller[693]: <6> 288051 Start to run WAN1_ON
2019-01-08 00:46:32 led-controller[693]: <7> 288004 WAN1_ON is found
2019-01-08 00:46:32 led-controller[693]: <7> 288003 Led rule name is WAN1_ON
2019-01-08 00:46:32 led-controller[693]: <7> 288001 Receive data length = 132
2019-01-08 00:46:32 led-controller[693]: <6> 288051 Start to run WAN0_OFF
2019-01-08 00:46:32 led-controller[693]: <7> 288004 WAN0_OFF is found
2019-01-08 00:46:32 led-controller[693]: <7> 288003 Led rule name is WAN0_OFF
2019-01-08 00:46:32 led-controller[693]: <7> 288001 Receive data length = 132
2019-01-08 00:46:30 led-controller[693]: <6> 288051 Start to run LAN1_OFF
2019-01-08 00:46:30 led-controller[693]: <7> 288004 LAN1_OFF is found
2019-01-08 00:46:30 led-controller[693]: <7> 288003 Led rule name is LAN1_OFF
2019-01-08 00:46:30 led-controller[693]: <7> 288001 Receive data length = 132
2019-01-08 00:46:30 led-controller[693]: <6> 288051 Start to run WAN1_ON
2019-01-08 00:46:30 led-controller[693]: <7> 288004 WAN1_ON is found
2019-01-08 00:46:30 led-controller[693]: <7> 288003 Led rule name is WAN1_ON
2019-01-08 00:46:30 led-controller[693]: <7> 288001 Receive data length = 132
2019-01-08 00:46:30 led-controller[693]: <6> 288051 Start to run WAN0_OFF
2019-01-08 00:46:30 led-controller[693]: <7> 288004 WAN0_OFF is found
2019-01-08 00:46:30 led-controller[693]: <7> 288003 Led rule name is WAN0_OFF
2019-01-08 00:46:30 led-controller[693]: <7> 288001 Receive data length = 132
2019-01-08 00:46:28 led-controller[693]: <6> 288051 Start to run LAN1_ON
2019-01-08 00:46:28 led-controller[693]: <7> 288004 LAN1_ON is found
2019-01-08 00:46:28 led-controller[693]: <7> 288003 Led rule name is LAN1_ON
2019-01-08 00:46:28 led-controller[693]: <7> 288001 Receive data length = 132
2019-01-08 00:46:28 led-controller[693]: <6> 288051 Start to run WAN1_ON
2019-01-08 00:46:28 led-controller[693]: <7> 288004 WAN1_ON is found
2019-01-08 00:46:28 led-controller[693]: <7> 288003 Led rule name is WAN1_ON
2019-01-08 00:46:28 led-controller[693]: <7> 288001 Receive data length = 132
2019-01-08 00:46:28 led-controller[693]: <6> 288051 Start to run WAN0_OFF
2019-01-08 00:46:28 led-controller[693]: <7> 288004 WAN0_OFF is found
2019-01-08 00:46:28 led-controller[693]: <7> 288003 Led rule name is WAN0_OFF
2019-01-08 00:46:28 led-controller[693]: <7> 288001 Receive data length = 132
2019-01-08 00:46:25 led-controller[693]: <6> 288051 Start to run LAN1_OFF
2019-01-08 00:46:25 led-controller[693]: <7> 288004 LAN1_OFF is found
2019-01-08 00:46:25 led-controller[693]: <7> 288003 Led rule name is LAN1_OFF
2019-01-08 00:46:25 led-controller[693]: <7> 288001 Receive data length = 132
2019-01-08 00:46:25 led-controller[693]: <6> 288051 Start to run WAN1_ON
2019-01-08 00:46:25 led-controller[693]: <7> 288004 WAN1_ON is found
2019-01-08 00:46:25 led-controller[693]: <7> 288003 Led rule name is WAN1_ON
2019-01-08 00:46:25 led-controller[693]: <7> 288001 Receive data length = 132
2019-01-08 00:46:25 led-controller[693]: <6> 288051 Start to run WAN0_OFF
2019-01-08 00:46:25 led-controller[693]: <7> 288004 WAN0_OFF is found
2019-01-08 00:46:25 led-controller[693]: <7> 288003 Led rule name is WAN0_OFF
2019-01-08 00:46:25 led-controller[693]: <7> 288001 Receive data length = 132
2019-01-08 00:46:19 led-controller[693]: <6> 288051 Start to run LAN1_ON
2019-01-08 00:46:19 led-controller[693]: <7> 288004 LAN1_ON is found
2019-01-08 00:46:19 led-controller[693]: <7> 288003 Led rule name is LAN1_ON
2019-01-08 00:46:19 led-controller[693]: <7> 288001 Receive data length = 132
2019-01-08 00:46:19 led-controller[693]: <6> 288051 Start to run WAN1_ON
2019-01-08 00:46:19 led-controller[693]: <7> 288004 WAN1_ON is found
2019-01-08 00:46:19 led-controller[693]: <7> 288003 Led rule name is WAN1_ON
2019-01-08 00:46:19 led-controller[693]: <7> 288001 Receive data length = 132
2019-01-08 00:46:19 led-controller[693]: <6> 288051 Start to run WAN0_OFF
2019-01-08 00:46:19 led-controller[693]: <7> 288004 WAN0_OFF is found
2019-01-08 00:46:19 led-controller[693]: <7> 288003 Led rule name is WAN0_OFF
2019-01-08 00:46:19 led-controller[693]: <7> 288001 Receive data length = 132
2017-01-01 00:01:20 led-controller[693]: <6> 288051 Start to run WAN1_ON
2017-01-01 00:01:20 led-controller[693]: <7> 288004 WAN1_ON is found
2017-01-01 00:01:20 led-controller[693]: <7> 288003 Led rule name is WAN1_ON
2017-01-01 00:01:20 led-controller[693]: <7> 288001 Receive data length = 132
2017-01-01 00:01:20 led-controller[693]: <6> 288051 Start to run WAN0_OFF
2017-01-01 00:01:20 led-controller[693]: <7> 288004 WAN0_OFF is found
2017-01-01 00:01:20 led-controller[693]: <7> 288003 Led rule name is WAN0_OFF
2017-01-01 00:01:20 led-controller[693]: <7> 288001 Receive data length = 132
2017-01-01 00:01:04 upnp[4547]: <6> 217504 Service start
2017-01-01 00:01:03 upnp[4547]: <6> 217505 Service stop
2017-01-01 00:01:02 nat[3376]: <7> 211001 Flush conntrack
2017-01-01 00:01:02 nat[3376]: <6> 211021 IPSEC ALG enabled
2017-01-01 00:01:02 nat[3376]: <6> 211021 L2TP ALG enabled
2017-01-01 00:01:02 nat[3376]: <6> 211021 PPTP ALG enabled
2017-01-01 00:01:02 nat[3376]: <6> 211021 SIP ALG enabled
2017-01-01 00:01:02 nat[3376]: <6> 211021 RTSP ALG enabled
2017-01-01 00:01:02 nat[3376]: <6> 211021 H323 ALG enabled
2017-01-01 00:01:02 nat[3376]: <6> 211021 TFTP ALG enabled
2017-01-01 00:01:02 nat[3376]: <6> 211021 FTP ALG enabled
2017-01-01 00:00:57 led-controller[693]: <6> 288051 Start to run WAN1_OFF
2017-01-01 00:00:57 led-controller[693]: <7> 288004 WAN1_OFF is found
2017-01-01 00:00:57 led-controller[693]: <7> 288003 Led rule name is WAN1_OFF
2017-01-01 00:00:57 led-controller[693]: <7> 288001 Receive data length = 132
2017-01-01 00:00:57 led-controller[693]: <6> 288051 Start to run WAN0_ON
2017-01-01 00:00:57 led-controller[693]: <7> 288004 WAN0_ON is found
2017-01-01 00:00:57 led-controller[693]: <7> 288003 Led rule name is WAN0_ON
2017-01-01 00:00:57 led-controller[693]: <7> 288001 Receive data length = 132
2017-01-01 00:00:54 nat[3376]: <6> 211501 Initialization succeeded
2017-01-01 00:00:53 led-controller[693]: <6> 288051 Start to run WLAN5G_ON
2017-01-01 00:00:53 led-controller[693]: <7> 288004 WLAN5G_ON is found
2017-01-01 00:00:53 led-controller[693]: <7> 288003 Led rule name is WLAN5G_ON
2017-01-01 00:00:53 led-controller[693]: <7> 288001 Receive data length = 132
2017-01-01 00:00:53 led-controller[693]: <6> 288051 Start to run WLAN2G_ON
2017-01-01 00:00:53 led-controller[693]: <7> 288004 WLAN2G_ON is found
2017-01-01 00:00:53 led-controller[693]: <7> 288003 Led rule name is WLAN2G_ON
2017-01-01 00:00:53 led-controller[693]: <7> 288001 Receive data length = 132
2017-01-01 00:00:50 nat[3376]: <6> 211501 Initialization succeeded
2017-01-01 00:00:47 qos[3681]: <6> 259504 Service start
2017-01-01 00:00:47 qos[3681]: <6> 259503 Function disabled
2017-01-01 00:00:42 modem[864]: <7> 292036 backup: switch network to WIRED.
2017-01-01 00:00:41 led-controller[693]: <6> 288051 Start to run NIGHT
2017-01-01 00:00:41 led-controller[693]: <7> 288004 NIGHT is found
2017-01-01 00:00:41 led-controller[693]: <7> 288003 Led rule name is NIGHT
2017-01-01 00:00:41 led-controller[693]: <7> 288001 Receive data length = 132
2017-01-01 00:00:40 led-controller[693]: <6> 288051 Start to run GENERAL
2017-01-01 00:00:40 led-controller[693]: <6> 288051 Start to run Gernal on
2017-01-01 00:00:40 led-controller[693]: <7> 288004 GENERAL is found
2017-01-01 00:00:40 led-controller[693]: <7> 288003 Led rule name is GENERAL
2017-01-01 00:00:40 led-controller[693]: <7> 288001 Receive data length = 132
2017-01-01 00:00:40 led-controller[693]: <6> 288051 Start to run STATUS_ON
2017-01-01 00:00:40 led-controller[693]: <7> 288004 STATUS_ON is found
2017-01-01 00:00:40 led-controller[693]: <7> 288003 Led rule name is STATUS_ON
2017-01-01 00:00:40 led-controller[693]: <7> 288001 Receive data length = 132
2017-01-01 00:00:32 factory-reset[2977]: <6> 284504 Service start
2017-01-01 00:00:31 parental-control[2820]: <6> 229504 Service start
2017-01-01 00:00:31 parental-control[2820]: <5> 229606 Flush conntrack table succeeded
2017-01-01 00:00:31 parental-control[2820]: <6> 229502 Function enabled
2017-01-01 00:00:29 access-control[2742]: <6> 239504 Service start
2017-01-01 00:00:29 access-control[2742]: <5> 239606 Flush conntrack table succeeded
2017-01-01 00:00:29 access-control[2742]: <6> 239502 Function enabled
2017-01-01 00:00:29 nat[2444]: <7> 211001 Flush conntrack
2017-01-01 00:00:27 nat[2444]: <6> 211502 Function enabled
2017-01-01 00:00:27 nat[2444]: <5> 211051 Create NAT chain succeeded
2017-01-01 00:00:25 nat[2444]: <6> 211501 Initialization succeeded
2017-01-01 00:00:24 nat[2444]: <6> 211501 Initialization succeeded
2017-01-01 00:00:23 basic-security[2221]: <6> 219504 Service start
2017-01-01 00:00:23 basic-security[2221]: <5> 219606 Flush conntrack table succeeded
2017-01-01 00:00:21 firewall[1463]: <6> 209504 Service start
2017-01-01 00:00:14 imb[1763]: <6> 218507 Daemon connection succeeded
2017-01-01 00:00:14 imb[1763]: <6> 218012 ARP Binding disabled
2017-01-01 00:00:14 imb[1763]: <6> 218506 Config interface initialization succeeded
2017-01-01 00:00:14 imb[1763]: <6> 218501 Initialization succeeded
2017-01-01 00:00:13 upnp[1661]: <6> 217504 Service start
2017-01-01 00:00:12 upnp[1661]: <6> 217505 Service stop
2017-01-01 00:00:00 led-controller[693]: <6> 288051 Start to run STATUS_SAN
2017-01-01 00:00:00 led-controller[693]: <7> 288004 STATUS_SAN is found
2017-01-01 00:00:00 led-controller[693]: <7> 288003 Led rule name is STATUS_SAN
2017-01-01 00:00:00 led-controller[693]: <7> 288001 Receive data length = 132
1970-01-01 00:00:12 led-controller[693]: <6> 288504 Service start
1970-01-01 00:00:12 led-controller[693]: <7> 288002 Adding led WLAN5G
1970-01-01 00:00:12 led-controller[693]: <7> 288002 Adding led WLAN2G
1970-01-01 00:00:12 led-controller[693]: <7> 288002 Adding led STATUS
1970-01-01 00:00:12 led-controller[693]: <7> 288002 Adding led WAN2
1970-01-01 00:00:12 led-controller[693]: <7> 288002 Adding led WAN1
1970-01-01 00:00:12 led-controller[693]: <7> 288002 Adding led USB1
1970-01-01 00:00:12 led-controller[693]: <7> 288002 Adding led LAN4
1970-01-01 00:00:12 led-controller[693]: <7> 288002 Adding led LAN3
1970-01-01 00:00:12 led-controller[693]: <7> 288002 Adding led LAN2
1970-01-01 00:00:12 led-controller[693]: <7> 288002 Adding led LAN1
2018-08-22 00:55:37 led-controller[701]: <3> 288205 Socket was closed!
2018-08-22 00:55:30 led-controller[701]: <3> 288205 Socket was closed!
2018-08-22 00:55:22 led-controller[701]: <3> 288205 Socket was closed!
2018-08-22 00:52:32 led-controller[701]: <3> 288205 Socket was closed!
2018-08-22 00:51:38 led-controller[701]: <3> 288205 Socket was closed!
2018-08-22 00:47:29 led-controller[701]: <3> 288205 Socket was closed!
2018-08-22 00:41:05 led-controller[701]: <3> 288205 Socket was closed!
2018-08-22 00:37:03 led-controller[701]: <3> 288205 Socket was closed!
2018-08-22 00:35:59 led-controller[701]: <3> 288205 Socket was closed!
1970-01-01 00:00:45 access-control[4400]: <4> 239042 firewall framework is not loaded
Описание проблемы: В общем, Archer C1200 перезагружается через минут 5-10 после выключения компьютера, в основном ночью
Уровень сигнала от основного роутера: 4-5 делений

Goodwin
Модератор
Модератор
Сообщения: 3746
Зарегистрирован: 25 май 2011, 10:56
Страна: Россия

Re: Archer C1200 периодически перезагружается после выключения компьютера

Сообщение Goodwin » 08 янв 2019, 21:54

в основном? Т.е. не всегда? Опишите проблему подробнее. Пробовали с другим кабелем? С другим компьютером?
Перед тем, как создать тему, посетите раздел ЧАСТО ЗАДАВАЕМЫЕ ВОПРОСЫ
TP-LINK Archer C7v2
Личные сообщения по техническим проблемам без сообщения на форуме не рассматриваются!

andrey.vorobev
Сообщения: 2
Зарегистрирован: 08 янв 2019, 00:41

Re: Archer C1200 периодически перезагружается после выключения компьютера

Сообщение andrey.vorobev » 08 янв 2019, 22:46

Goodwin писал(а):
08 янв 2019, 21:54
в основном? Т.е. не всегда? Опишите проблему подробнее. Пробовали с другим кабелем? С другим компьютером?
Другого компьютера нет, с другим кабелем также. Винду переустановил, попробую поставить драйвер с сайта материнской платы.
После того как выключу компьютер,роутер выключается, сам перезагружается и восстанавливает соединение , а комп выключаю в полночь. Бывали случаи, когда роутер перезагружался прямо во время работы за компьютером.

aureoli86
Сообщения: 437
Зарегистрирован: 06 фев 2015, 12:07
Страна: Россия

Re: Archer C1200 периодически перезагружается после выключения компьютера

Сообщение aureoli86 » 10 янв 2019, 21:13

andrey.vorobev писал(а):
08 янв 2019, 22:46
Goodwin писал(а):
08 янв 2019, 21:54
в основном? Т.е. не всегда? Опишите проблему подробнее. Пробовали с другим кабелем? С другим компьютером?
Другого компьютера нет, с другим кабелем также. Винду переустановил, попробую поставить драйвер с сайта материнской платы.
После того как выключу компьютер,роутер выключается, сам перезагружается и восстанавливает соединение , а комп выключаю в полночь. Бывали случаи, когда роутер перезагружался прямо во время работы за компьютером.
Проверьте на бета прошивке
viewtopic.php?p=62300#p62300

Ответить

Вернуться в «Archer C1200»