проблемы с сетью

AC1200 Двухдиапазонный гигабитный Wi‑Fi роутер
Ответить
nimfius
Сообщения: 3
Зарегистрирован: 08 окт 2020, 19:40

проблемы с сетью

Сообщение nimfius » 08 окт 2020, 19:45

Название темы: проблемы с сетью
Аппаратная версия устройства: 1
Версия встроенного ПО: V1_200722
Провайдер: baltcom
Системный журнал: ########################################################################## # AC12G System Log # Time = 2020-07-26 7:47:31 331032s # H-Ver = AC12G 1.0 00000000 : S-Ver = 1.0.2 Build 200722 Rel.39022n # L = 192.168.1.1 : M = 255.255.255.0 # WAN = DHCP : W = 185.7.239.24 : M = 255.255.252.0 : G = 185.7.236.1 # Cnt = 11008, Free = 10889, Busy = 119 ########################################################################## 0days, 00:00:01, LAN: Attach mirror0 to stack. 0days, 00:00:01, WAN: Attach interface eth1. 0days, 00:00:01, LAN: Set interface mirror0 ip=192.168.1.1 netmask 255.255.255.0. 0days, 00:00:01, HTTPD: Http server start! 0days, 00:00:04, WAN: Wan ethernet port plug on. 0days, 00:00:05, DHCPS: IP(C0A80066) not in dhcp pool or equal to server ip, ignore!!! 0days, 00:00:06, DHCPS: Send OFFER with ip 192.168.1.100. 0days, 00:00:06, DHCPC: Send DISCOVER with unicast flag 0. 0days, 00:00:06, DHCPS: Send ACK to 192.168.1.100. 0days, 00:00:06, DHCPC: Recv OFFER from server 89.201.0.1 with ip 185.7.239.24. 0days, 00:00:06, DHCPC: Send REQUEST to server 89.201.0.1 with request ip 185.7.239.24. 0days, 00:00:07, DHCPC: eth1 set ip 185.7.239.24 mask 255.255.252.0 gateway 185.7.236.1. 0days, 00:00:07, WAN: advanced ddns -wanChanged 0days, 00:06:12, DIAGNOSE: DNS server=217.198.224.11. 0days, 00:06:12, DIAGNOSE: Ping progress is now running with id=1024. 0days, 00:07:02, DIAGNOSE: Auto stopped, id=1024, sequence=49. 0days, 00:07:02, DIAGNOSE: Stop diagnose ping progress ....... 0days, 00:07:02, DIAGNOSE: Free context force. 0days, 02:17:17, DHCPS: Send OFFER with ip 192.168.1.101. 0days, 02:17:17, DHCPS: Send ACK to 192.168.1.101. 0days, 09:09:54, DHCPS: Send OFFER with ip 192.168.1.100. 0days, 09:09:54, DHCPS: Send ACK to 192.168.1.100. 0days, 18:12:10, DHCPS: Send OFFER with ip 192.168.1.100. 0days, 18:12:10, DHCPS: Send ACK to 192.168.1.100. 0days, 18:30:49, DHCPS: Send OFFER with ip 192.168.1.101. 0days, 18:30:49, DHCPS: Send ACK to 192.168.1.101. 1days, 01:04:02, DHCPS: Send OFFER with ip 192.168.1.102. 1days, 01:04:02, DHCPS: Send ACK to 192.168.1.102. 1days, 04:16:30, DHCPS: Send OFFER with ip 192.168.1.102. 1days, 04:16:30, DHCPS: Send ACK to 192.168.1.102. 1days, 09:44:55, DHCPS: Send OFFER with ip 192.168.1.102. 1days, 09:44:55, DHCPS: Send ACK to 192.168.1.102. 1days, 10:17:10, DHCPS: Send OFFER with ip 192.168.1.100. 1days, 10:17:10, DHCPS: Send ACK to 192.168.1.100. 1days, 17:50:01, DHCPS: Send OFFER with ip 192.168.1.101. 1days, 17:50:05, DHCPS: Send OFFER with ip 192.168.1.101. 1days, 17:50:13, DHCPS: Send OFFER with ip 192.168.1.101. 1days, 17:50:13, DHCPS: Send ACK to 192.168.1.101. 2days, 09:44:07, DHCPS: Send OFFER with ip 192.168.1.100. 2days, 09:44:07, DHCPS: Send ACK to 192.168.1.100. 2days, 09:44:51, DHCPS: Send OFFER with ip 192.168.1.102. 2days, 09:44:51, DHCPS: Send ACK to 192.168.1.102. 2days, 12:56:04, DHCPS: Send OFFER with ip 192.168.1.100. 2days, 12:56:04, DHCPS: Send ACK to 192.168.1.100. 2days, 16:36:42, DHCPS: Send OFFER with ip 192.168.1.101. 2days, 16:36:42, DHCPS: Send ACK to 192.168.1.101. 2days, 17:04:36, DHCPS: Lease host name not found. 2days, 17:04:36, DHCPS: Send OFFER with ip 192.168.1.101. 2days, 23:38:55, DHCPC: interface bring down. 2days, 23:38:55, WAN: advanced ddns -wanChanged 2days, 23:38:56, DHCPC: Send DISCOVER with unicast flag 0. 2days, 23:38:57, DHCPC: Recv OFFER from server 89.201.0.1 with ip 185.7.239.24. 2days, 23:38:57, DHCPC: Send REQUEST to server 89.201.0.1 with request ip 185.7.239.24. 2days, 23:38:58, DHCPC: eth1 set ip 185.7.239.24 mask 255.255.252.0 gateway 185.7.236.1. 2days, 23:38:58, WAN: advanced ddns -wanChanged 2days, 23:40:35, DIAGNOSE: DNS server=217.198.224.11. 2days, 23:40:35, DIAGNOSE: Ping progress is now running with id=1025. 2days, 23:40:38, DIAGNOSE: Stop diagnose ping progress ....... 2days, 23:40:38, DIAGNOSE: Free context force. 3days, 00:04:04, DHCPC: interface bring down. 3days, 00:04:04, WAN: advanced ddns -wanChanged 3days, 00:04:07, DHCPC: Send DISCOVER with unicast flag 0. 3days, 00:04:08, DHCPC: Recv OFFER from server 89.201.0.1 with ip 185.7.239.24. 3days, 00:04:08, DHCPC: Send REQUEST to server 89.201.0.1 with request ip 185.7.239.24. 3days, 00:04:09, DHCPC: eth1 set ip 185.7.239.24 mask 255.255.252.0 gateway 185.7.236.1. 3days, 00:04:09, WAN: advanced ddns -wanChanged 3days, 09:44:30, DHCPS: Send OFFER with ip 192.168.1.100. 3days, 09:44:30, DHCPS: Send ACK to 192.168.1.100. 3days, 09:44:43, DHCPS: Send OFFER with ip 192.168.1.102. 3days, 09:44:43, DHCPS: Send ACK to 192.168.1.102. 3days, 18:43:46, DHCPS: Send OFFER with ip 192.168.1.100. 3days, 18:43:46, DHCPS: Send ACK to 192.168.1.100. 3days, 18:46:21, DHCPS: Send OFFER with ip 192.168.1.101. 3days, 18:46:21, DHCPS: Send ACK to 192.168.1.101.
Описание проблемы: временами пропадает интернет ( в виндовсе подключение остается активным, но ни один сайт нельзя открыть, торенты тоже не качают). Провайдер говорит, что соединение не пропадает.

