Jump to content
Как правильно добавить self-test и прочую отладку в тему
Где взять тестовые сборки
Официальное хранилище ПО в виде файлов
  • 0

Постоянно отваливается Wi-Fi

Zaklepkin

Asked by Zaklepkin,

 Share

Question

Zaklepkin Newbie

Zaklepkin

Posted
Posted

Keenetic Ultra (KN-1810) на прошивке 2.15.C.5.0-0 - постоянно отваливается Wi-Fi на 2.4ГГц. Уже ширину канала ограничил 20МГц, канал поставил свободный совсем. Не помогает.

11 answers to this question

Recommended Posts

  • 0
vasek00 Honored Flooder

vasek00

Posted
Posted (edited)
10 часов назад, Zaklepkin сказал:

Прикладываю файлы сразу после инцидента. 

log.txt 366 \u041a\u0431 · 1 download self-test.txt 682 \u041a\u0431 · 1 download

Наверное лучше сказать проблема на клиенте

Скрытый текст 

known host ZyXEL-Keenetic-Viva 12:7b:ef:5b:dc:74
ip dhcp host 12:7b:ef:5b:dc:74 192.168.100.100


Клиент подключился и получил IP от роутера
[I] Jul 20 10:37:02 wmond: WifiMaster0/AccessPoint0: (MT7615) STA(12:7b:ef:5b:dc:74) had associated successfully.
[I] Jul 20 10:37:02 wmond: WifiMaster0/AccessPoint0: (MT7615) STA(12:7b:ef:5b:dc:74) set key done in WPA2/WPA2PSK.
[I] Jul 20 10:37:04 ndhcps: DHCPDISCOVER received  from 12:7b:ef:5b:dc:74.
[I] Jul 20 10:37:04 ndhcps: making OFFER of 192.168.100.100 to 12:7b:ef:5b:dc:74.
[I] Jul 20 10:37:11 ndhcps: DHCPDISCOVER received  from 12:7b:ef:5b:dc:74.
[I] Jul 20 10:37:11 ndhcps: making OFFER of 192.168.100.100 to 12:7b:ef:5b:dc:74.
[I] Jul 20 10:37:25 ndhcps: DHCPDISCOVER received  from 12:7b:ef:5b:dc:74.
[I] Jul 20 10:37:25 ndhcps: making OFFER of 192.168.100.100 to 12:7b:ef:5b:dc:74.
[I] Jul 20 10:37:29 wmond: WifiMaster0/AccessPoint0: (MT7615) STA(30:cd:a7:8e:88:1e) set key done in WPA2/WPA2PSK.
[I] Jul 20 10:37:30 wmond: WifiMaster0/AccessPoint0: (MT7615) STA(c4:50:06:41:20:11) set key done in WPA2/WPA2PSK.
[I] Jul 20 10:37:31 wmond: WifiMaster0/AccessPoint0: (MT7615) STA(08:ec:a9:d9:da:98) replay counter differs in key handshaking.
[I] Jul 20 10:37:31 wmond: WifiMaster0/AccessPoint0: (MT7615) STA(08:ec:a9:d9:da:98) set key done in WPA2/WPA2PSK.
[I] Jul 20 10:37:31 wmond: WifiMaster0/AccessPoint0: (MT7615) STA(38:aa:3c:47:96:eb) set key done in WPA2/WPA2PSK.
[I] Jul 20 10:37:38 wmond: WifiMaster1/AccessPoint0: (MT7615) STA(e4:40:e2:05:38:06) set key done in WPA2/WPA2PSK.
[I] Jul 20 10:37:38 wmond: WifiMaster1/AccessPoint0: (MT7615) STA(ec:9b:f3:70:4f:c8) set key done in WPA2/WPA2PSK.
[I] Jul 20 10:37:39 wmond: WifiMaster1/AccessPoint0: (MT7615) STA(2c:0e:3d:50:e8:bf) set key done in WPA2/WPA2PSK.
[I] Jul 20 10:40:37 wmond: WifiMaster0/AccessPoint0: (MT7615) STA(12:7b:ef:5b:dc:74) had associated successfully.
[I] Jul 20 10:40:37 wmond: WifiMaster0/AccessPoint0: (MT7615) STA(12:7b:ef:5b:dc:74) set key done in WPA2/WPA2PSK.
[I] Jul 20 10:40:39 ndhcps: DHCPDISCOVER received  from 12:7b:ef:5b:dc:74.
[I] Jul 20 10:40:39 ndhcps: making OFFER of 192.168.100.100 to 12:7b:ef:5b:dc:74.
[I] Jul 20 10:40:46 ndhcps: DHCPDISCOVER received  from 12:7b:ef:5b:dc:74.
[I] Jul 20 10:40:46 ndhcps: making OFFER of 192.168.100.100 to 12:7b:ef:5b:dc:74.
[I] Jul 20 10:43:12 wmond: WifiMaster0/AccessPoint0: (MT7615) STA(12:7b:ef:5b:dc:74) had associated successfully.
[I] Jul 20 10:43:13 wmond: Core::Syslog: last message repeated 18 times.
[I] Jul 20 10:43:16 wmond: WifiMaster0/AccessPoint0: (MT7615) STA(12:7b:ef:5b:dc:74) pairwise key handshaking timeout.
[I] Jul 20 10:43:16 wmond: WifiMaster0/AccessPoint0: (MT7615) STA(12:7b:ef:5b:dc:74) had deauthenticated by AP (reason: PTK 4-way handshake timeout).
[I] Jul 20 10:43:53 wmond: WifiMaster0/AccessPoint0: (MT7615) STA(12:7b:ef:5b:dc:74) had associated successfully.
[I] Jul 20 10:43:54 wmond: Core::Syslog: last message repeated 18 times.
[I] Jul 20 10:43:57 wmond: WifiMaster0/AccessPoint0: (MT7615) STA(12:7b:ef:5b:dc:74) pairwise key handshaking timeout.
[I] Jul 20 10:43:57 wmond: WifiMaster0/AccessPoint0: (MT7615) STA(12:7b:ef:5b:dc:74) had deauthenticated by AP (reason: PTK 4-way handshake timeout).

