> 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/es/hacking-wifi/wpa-wpa2-psk-network-attacks/packet-analysis/association-request-packet-analysis.md).

# Análisis de paquetes de solicitud de asociación

Analiza paquetes de solicitud de asociación en una captura inalámbrica autorizada.

Una solicitud de asociación es enviada por un cliente al unirse a un punto de acceso. Esta página muestra cómo identificar estos paquetes y enumerar las direcciones MAC de los clientes en una captura.

Analiza capturas de redes que posees o que estás autorizado a evaluar.

### Filtrar solicitudes de asociación

El filtro `wlan.fc.type_subtype == 0` devuelve **solicitudes de asociación**. No devuelve solicitudes de sondeo:

{% 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 Solicitud de asociación, SN=3067, FN=0, Flags=........, SSID="ATIC2"\
> 2541 11.831747 9e:8c:fb:49:d4:52 → TpLinkTechno\_62:45:e7 802.11 160 Solicitud de asociación, SN=3067, FN=0, Flags=....R..., SSID="ATIC2"\
> 2546 11.846464 9e:8c:fb:49:d4:52 → TpLinkTechno\_62:45:e7 802.11 160 Solicitud de asociación, SN=3067, FN=0, Flags=....R..., SSID="ATIC2"\
> 2582 11.940395 9e:8c:fb:49:d4:52 → TpLinkTechno\_62:45:e7 802.11 160 Solicitud de asociación, SN=3070, FN=0, Flags=....R..., SSID="ATIC2"\
> 2585 11.945362 9e:8c:fb:49:d4:52 → TpLinkTechno\_62:45:e7 802.11 160 Solicitud de asociación, SN=3070, FN=0, Flags=....R..., SSID="ATIC2"\
> 2590 11.961791 9e:8c:fb:49:d4:52 → TpLinkTechno\_62:45:e7 802.11 160 Solicitud de asociación, SN=3070, FN=0, Flags=....R..., SSID="ATIC2"\
> 3533 22.271900 9e:8c:fb:49:d4:52 → TpLinkTechno\_62:45:e7 802.11 160 Solicitud de asociación, SN=328, FN=0, Flags=........, SSID="ATIC2"\
> 17505 97.427531 8e:60:c4:67:1c:9f → TpLinkTechno\_62:45:e7 802.11 160 Solicitud de asociación, SN=2458, FN=0, Flags=........, SSID="ATIC2"\
> 17930 98.859721 8e:60:c4:67:1c:9f → TpLinkTechno\_62:45:e7 802.11 160 Solicitud de asociación, SN=1208, FN=0, Flags=........, SSID="ATIC2"\
> 20307 107.283060 8e:60:c4:67:1c:9f → TpLinkTechno\_62:45:e7 802.11 160 Solicitud de asociación, SN=3937, FN=0, Flags=........, SSID="ATIC2"\
> 22489 116.717916 9e:8c:fb:49:d4:52 → TpLinkTechno\_62:45:e7 802.11 160 Solicitud de asociación, SN=881, FN=0, Flags=........, SSID="ATIC2"

<figure><img src="https://754079710-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 salida muestra clientes enviando solicitudes de asociación al punto de acceso. El `SSID` campo identifica la red solicitada por cada cliente.

### Listar direcciones MAC de los clientes

Extrae la dirección de origen de las solicitudes de asociación. El siguiente comando devuelve cada dirección MAC de cliente una sola vez:

{% 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://754079710-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/es/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.