Ноутбук с модулем https://ark.intel.com/products/89450/Intel-Dual-Band-Wireless-AC-3165 под Windows 10 и драйверов от 10.01.2018 версии 19.51.11.2 - при выходе из сна, ноутбук получает по Wi-Fi адрес 169.x.x.x. Отключение и подключение к сети не помогает, приходится в сетевых подключениях адаптер отключать и включать заново (либо из диспетчера устройств). Причём такое поведение именно на Windows 10 на разных ноутбуках с разными адаптерами. MAC-адрес я нулями забил, так-то мак нормально отображается. Причем это происходит только тогда, когда ноутбук из сна выходит. Ещё, конечно же, помогает ребут. На своём ноуте я обновил дрова на Wi-Fi - стало появляться сильно реже. Но на ноуте, что ниже (лог), корпоративный и там особо не пообновляешь драйвера.
Mar 26 23:02:57wmondWifiMaster0/AccessPoint0: (RT2860) STA(00:00:00:00:00:00) had been aged-out and disassociated.
Mar 26 23:02:57wmondWifiMaster0/AccessPoint0: (RT2860) STA(00:00:00:00:00:00) had associated successfully.
Mar 26 23:02:58wmondWifiMaster0/AccessPoint0: (RT2860) STA(00:00:00:00:00:00) set key done in WPA2/WPA2PSK.
Mar 26 23:02:58ndhcpsDHCPREQUEST received (STATE_INIT) for 192.168.3.2 from 00:00:00:00:00:00.
Mar 26 23:02:58ndhcpssending ACK of 192.168.3.2 to 00:00:00:00:00:00.
Mar 26 23:03:07wmondWifiMaster0/AccessPoint0: (RT2860) STA(00:00:00:00:00:00) had been aged-out and disassociated.
Mar 26 23:03:07wmondWifiMaster0/AccessPoint0: (RT2860) STA(00:00:00:00:00:00) had associated successfully.
Mar 26 23:03:08wmondWifiMaster0/AccessPoint0: (RT2860) STA(00:00:00:00:00:00) set key done in WPA2/WPA2PSK.
Mar 26 23:03:08ndhcpsDHCPREQUEST received (STATE_INIT) for 192.168.3.2 from 00:00:00:00:00:00.
Mar 26 23:03:08ndhcpssending ACK of 192.168.3.2 to 00:00:00:00:00:00.
Mar 26 23:03:15wmondWifiMaster0/AccessPoint0: (RT2860) STA(00:00:00:00:00:00) had been aged-out and disassociated.
Mar 26 23:03:15wmondWifiMaster0/AccessPoint0: (RT2860) STA(00:00:00:00:00:00) had associated successfully.
Mar 26 23:03:16wmondWifiMaster0/AccessPoint0: (RT2860) STA(00:00:00:00:00:00) set key done in WPA2/WPA2PSK.
Mar 26 23:03:16ndhcpsDHCPREQUEST received (STATE_INIT) for 192.168.3.2 from 00:00:00:00:00:00.
Mar 26 23:03:16ndhcpssending ACK of 192.168.3.2 to 00:00:00:00:00:00.
Apr 22 18:57:57wmondWifiMaster0/AccessPoint1: (RT2860) STA(xx:aa:bb:cc:ee:qq) had associated successfully.
Apr 22 18:57:58wmondWifiMaster0/AccessPoint1: (RT2860) STA(xx:aa:bb:cc:ee:qq) set key done in WPA2/WPA2PSK.
Apr 22 18:57:58ndhcpsDHCPDISCOVER received for 10.1.30.38 from xx:aa:bb:cc:ee:qq.
Apr 22 18:57:58ndhcpsmaking OFFER of 10.1.30.38 to xx:aa:bb:cc:ee:qq.
Apr 22 18:57:58ndhcpsDHCPREQUEST received (STATE_SELECTING) for 10.1.30.38 from xx:aa:bb:cc:ee:qq.
Apr 22 18:57:58ndmkernel: SWNAT bind table cleared
Apr 22 18:57:58ndhcpssending ACK of 10.1.30.38 to xx:aa:bb:cc:ee:qq.
Apr 22 19:01:31wmondWifiMaster0/AccessPoint1: (RT2860) STA(xx:aa:bb:cc:ee:qq) had deauthenticated.
Apr 22 19:01:32wmondWifiMaster0/AccessPoint1: (RT2860) STA(xx:aa:bb:cc:ee:qq) had associated successfully.
Apr 22 19:01:32wmondWifiMaster0/AccessPoint1: (RT2860) STA(xx:aa:bb:cc:ee:qq) set key done in WPA2/WPA2PSK.
Apr 22 19:01:32ndhcpsDHCPREQUEST received (STATE_INIT) for 10.1.30.38 from xx:aa:bb:cc:ee:qq.
Apr 22 19:01:32ndhcpssending ACK of 10.1.30.38 to xx:aa:bb:cc:ee:qq.
Apr 22 19:01:35ndhcpsDHCPREQUEST received (STATE_INIT) for 10.1.30.38 from xx:aa:bb:cc:ee:qq.
Apr 22 19:01:35ndhcpssending ACK of 10.1.30.38 to xx:aa:bb:cc:ee:qq.
Apr 22 19:01:35wmondWifiMaster0/AccessPoint1: (RT2860) STA(xx:aa:bb:cc:ee:qq) had been aged-out and disassociated.
Apr 22 19:01:36wmondWifiMaster0/AccessPoint1: (RT2860) STA(xx:aa:bb:cc:ee:qq) had associated successfully.
Apr 22 19:01:36wmondWifiMaster0/AccessPoint1: (RT2860) STA(xx:aa:bb:cc:ee:qq) set key done in WPA2/WPA2PSK.
Apr 22 19:01:36ndhcpsDHCPREQUEST received (STATE_INIT) for 10.1.30.38 from xx:aa:bb:cc:ee:qq.
Apr 22 19:01:36ndhcpssending ACK of 10.1.30.38 to xx:aa:bb:cc:ee:qq.
Apr 22 19:03:18wmondWifiMaster0/AccessPoint1: (RT2860) STA(xx:aa:bb:cc:ee:qq) had deauthenticated.
Apr 22 19:03:24ndmkernel: SWNAT bind table cleared
Apr 22 19:03:27wmondWifiMaster0/AccessPoint1: (RT2860) STA(xx:aa:bb:cc:ee:qq) had associated successfully.
Apr 22 19:03:28wmondWifiMaster0/AccessPoint1: (RT2860) STA(xx:aa:bb:cc:ee:qq) set key done in WPA2/WPA2PSK.
Apr 22 19:03:28ndhcpsDHCPREQUEST received (STATE_INIT) for 10.1.30.38 from xx:aa:bb:cc:ee:qq.
Apr 22 19:03:28ndmkernel: IPv4 conntrack lan: flushed 56 entries with address 10.1.30.38
Apr 22 19:03:28ndmkernel: SWNAT bind table cleared
Apr 22 19:03:28ndhcpssending ACK of 10.1.30.38 to xx:aa:bb:cc:ee:qq.
При чем это происходит как при подключении рабочего ноута к госетвой сети (10.1.x.x) так и при подключении личного ноута к домашней сети (192.168.1.x).
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.
Question
JIABP
Giga 2, 2.10.C.2.0-4
Ноутбук с модулем https://ark.intel.com/products/89450/Intel-Dual-Band-Wireless-AC-3165 под Windows 10 и драйверов от 10.01.2018 версии 19.51.11.2 - при выходе из сна, ноутбук получает по Wi-Fi адрес 169.x.x.x. Отключение и подключение к сети не помогает, приходится в сетевых подключениях адаптер отключать и включать заново (либо из диспетчера устройств). Причём такое поведение именно на Windows 10 на разных ноутбуках с разными адаптерами. MAC-адрес я нулями забил, так-то мак нормально отображается. Причем это происходит только тогда, когда ноутбук из сна выходит. Ещё, конечно же, помогает ребут. На своём ноуте я обновил дрова на Wi-Fi - стало появляться сильно реже. Но на ноуте, что ниже (лог), корпоративный и там особо не пообновляешь драйвера.
Mar 26 23:02:57wmondWifiMaster0/AccessPoint0: (RT2860) STA(00:00:00:00:00:00) had been aged-out and disassociated. Mar 26 23:02:57wmondWifiMaster0/AccessPoint0: (RT2860) STA(00:00:00:00:00:00) had associated successfully. Mar 26 23:02:58wmondWifiMaster0/AccessPoint0: (RT2860) STA(00:00:00:00:00:00) set key done in WPA2/WPA2PSK. Mar 26 23:02:58ndhcpsDHCPREQUEST received (STATE_INIT) for 192.168.3.2 from 00:00:00:00:00:00. Mar 26 23:02:58ndhcpssending ACK of 192.168.3.2 to 00:00:00:00:00:00. Mar 26 23:03:07wmondWifiMaster0/AccessPoint0: (RT2860) STA(00:00:00:00:00:00) had been aged-out and disassociated. Mar 26 23:03:07wmondWifiMaster0/AccessPoint0: (RT2860) STA(00:00:00:00:00:00) had associated successfully. Mar 26 23:03:08wmondWifiMaster0/AccessPoint0: (RT2860) STA(00:00:00:00:00:00) set key done in WPA2/WPA2PSK. Mar 26 23:03:08ndhcpsDHCPREQUEST received (STATE_INIT) for 192.168.3.2 from 00:00:00:00:00:00. Mar 26 23:03:08ndhcpssending ACK of 192.168.3.2 to 00:00:00:00:00:00. Mar 26 23:03:15wmondWifiMaster0/AccessPoint0: (RT2860) STA(00:00:00:00:00:00) had been aged-out and disassociated. Mar 26 23:03:15wmondWifiMaster0/AccessPoint0: (RT2860) STA(00:00:00:00:00:00) had associated successfully. Mar 26 23:03:16wmondWifiMaster0/AccessPoint0: (RT2860) STA(00:00:00:00:00:00) set key done in WPA2/WPA2PSK. Mar 26 23:03:16ndhcpsDHCPREQUEST received (STATE_INIT) for 192.168.3.2 from 00:00:00:00:00:00. Mar 26 23:03:16ndhcpssending ACK of 192.168.3.2 to 00:00:00:00:00:00.
Другой ноутбук (рабочий), с Win 10, и модулем https://www.intel.ru/content/www/ru/ru/products/wireless/wireless-products/dual-band-wireless-ac-8265.html - то же самое - при выходе из сна не получает IP и необходимо отключать/включать адаптер, т.к. отключение от сети и повторное подключение не помогает.
Apr 22 18:57:57wmondWifiMaster0/AccessPoint1: (RT2860) STA(xx:aa:bb:cc:ee:qq) had associated successfully. Apr 22 18:57:58wmondWifiMaster0/AccessPoint1: (RT2860) STA(xx:aa:bb:cc:ee:qq) set key done in WPA2/WPA2PSK. Apr 22 18:57:58ndhcpsDHCPDISCOVER received for 10.1.30.38 from xx:aa:bb:cc:ee:qq. Apr 22 18:57:58ndhcpsmaking OFFER of 10.1.30.38 to xx:aa:bb:cc:ee:qq. Apr 22 18:57:58ndhcpsDHCPREQUEST received (STATE_SELECTING) for 10.1.30.38 from xx:aa:bb:cc:ee:qq. Apr 22 18:57:58ndmkernel: SWNAT bind table cleared Apr 22 18:57:58ndhcpssending ACK of 10.1.30.38 to xx:aa:bb:cc:ee:qq. Apr 22 19:01:31wmondWifiMaster0/AccessPoint1: (RT2860) STA(xx:aa:bb:cc:ee:qq) had deauthenticated. Apr 22 19:01:32wmondWifiMaster0/AccessPoint1: (RT2860) STA(xx:aa:bb:cc:ee:qq) had associated successfully. Apr 22 19:01:32wmondWifiMaster0/AccessPoint1: (RT2860) STA(xx:aa:bb:cc:ee:qq) set key done in WPA2/WPA2PSK. Apr 22 19:01:32ndhcpsDHCPREQUEST received (STATE_INIT) for 10.1.30.38 from xx:aa:bb:cc:ee:qq. Apr 22 19:01:32ndhcpssending ACK of 10.1.30.38 to xx:aa:bb:cc:ee:qq. Apr 22 19:01:35ndhcpsDHCPREQUEST received (STATE_INIT) for 10.1.30.38 from xx:aa:bb:cc:ee:qq. Apr 22 19:01:35ndhcpssending ACK of 10.1.30.38 to xx:aa:bb:cc:ee:qq. Apr 22 19:01:35wmondWifiMaster0/AccessPoint1: (RT2860) STA(xx:aa:bb:cc:ee:qq) had been aged-out and disassociated. Apr 22 19:01:36wmondWifiMaster0/AccessPoint1: (RT2860) STA(xx:aa:bb:cc:ee:qq) had associated successfully. Apr 22 19:01:36wmondWifiMaster0/AccessPoint1: (RT2860) STA(xx:aa:bb:cc:ee:qq) set key done in WPA2/WPA2PSK. Apr 22 19:01:36ndhcpsDHCPREQUEST received (STATE_INIT) for 10.1.30.38 from xx:aa:bb:cc:ee:qq. Apr 22 19:01:36ndhcpssending ACK of 10.1.30.38 to xx:aa:bb:cc:ee:qq. Apr 22 19:03:18wmondWifiMaster0/AccessPoint1: (RT2860) STA(xx:aa:bb:cc:ee:qq) had deauthenticated. Apr 22 19:03:24ndmkernel: SWNAT bind table cleared Apr 22 19:03:27wmondWifiMaster0/AccessPoint1: (RT2860) STA(xx:aa:bb:cc:ee:qq) had associated successfully. Apr 22 19:03:28wmondWifiMaster0/AccessPoint1: (RT2860) STA(xx:aa:bb:cc:ee:qq) set key done in WPA2/WPA2PSK. Apr 22 19:03:28ndhcpsDHCPREQUEST received (STATE_INIT) for 10.1.30.38 from xx:aa:bb:cc:ee:qq. Apr 22 19:03:28ndmkernel: IPv4 conntrack lan: flushed 56 entries with address 10.1.30.38 Apr 22 19:03:28ndmkernel: SWNAT bind table cleared Apr 22 19:03:28ndhcpssending ACK of 10.1.30.38 to xx:aa:bb:cc:ee:qq.
При чем это происходит как при подключении рабочего ноута к госетвой сети (10.1.x.x) так и при подключении личного ноута к домашней сети (192.168.1.x).
Edited by JIABP9 answers to this question
Recommended Posts
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.