И далее так и повторяееться 
[I] Jul 21 03:18:47 wmond: WifiMaster0/AccessPoint0: (MT7615) STA(12:7b:ef:5b:dc:74) had associated successfully.
[I] Jul 21 03:18:47 wmond: WifiMaster0/AccessPoint0: (MT7615) STA(12:7b:ef:5b:dc:74) set key done in WPA2/WPA2PSK.
[I] Jul 21 03:18:50 ndhcps: DHCPDISCOVER received  from 12:7b:ef:5b:dc:74.
[I] Jul 21 03:18:50 ndhcps: making OFFER of 192.168.100.100 to 12:7b:ef:5b:dc:74.
[I] Jul 21 03:18:57 ndhcps: DHCPDISCOVER received  from 12:7b:ef:5b:dc:74.
[I] Jul 21 03:18:57 ndhcps: making OFFER of 192.168.100.100 to 12:7b:ef:5b:dc:74.
[I] Jul 21 03:19:11 ndhcps: DHCPDISCOVER received  from 12:7b:ef:5b:dc:74.
[I] Jul 21 03:19:11 ndhcps: making OFFER of 192.168.100.100 to 12:7b:ef:5b:dc:74.
[I] Jul 21 03:19:32 ndhcps: DHCPDISCOVER received  from 12:7b:ef:5b:dc:74.
[I] Jul 21 03:19:32 ndhcps: making OFFER of 192.168.100.100 to 12:7b:ef:5b:dc:74.
[I] Jul 21 03:20:24 wmond: WifiMaster0/AccessPoint0: (MT7615) STA(12:7b:ef:5b:dc:74) had associated successfully.
[I] Jul 21 03:20:24 wmond: Core::Syslog: last message repeated 12 times.
[I] Jul 21 03:20:27 wmond: WifiMaster0/AccessPoint0: (MT7615) STA(12:7b:ef:5b:dc:74) pairwise key handshaking timeout.
[I] Jul 21 03:20:27 wmond: WifiMaster0/AccessPoint0: (MT7615) STA(12:7b:ef:5b:dc:74) had deauthenticated by AP (reason: PTK 4-way handshake timeout).
[I] Jul 21 03:21:04 wmond: WifiMaster0/AccessPoint0: (MT7615) STA(12:7b:ef:5b:dc:74) had associated successfully.
[I] Jul 21 03:21:04 wmond: Core::Syslog: last message repeated 2 times.
[I] Jul 21 03:21:07 wmond: WifiMaster0/AccessPoint0: (MT7615) STA(12:7b:ef:5b:dc:74) pairwise key handshaking timeout.
[I] Jul 21 03:21:07 wmond: WifiMaster0/AccessPoint0: (MT7615) STA(12:7b:ef:5b:dc:74) had deauthenticated by AP (reason: PTK 4-way handshake timeout).
[I] Jul 21 03:21:40 wmond: WifiMaster0/AccessPoint0: (MT7615) STA(12:7b:ef:5b:dc:74) had associated successfully.
[I] Jul 21 03:21:40 wmond: Core::Syslog: last message repeated 3 times.
[I] Jul 21 03:21:40 wmond: WifiMaster0/AccessPoint0: (MT7615) STA(12:7b:ef:5b:dc:74) set key done in WPA2/WPA2PSK.
[I] Jul 21 03:21:44 ndhcps: DHCPDISCOVER received  from 12:7b:ef:5b:dc:74.
[I] Jul 21 03:21:44 ndhcps: making OFFER of 192.168.100.100 to 12:7b:ef:5b:dc:74.
[I] Jul 21 03:21:51 ndhcps: DHCPDISCOVER received  from 12:7b:ef:5b:dc:74.
[I] Jul 21 03:21:51 ndhcps: making OFFER of 192.168.100.100 to 12:7b:ef:5b:dc:74.
[I] Jul 21 03:22:18 wmond: WifiMaster0/AccessPoint0: (MT7615) STA(12:7b:ef:5b:dc:74) had associated successfully.
[I] Jul 21 03:22:18 wmond: Core::Syslog: last message repeated 2 times.
[I] Jul 21 03:22:18 wmond: WifiMaster0/AccessPoint0: (MT7615) STA(12:7b:ef:5b:dc:74) set key done in WPA2/WPA2PSK.
[I] Jul 21 03:22:22 ndhcps: DHCPDISCOVER received  from 12:7b:ef:5b:dc:74.
[I] Jul 21 03:22:22 ndhcps: making OFFER of 192.168.100.100 to 12:7b:ef:5b:dc:74.
[I] Jul 21 03:22:29 ndhcps: DHCPDISCOVER received  from 12:7b:ef:5b:dc:74.
[I] Jul 21 03:22:29 ndhcps: making OFFER of 192.168.100.100 to 12:7b:ef:5b:dc:74.
[I] Jul 21 03:22:43 ndhcps: DHCPDISCOVER received  from 12:7b:ef:5b:dc:74.
[I] Jul 21 03:22:43 ndhcps: making OFFER of 192.168.100.100 to 12:7b:ef:5b:dc:74.
[I] Jul 21 03:24:41 wmond: WifiMaster0/AccessPoint0: (MT7615) STA(12:7b:ef:5b:dc:74) had associated successfully.
[I] Jul 21 03:24:42 wmond: Core::Syslog: last message repeated 2 times.