Дмитрий
Сообщения: 7
Зарегистрирован: 15 май 2020, 21:28

Re: проблемы с сетью

Сообщение Дмитрий » 08 окт 2020, 20:20

Пожалуйста, пришлите построчный лог, это очень тяжело разобрать кому-ни было.
Фактически отключение = обрыв кабеля, ровно точно также как и простое отключение, если его вытащить. В таких случаях в роутере фиксируется сообщение о том что WAN port is down (или что-то подобное).
Как правило само соединение (локальное) устанавливается вашим роутером с провайдером. (условно ВЫ=ПРОВАЙДЕР). Далее ваш роутер передаёт настройки к нему, после чего сам провайдер тоже устанавливает связь с вышестоящим оборудование (региональные трассы). Иными словами
Сам провайдер - это тоже такой же роутер который тоже просит интернет у кого-либо. И если в случае вашего лога - отключений не было. Это лишь подтверждает что отключение могло произойти на уровне провайдера вашего интернет провайдера. (извините за тавтологию). Для наглядности спросите лог журнала общей авторизации сервера провайдера, но я сомневаюсь что вам его пришлют, как правило эта информация недоступна пользователям из за условий договора (людям свойственно подписывать договор не вдумчиво). Когда такая ситуация происходит - у вас действительно не теряется соединение, ваша сессия с провайдером есть и работает. Но вот сессия между самим провайдером и уже его поставщиком связи может обрываться, у вас это никак не будет фиксироваться потому что не должно.

