vanhoefm / krackattacks-scripts

Other
3.3k stars 770 forks source link

Using an 8814au driver- Results for ./krack-test-client.py seems incomplete #67

Closed pittzgal closed 5 years ago

pittzgal commented 5 years ago

Hi, I am using an 8814au Realtek driver and when i issued the make -j 2 command, I got a fatal:no names found, cannot describe anything at the start of the results. After executing ./krack-test-client.py I get the following: [19:30:34] Note: disable Wi-Fi in network manager & disable hardware encryption. Both may interfere with this script. [19:30:34] Starting hostapd ... Configuration file: /home/krackattacks-scripts/krackattack/hostapd.conf Using interface wlan0 with hwaddr 18:d6:c7:07:52:bd and ssid "testnetwork" wlan0: interface state UNINITIALIZED->ENABLED wlan0: AP-ENABLED [19:30:35] Ready. Connect to this Access Point to start the tests. Make sure the client requests an IP using DHCP! [19:30:36] Reset PN for GTK [19:30:38] Reset PN for GTK [19:30:41] Reset PN for GTK [19:30:43] Reset PN for GTK [19:30:45] Reset PN for GTK [19:30:47] Reset PN for GTK [19:30:49] Reset PN for GTK [19:30:52] Reset PN for GTK [19:30:54] Reset PN for GTK [19:30:56] Reset PN for GTK wlan0: STA 90:61:ae:18:18:de IEEE 802.11: associated wlan0: AP-STA-CONNECTED 90:61:ae:18:18:de wlan0: STA 90:61:ae:18:18:de RADIUS: starting accounting session 123A11F7AF81F4DE [19:30:58] 90:61:ae:18:18:de: 4-way handshake completed (RSN) [19:30:58] 90:61:ae:18:18:de: DHCP reply 192.168.100.2 to 90:61:ae:18:18:de [19:30:59] Reset PN for GTK [19:31:01] Reset PN for GTK [19:31:03] Reset PN for GTK [19:31:05] Reset PN for GTK [19:31:07] Reset PN for GTK wlan0: STA 90:61:ae:18:18:de IEEE 802.11: associated wlan0: STA 90:61:ae:18:18:de RADIUS: starting accounting session 123A11F7AF81F4DE [19:31:08] 90:61:ae:18:18:de: 4-way handshake completed (RSN) [19:31:09] Reset PN for GTK [19:31:11] Reset PN for GTK [19:31:12] 90:61:ae:18:18:de: DHCP reply 192.168.100.2 to 90:61:ae:18:18:de [19:31:14] Reset PN for GTK [19:31:16] Reset PN for GTK [19:31:18] Reset PN for GTK [19:31:21] Reset PN for GTK [19:31:23] Reset PN for GTK [19:31:25] Reset PN for GTK wlan0: STA 90:61:ae:18:18:de IEEE 802.11: associated wlan0: STA 90:61:ae:18:18:de RADIUS: starting accounting session 123A11F7AF81F4DE [19:31:26] 90:61:ae:18:18:de: 4-way handshake completed (RSN) [19:31:28] Reset PN for GTK [19:31:30] Reset PN for GTK [19:31:32] Reset PN for GTK [19:31:34] Reset PN for GTK [19:31:36] Reset PN for GTK wlan0: STA 90:61:ae:18:18:de IEEE 802.11: associated wlan0: STA 90:61:ae:18:18:de RADIUS: starting accounting session 123A11F7AF81F4DE [19:31:37] 90:61:ae:18:18:de: 4-way handshake completed (RSN) [19:31:38] Reset PN for GTK [19:31:40] Reset PN for GTK [19:31:42] Reset PN for GTK [19:31:44] Reset PN for GTK [19:31:46] Reset PN for GTK [19:31:48] Reset PN for GTK [19:31:50] Reset PN for GTK [19:31:52] Reset PN for GTK

What could be the reason for this? Is the driver not supported or there is an issue somewhere else? Thanks in advance!

pittzgal commented 5 years ago

UPDATE: It was the driver, changed the dongle and was able to see results