И так же что-то про неправельный ключ

[I] Jul 21 03:29:47 ndhcps: DHCPREQUEST received (STATE_SELECTING) for 192.168.100.100 from 12:7b:ef:5b:dc:74.
[I] Jul 21 03:29:47 ndhcps: sending ACK of 192.168.100.100 to 12:7b:ef:5b:dc:74.
[I] Jul 21 03:33:33 wmond: WifiMaster0/AccessPoint0: (MT7615) STA(30:cd:a7:8e:88:1e) set key done in WPA2/WPA2PSK.
[I] Jul 21 03:33:33 wmond: WifiMaster0/AccessPoint0: (MT7615) STA(c4:50:06:41:20:11) set key done in WPA2/WPA2PSK.
[I] Jul 21 03:33:34 wmond: WifiMaster0/AccessPoint0: (MT7615) STA(08:ec:a9:d9:da:98) replay counter differs in key handshaking.
[I] Jul 21 03:33:34 wmond: WifiMaster0/AccessPoint0: (MT7615) STA(08:ec:a9:d9:da:98) set key done in WPA2/WPA2PSK.
[I] Jul 21 03:33:37 wmond: WifiMaster1/AccessPoint0: (MT7615) STA(ec:9b:f3:70:4f:c8) set key done in WPA2/WPA2PSK.
[I] Jul 21 03:33:37 wmond: WifiMaster1/AccessPoint0: (MT7615) STA(2c:0e:3d:50:e8:bf) set key done in WPA2/WPA2PSK.
[I] Jul 21 03:33:38 wmond: WifiMaster1/AccessPoint0: (MT7615) STA(e4:40:e2:05:38:06) set key done in WPA2/WPA2PSK.
[I] Jul 21 03:34:12 wmond: WifiMaster0/AccessPoint0: (MT7615) STA(12:7b:ef:5b:dc:74) had associated successfully.
...
[I] Jul 21 06:34:38 ndm: kernel: AP 2.4GHz: run channel auto-switch
[I] Jul 21 06:34:41 ndm: kernel: ACS result: Primary Channel 8, Min Channel Busy = 522, BW = 20
[I] Jul 21 06:34:41 wmond: WifiMaster0/AccessPoint0: (MT7615) BSS(ra0) channel switched to 8.
...
[I] Jul 21 06:34:59 ndhcps: received DHCP packet on br0 from: 0.0.0.0 12:7b:ef:5b:dc:74 ndhcpc Keenetic_Viva via 12:7b:ef:5b:dc:74
...
I] Jul 21 06:34:59 ndhcps: DHCPDISCOVER received  from 12:7b:ef:5b:dc:74.
[I] Jul 21 06:34:59 ndhcps: checking current leases...
[I] Jul 21 06:34:59 ndhcps: searching for free IP address...
[I] Jul 21 06:34:59 ndhcps: offering lease: 192.168.100.100 12:7b:ef:5b:dc:74 911263 requested no Keenetic_Viva ndhcpc
[I] Jul 21 06:34:59 nvox: Get FW version cfm: result 0
[I] Jul 21 06:34:59 ndhcps: making OFFER of 192.168.100.100 to 12:7b:ef:5b:dc:74.
...
[I] Jul 21 06:35:00 ndhcps: received DHCP packet on br0 from: 0.0.0.0 12:7b:ef:5b:dc:74 ndhcpc Keenetic_Viva via 12:7b:ef:5b:dc:74
[I] Jul 21 06:35:00 wmond: WifiMaster0/AccessPoint0: (MT7615) STA(30:cd:a7:8e:88:1e) had re-associated successfully.
[I] Jul 21 06:35:00 wmond: WifiMaster0/AccessPoint0: (MT7615) STA(30:cd:a7:8e:88:1e) set key done in WPA2/WPA2PSK.
...
[I] Jul 21 06:35:01 ndhcps: 1: 192.168.100.100 12:7b:ef:5b:dc:74 936344 bind no Keenetic_Viva ndhcpc
[I] Jul 21 06:35:01 ndhcps: 2: 192.168.100.103 64:9e:f3:76:9b:d3 926758 bind yes SEP649EF3769BD3 unknown
[I] Jul 21 06:35:01 ndhcps: 3: 192.168.100.107 10:c3:7b:95:a7:12 933703 bind yes NeoVX unknown
[I] Jul 21 06:35:01 ndhcps: 4: 192.168.100.111 2c:0e:3d:50:e8:bf 924501 bind yes Galaxy-S6-edge unknown
[I] Jul 21 06:35:01 ndhcps: 5: 192.168.100.128 ec:9b:f3:70:4f:c8 928023 bind yes Galaxy-S6 unknown
[I] Jul 21 06:35:01 ndhcps: 6: 192.168.100.130 e4:40:e2:05:38:06 926758 bind yes android-578b4fe15e4a67fa unknown
[I] Jul 21 06:35:01 ndhcps: 7: 192.168.100.133 c4:50:06:41:20:11 936340 bind yes android-c292f58c9f046b2d dhcpcd-5.5.6
[I] Jul 21 06:35:01 ndhcps: 8: 192.168.100.156 08:ec:a9:d9:da:98 936338 bind yes android-f00818676ca55a dhcpcd-5.5.6

 

 