nimfius
Сообщения: 3
Зарегистрирован: 08 окт 2020, 19:40

Re: проблемы с сетью

Сообщение nimfius » 08 окт 2020, 22:11

Провайдер утверждает, что соединение не прерывается с ним вообще и в виндовсе так же не меняется иконка соединения. Просто скорость интернета становится нулевой.
##########################################################################
# AC12G System Log
# Time = 2020-07-26 7:47:31 331032s
# H-Ver = AC12G 1.0 00000000 : S-Ver = 1.0.2 Build 200722 Rel.39022n
# L = 192.168.1.1 : M = 255.255.255.0
# WAN = DHCP : W = 185.7.239.24 : M = 255.255.252.0 : G = 185.7.236.1
# Cnt = 11008, Free = 10889, Busy = 119
##########################################################################
0days, 00:00:01, LAN: Attach mirror0 to stack.
0days, 00:00:01, WAN: Attach interface eth1.
0days, 00:00:01, LAN: Set interface mirror0 ip=192.168.1.1 netmask 255.255.255.0.
0days, 00:00:01, HTTPD: Http server start!
0days, 00:00:04, WAN: Wan ethernet port plug on.
0days, 00:00:05, DHCPS: IP(C0A80066) not in dhcp pool or equal to server ip, ignore!!!
0days, 00:00:06, DHCPS: Send OFFER with ip 192.168.1.100.
0days, 00:00:06, DHCPC: Send DISCOVER with unicast flag 0.
0days, 00:00:06, DHCPS: Send ACK to 192.168.1.100.
0days, 00:00:06, DHCPC: Recv OFFER from server 89.201.0.1 with ip 185.7.239.24.
0days, 00:00:06, DHCPC: Send REQUEST to server 89.201.0.1 with request ip 185.7.239.24.
0days, 00:00:07, DHCPC: eth1 set ip 185.7.239.24 mask 255.255.252.0 gateway 185.7.236.1.
0days, 00:00:07, WAN: advanced ddns -wanChanged
0days, 00:06:12, DIAGNOSE: DNS server=217.198.224.11.
0days, 00:06:12, DIAGNOSE: Ping progress is now running with id=1024.
0days, 00:07:02, DIAGNOSE: Auto stopped, id=1024, sequence=49.
0days, 00:07:02, DIAGNOSE: Stop diagnose ping progress .......
0days, 00:07:02, DIAGNOSE: Free context force.
0days, 02:17:17, DHCPS: Send OFFER with ip 192.168.1.101.
0days, 02:17:17, DHCPS: Send ACK to 192.168.1.101.
0days, 09:09:54, DHCPS: Send OFFER with ip 192.168.1.100.
0days, 09:09:54, DHCPS: Send ACK to 192.168.1.100.
0days, 18:12:10, DHCPS: Send OFFER with ip 192.168.1.100.
0days, 18:12:10, DHCPS: Send ACK to 192.168.1.100.
0days, 18:30:49, DHCPS: Send OFFER with ip 192.168.1.101.
0days, 18:30:49, DHCPS: Send ACK to 192.168.1.101.
1days, 01:04:02, DHCPS: Send OFFER with ip 192.168.1.102.
1days, 01:04:02, DHCPS: Send ACK to 192.168.1.102.
1days, 04:16:30, DHCPS: Send OFFER with ip 192.168.1.102.
1days, 04:16:30, DHCPS: Send ACK to 192.168.1.102.
1days, 09:44:55, DHCPS: Send OFFER with ip 192.168.1.102.
1days, 09:44:55, DHCPS: Send ACK to 192.168.1.102.
1days, 10:17:10, DHCPS: Send OFFER with ip 192.168.1.100.
1days, 10:17:10, DHCPS: Send ACK to 192.168.1.100.
1days, 17:50:01, DHCPS: Send OFFER with ip 192.168.1.101.
1days, 17:50:05, DHCPS: Send OFFER with ip 192.168.1.101.
1days, 17:50:13, DHCPS: Send OFFER with ip 192.168.1.101.
1days, 17:50:13, DHCPS: Send ACK to 192.168.1.101.
2days, 09:44:07, DHCPS: Send OFFER with ip 192.168.1.100.
2days, 09:44:07, DHCPS: Send ACK to 192.168.1.100.
2days, 09:44:51, DHCPS: Send OFFER with ip 192.168.1.102.
2days, 09:44:51, DHCPS: Send ACK to 192.168.1.102.
2days, 12:56:04, DHCPS: Send OFFER with ip 192.168.1.100.
2days, 12:56:04, DHCPS: Send ACK to 192.168.1.100.
2days, 16:36:42, DHCPS: Send OFFER with ip 192.168.1.101.
2days, 16:36:42, DHCPS: Send ACK to 192.168.1.101.
2days, 17:04:36, DHCPS: Lease host name not found.
2days, 17:04:36, DHCPS: Send OFFER with ip 192.168.1.101.
2days, 23:38:55, DHCPC: interface bring down.
2days, 23:38:55, WAN: advanced ddns -wanChanged
2days, 23:38:56, DHCPC: Send DISCOVER with unicast flag 0.
2days, 23:38:57, DHCPC: Recv OFFER from server 89.201.0.1 with ip 185.7.239.24.
2days, 23:38:57, DHCPC: Send REQUEST to server 89.201.0.1 with request ip 185.7.239.24.
2days, 23:38:58, DHCPC: eth1 set ip 185.7.239.24 mask 255.255.252.0 gateway 185.7.236.1.
2days, 23:38:58, WAN: advanced ddns -wanChanged
2days, 23:40:35, DIAGNOSE: DNS server=217.198.224.11.
2days, 23:40:35, DIAGNOSE: Ping progress is now running with id=1025.
2days, 23:40:38, DIAGNOSE: Stop diagnose ping progress .......
2days, 23:40:38, DIAGNOSE: Free context force.
3days, 00:04:04, DHCPC: interface bring down.
3days, 00:04:04, WAN: advanced ddns -wanChanged
3days, 00:04:07, DHCPC: Send DISCOVER with unicast flag 0.
3days, 00:04:08, DHCPC: Recv OFFER from server 89.201.0.1 with ip 185.7.239.24.
3days, 00:04:08, DHCPC: Send REQUEST to server 89.201.0.1 with request ip 185.7.239.24.
3days, 00:04:09, DHCPC: eth1 set ip 185.7.239.24 mask 255.255.252.0 gateway 185.7.236.1.
3days, 00:04:09, WAN: advanced ddns -wanChanged
3days, 09:44:30, DHCPS: Send OFFER with ip 192.168.1.100.
3days, 09:44:30, DHCPS: Send ACK to 192.168.1.100.
3days, 09:44:43, DHCPS: Send OFFER with ip 192.168.1.102.
3days, 09:44:43, DHCPS: Send ACK to 192.168.1.102.
3days, 18:43:46, DHCPS: Send OFFER with ip 192.168.1.100.
3days, 18:43:46, DHCPS: Send ACK to 192.168.1.100.
3days, 18:46:21, DHCPS: Send OFFER with ip 192.168.1.101.
3days, 18:46:21, DHCPS: Send ACK to 192.168.1.101.

