From 2575806958c969ec693c933e4d197b44bcb02dbe Mon Sep 17 00:00:00 2001 From: Mathy Vanhoef Date: Tue, 11 May 2021 18:59:52 +0400 Subject: [PATCH] fragattacks: clarify example pcaps --- example-pcaps/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/example-pcaps/README.md b/example-pcaps/README.md index bca55119c..b0ae3ee90 100644 --- a/example-pcaps/README.md +++ b/example-pcaps/README.md @@ -1,6 +1,6 @@ # Example Packet Captures -In all the following captures the Wi-Fi network is `testnetwork` with as password `abcdefgh`. +The following captures are based on executing the test tool and **illustrate the root cause** of the vulnerabilities. In all captures the Wi-Fi network being used has SSID `testnetwork` with password `abcdefgh`. Note that the captures were made on the same network card that was injecting packets (with hardware encryption disabled). On Linux, **injected packets are shown twice in a network capture**. First it shows the frame as injected by userspace (the test tool will always set the `Has Seqnum` and `Order` in the radiotap header). After the frame was sent, the Linux kernel echoes the actual transmitted frame a second time. This second frame for instance contains the bitrate that was used to send the frame and whether an acknowledgement was received in response.