Да и по подробней про Keenetic_Viva

Edited by vasek00
  • 0
Zaklepkin Newbie

Zaklepkin

Posted
  • Author
Posted
On 7/21/2019 at 6:55 AM, Zaklepkin said:

Так отваливается все - мобильные, планшеты, Viva....

Просто Viva явно заметно, так как тупо пропадает интернет на ПК, что подключены к ней.

  • 0
vasek00 Honored Flooder

vasek00

Posted
Posted
17 минут назад, Zaklepkin сказал:

Так отваливается все - мобильные, планшеты, Viva....

Просто Viva явно заметно, так как тупо пропадает интернет на ПК, что подключены к ней.

Посмотрите основы работы wi-fi - только один клиент может передавать данные, остальные только слушают.

Отключите на время viva и посмотрите, так же вопрос не на базе ли 7620 данная viva.

  • 0
Zaklepkin Newbie

Zaklepkin

Posted
  • Author
Posted
8 minutes ago, vasek00 said:

Посмотрите основы работы wi-fi - только один клиент может передавать данные, остальные только слушают.

Отключите на время viva и посмотрите, так же вопрос не на базе ли 7620 данная viva. 

Viva сейчас выкл, планшеты продолжили отваливаться в том же режиме. То есть связь то есть, то нет. Восстанавливается через некоторое время сама по себе.