nimfius
Сообщения: 3
Зарегистрирован: 08 окт 2020, 19:40

Re: проблемы с сетью

Сообщение nimfius » 08 окт 2020, 22:13

Отключение происходит под нагрузкой, когда скорость интернета превышает 800 мбит

В сети
aureoli86
Сообщения: 23
Зарегистрирован: 13 май 2020, 18:51

Re: проблемы с сетью

Сообщение aureoli86 » 10 окт 2020, 22:46

nimfius писал(а):
08 окт 2020, 22:11
Провайдер утверждает, что соединение не прерывается с ним вообще и в виндовсе так же не меняется иконка соединения. Просто скорость интернета становится нулевой.
##########################################################################
# AC12G System Log
# Time = 2020-07-26 7:47:31 331032s
# H-Ver = AC12G 1.0 00000000 : S-Ver = 1.0.2 Build 200722 Rel.39022n
# L = 192.168.1.1 : M = 255.255.255.0
# WAN = DHCP : W = 185.7.239.24 : M = 255.255.252.0 : G = 185.7.236.1
# Cnt = 11008, Free = 10889, Busy = 119
##########################################################################
0days, 00:00:01, LAN: Attach mirror0 to stack.
0days, 00:00:01, WAN: Attach interface eth1.
0days, 00:00:01, LAN: Set interface mirror0 ip=192.168.1.1 netmask 255.255.255.0.
0days, 00:00:01, HTTPD: Http server start!
0days, 00:00:04, WAN: Wan ethernet port plug on.
0days, 00:00:05, DHCPS: IP(C0A80066) not in dhcp pool or equal to server ip, ignore!!!
0days, 00:00:06, DHCPS: Send OFFER with ip 192.168.1.100.
0days, 00:00:06, DHCPC: Send DISCOVER with unicast flag 0.
0days, 00:00:06, DHCPS: Send ACK to 192.168.1.100.
0days, 00:00:06, DHCPC: Recv OFFER from server 89.201.0.1 with ip 185.7.239.24.
0days, 00:00:06, DHCPC: Send REQUEST to server 89.201.0.1 with request ip 185.7.239.24.
0days, 00:00:07, DHCPC: eth1 set ip 185.7.239.24 mask 255.255.252.0 gateway 185.7.236.1.
0days, 00:00:07, WAN: advanced ddns -wanChanged
0days, 00:06:12, DIAGNOSE: DNS server=217.198.224.11.
0days, 00:06:12, DIAGNOSE: Ping progress is now running with id=1024.
0days, 00:07:02, DIAGNOSE: Auto stopped, id=1024, sequence=49.
0days, 00:07:02, DIAGNOSE: Stop diagnose ping progress .......
0days, 00:07:02, DIAGNOSE: Free context force.
0days, 02:17:17, DHCPS: Send OFFER with ip 192.168.1.101.
0days, 02:17:17, DHCPS: Send ACK to 192.168.1.101.
0days, 09:09:54, DHCPS: Send OFFER with ip 192.168.1.100.
0days, 09:09:54, DHCPS: Send ACK to 192.168.1.100.
0days, 18:12:10, DHCPS: Send OFFER with ip 192.168.1.100.
0days, 18:12:10, DHCPS: Send ACK to 192.168.1.100.
0days, 18:30:49, DHCPS: Send OFFER with ip 192.168.1.101.
0days, 18:30:49, DHCPS: Send ACK to 192.168.1.101.
1days, 01:04:02, DHCPS: Send OFFER with ip 192.168.1.102.
1days, 01:04:02, DHCPS: Send ACK to 192.168.1.102.
1days, 04:16:30, DHCPS: Send OFFER with ip 192.168.1.102.
1days, 04:16:30, DHCPS: Send ACK to 192.168.1.102.
1days, 09:44:55, DHCPS: Send OFFER with ip 192.168.1.102.
1days, 09:44:55, DHCPS: Send ACK to 192.168.1.102.
1days, 10:17:10, DHCPS: Send OFFER with ip 192.168.1.100.
1days, 10:17:10, DHCPS: Send ACK to 192.168.1.100.
1days, 17:50:01, DHCPS: Send OFFER with ip 192.168.1.101.
1days, 17:50:05, DHCPS: Send OFFER with ip 192.168.1.101.
1days, 17:50:13, DHCPS: Send OFFER with ip 192.168.1.101.
1days, 17:50:13, DHCPS: Send ACK to 192.168.1.101.
2days, 09:44:07, DHCPS: Send OFFER with ip 192.168.1.100.
2days, 09:44:07, DHCPS: Send ACK to 192.168.1.100.
2days, 09:44:51, DHCPS: Send OFFER with ip 192.168.1.102.
2days, 09:44:51, DHCPS: Send ACK to 192.168.1.102.
2days, 12:56:04, DHCPS: Send OFFER with ip 192.168.1.100.
2days, 12:56:04, DHCPS: Send ACK to 192.168.1.100.
2days, 16:36:42, DHCPS: Send OFFER with ip 192.168.1.101.
2days, 16:36:42, DHCPS: Send ACK to 192.168.1.101.
2days, 17:04:36, DHCPS: Lease host name not found.
2days, 17:04:36, DHCPS: Send OFFER with ip 192.168.1.101.
2days, 23:38:55, DHCPC: interface bring down.
2days, 23:38:55, WAN: advanced ddns -wanChanged
2days, 23:38:56, DHCPC: Send DISCOVER with unicast flag 0.
2days, 23:38:57, DHCPC: Recv OFFER from server 89.201.0.1 with ip 185.7.239.24.
2days, 23:38:57, DHCPC: Send REQUEST to server 89.201.0.1 with request ip 185.7.239.24.
2days, 23:38:58, DHCPC: eth1 set ip 185.7.239.24 mask 255.255.252.0 gateway 185.7.236.1.
2days, 23:38:58, WAN: advanced ddns -wanChanged
2days, 23:40:35, DIAGNOSE: DNS server=217.198.224.11.
2days, 23:40:35, DIAGNOSE: Ping progress is now running with id=1025.
2days, 23:40:38, DIAGNOSE: Stop diagnose ping progress .......
2days, 23:40:38, DIAGNOSE: Free context force.
3days, 00:04:04, DHCPC: interface bring down.
3days, 00:04:04, WAN: advanced ddns -wanChanged
3days, 00:04:07, DHCPC: Send DISCOVER with unicast flag 0.
3days, 00:04:08, DHCPC: Recv OFFER from server 89.201.0.1 with ip 185.7.239.24.
3days, 00:04:08, DHCPC: Send REQUEST to server 89.201.0.1 with request ip 185.7.239.24.
3days, 00:04:09, DHCPC: eth1 set ip 185.7.239.24 mask 255.255.252.0 gateway 185.7.236.1.
3days, 00:04:09, WAN: advanced ddns -wanChanged
3days, 09:44:30, DHCPS: Send OFFER with ip 192.168.1.100.
3days, 09:44:30, DHCPS: Send ACK to 192.168.1.100.
3days, 09:44:43, DHCPS: Send OFFER with ip 192.168.1.102.
3days, 09:44:43, DHCPS: Send ACK to 192.168.1.102.
3days, 18:43:46, DHCPS: Send OFFER with ip 192.168.1.100.
3days, 18:43:46, DHCPS: Send ACK to 192.168.1.100.
3days, 18:46:21, DHCPS: Send OFFER with ip 192.168.1.101.
3days, 18:46:21, DHCPS: Send ACK to 192.168.1.101.
Это похоже на проблему с физической линией. Попробуйте выяснить у провайдера следующие моменты: подайте нагрузку на порт, так как вы это делали ранее и уточните у инженеров "второй линии", у которых есть доступ к оборудованию, растут ли в этот момент ошибки CRC на порту, количество ошибок на порту, скорость и дуплекс физического линка.

Ответить