> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/fr/hacking-wifi/wpa-wpa2-psk-network-attacks/packet-analysis/association-request-packet-analysis.md).

# Analyse des paquets de requête d’association

Analyser les paquets de requête d’association dans une capture sans fil autorisée.

Une requête d’association est envoyée par un client lorsqu’il se connecte à un point d’accès. Cette page montre comment identifier ces paquets et lister les adresses MAC des clients dans une capture.

Analysez des captures provenant de réseaux que vous possédez ou que vous êtes autorisé à évaluer.

### Filtrer les requêtes d’association

Le filtre `wlan.fc.type_subtype == 0` renvoie **les requêtes d’association**. Il ne renvoie pas les requêtes de sondage :

{% code overflow="wrap" %}

```bash
tshark -r CAPTURE-01.cap -Y "wlan.fc.type_subtype==0" 2>/dev/null
```

{% endcode %}

> 2539 11.827060 9e:8c:fb:49:d4:52 → TpLinkTechno\_62:45:e7 802.11 160 Requête d’association, SN=3067, FN=0, Flags=........, SSID="ATIC2"\
> 2541 11.831747 9e:8c:fb:49:d4:52 → TpLinkTechno\_62:45:e7 802.11 160 Requête d’association, SN=3067, FN=0, Flags=....R..., SSID="ATIC2"\
> 2546 11.846464 9e:8c:fb:49:d4:52 → TpLinkTechno\_62:45:e7 802.11 160 Requête d’association, SN=3067, FN=0, Flags=....R..., SSID="ATIC2"\
> 2582 11.940395 9e:8c:fb:49:d4:52 → TpLinkTechno\_62:45:e7 802.11 160 Requête d’association, SN=3070, FN=0, Flags=....R..., SSID="ATIC2"\
> 2585 11.945362 9e:8c:fb:49:d4:52 → TpLinkTechno\_62:45:e7 802.11 160 Requête d’association, SN=3070, FN=0, Flags=....R..., SSID="ATIC2"\
> 2590 11.961791 9e:8c:fb:49:d4:52 → TpLinkTechno\_62:45:e7 802.11 160 Requête d’association, SN=3070, FN=0, Flags=....R..., SSID="ATIC2"\
> 3533 22.271900 9e:8c:fb:49:d4:52 → TpLinkTechno\_62:45:e7 802.11 160 Requête d’association, SN=328, FN=0, Flags=........, SSID="ATIC2"\
> 17505 97.427531 8e:60:c4:67:1c:9f → TpLinkTechno\_62:45:e7 802.11 160 Requête d’association, SN=2458, FN=0, Flags=........, SSID="ATIC2"\
> 17930 98.859721 8e:60:c4:67:1c:9f → TpLinkTechno\_62:45:e7 802.11 160 Requête d’association, SN=1208, FN=0, Flags=........, SSID="ATIC2"\
> 20307 107.283060 8e:60:c4:67:1c:9f → TpLinkTechno\_62:45:e7 802.11 160 Requête d’association, SN=3937, FN=0, Flags=........, SSID="ATIC2"\
> 22489 116.717916 9e:8c:fb:49:d4:52 → TpLinkTechno\_62:45:e7 802.11 160 Requête d’association, SN=881, FN=0, Flags=........, SSID="ATIC2"

<figure><img src="https://3840167291-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2FqqYpjrNfCLytkTAy7okx%2F%7BD18AEEC5-2993-4D88-85C8-69DE6CE2EB6F%7D.png?alt=media&amp;token=440bbc50-fd9c-4779-87ff-fec9aa21855d" alt=""><figcaption></figcaption></figure>

La sortie montre des clients envoyant des requêtes d’association au point d’accès. Le `SSID` champ identifie le réseau demandé par chaque client.

### Lister les adresses MAC des clients

Extrayez l’adresse source des requêtes d’association. La commande suivante renvoie chaque adresse MAC de client une seule fois :

{% code overflow="wrap" %}

```bash
tshark -r CAPTURE-01.cap -Y "wlan.fc.type_subtype==0" -T fields -e wlan.sa 2>/dev/null | sort -u
```

{% endcode %}

<figure><img src="https://3840167291-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2FeOvZr0ahwSIsGVRiReUW%2F%7B703EA628-4976-4B61-9813-8D3FB06276EC%7D.png?alt=media&amp;token=2b75bda0-b50a-413c-b3cd-89bdda54c16a" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://hacking-notes.jord4n.pro/fr/hacking-wifi/wpa-wpa2-psk-network-attacks/packet-analysis/association-request-packet-analysis.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.