Если зайти в веб-интерфейс Ultra и пожмакать по вкладкам, то подключение у всех тотчас восстанавливается.

  • 0
Mamay Honored Flooder

Mamay

Posted
Posted
1 минуту назад, Zaklepkin сказал:

Черная Viva II

Таковой НЕТ в природе. Чёрная Viva не имеет цифру 2 - это раз.

Второе - да это 7620

  • 0
vasek00 Honored Flooder

vasek00

Posted
Posted
1 минуту назад, Zaklepkin сказал:

Viva сейчас выкл, планшеты продолжили отваливаться в том же режиме. То есть связь то есть, то нет. Восстанавливается через некоторое время сама по себе.

Если зайти в веб-интерфейс Ultra и пожмакать по вкладкам, то подключение у всех тотчас восстанавливается. 

Нужно смотреть логи без нее так же.

  • 0
Mamay Honored Flooder

Mamay

Posted
Posted (edited)
4 минуты назад, Zaklepkin сказал:

Если зайти в веб-интерфейс Ultra и пожмакать по вкладкам, то подключение у всех тотчас восстанавливается.

У вас из разряда, то потухнет, то погаснет. Для начала сходите к официалам, так как у вас актуальная модель и прошивка.

Edited by Mamay
  • 0
MDP Honored Flooder

MDP

Posted
Posted
25 минут назад, Mamay сказал:

Таковой НЕТ в природе. Чёрная Viva....

 

🤣🤣🤣🤣 ...звучит как страшилка на ночь. Жила была Белая Гига, и каждую ночь к ней приходила Чёрная причЁрная Вива ))))).....отдай мои каналы!!!

  • 0
Mamay Honored Flooder

Mamay

Posted
Posted
4 минуты назад, MDP сказал:

.....отдай мои каналы!!!

Не поверишь. Я намедни в один из филиалов написал главному бухгалтеру (далее цитата):

(14:45) Mamay: Погоняйте там у вас народ. Пусть анал освободят. Иначе мы с вами не сможем установить драйверы!
(14:45) Mamay: *канал )))

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 Share
Go to question listing

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...