In the earlier posts , we have learnt about the P2P Group formation Procedures and P2P power management procedures. In this post I have showed the sniffer captures that are useful in the WFD Protocol. Now, this post is linked with all other posts that I have written before, and you don’t feel it useful if you have not read the previous posts and you have not understood the WFD protocol. But if you just want to have a look at the P2P attributes and how they look at the wireshark, then you can find them here in the post. I have tried to get as many P2P Attributes as possible. This post is going to be final post about the WiFi Direct Protocol.
P2P IE Format
Now Lets see the sniffer capture for this P2P IE.
P2P Attributes
Above table shows the important P2P Attributes, and we will see their sniffer captures.
1. Status Attribute
Observe below capture for Status Attribute.
In the above figure , observe that status code can be the value from 0-255, and below table shows the possible status codes.
Observe the below few sniffer captures on the multiple status codes.
We see this this Attribute in the below frames.
| GO Negotiation Response frame |
| GO Negotiation Confirmation frame |
| P2P Invitation Response frames |
| P2P Presence Response frame |
2. Minor Reason Code Attribute
Observe the below few screen captures to see this attribute.
We see this this Attribute in the below frames.
| Deauthentication Frame |
| Disassociation Frame |
3. P2P Capability Attribute
Observe the below few screen captures to see this attribute.
We see this this Attribute in the below frames.
| Beacon frame |
| Probe Request frame |
| ProbeResponse frame |
| GO Negotiation Request frame |
| GO Negotiation Response frame |
| GO Negotiation Confirmation frame |
| (Re)association Request frame |
| Provision Discovery Request frame |
4. P2P Device ID Attribute
Observe the below capture to check this sniffer.
We see this Attribute in the below frames.
| Beacon Frame |
| Device Discoverability Request Frame |
5. Group Owner Intent Attribute
We see this Attribute in the below frames.
| GO Negotiation Request frame |
| GO Negotiation Response frame |
6. Configuration Timeout Attribute
Observe the below capture to check this frame.
We see this Attribute in the below frames.
| GO Negotiation Request frame |
| GO Negotiation Response frame |
| P2P Invitation Request frame |
| P2P Invitation Response frame |
7. Listen Channel Attribute
Observe the below capture to see this frame.
We see this Attribute in the below frames.
| Probe Request frame |
| GO Negotiation Request frame |
8. P2P Group BSSID Attribute
Observe the beloew capture for this attribute.
We see this Attribute in the below frames.
| P2P Invitation Request frame |
| P2P Invitation Response frame |
9. Extended Listen Timing Attribute
Observe the below capture to check this Attribute.
We see this Attribute in the below frames.
| Probe Request frame |
| Probe Response frame |
| GO Negotiation Request frame |
| (Re)Association Response frame |
| (Re)association Request frame |
10. Intended P2P Interface Address Attribute
Observe the below capture to check this.
We see this Attribute in the below frames.
| GO Negotiation Request Frame |
| GO Negotiation Response Frame |
11. P2P Manageability Attribute
The P2P Manageability attribute shall be included in Beacon, Probe Response, and (Re)association Response frames if it is supported.
We see this Attribute in the below frames.
| Beacon Frame |
| Probe Response Frame |
| (Re)association Response Frame |
12. Channel List Attribute
We see this Attribute in the below frames.
| GO Negotiation Request frame |
| GO Negotiation Response frame |
| GO Negotiation Confirmation frame |
| P2P Invitation Request frame |
| P2P Invitation Response frame |
13. Notice of Absence Attribute
Observe the below capture to check this Attribute.
We see this Attribute in the below frames.
| Beacon frame | |
| Probe Response frame | |
| Notice of Absence frame | |
| P2P Presence Request frame | |
| P2P Presence Response frame |
14. P2P Device Info
Observe the capture below to check this frame.
We see this Attribute in the below frames.
| (Re)association Request Frame |
| Probe Response frame Frame |
| GO Negotiation Request Frame |
| GO Negotiation Response Frame |
| Provision Discovery Request Frame |
15. P2P Group Info Attribute
Observe the below capture to see this attribute.
We see this Attribute in the below frame.
| Probe Response Frame |
16. P2P Group ID
Observe the below capture.
We see this Attribute in the below frame.
| P2P Invitation Request Frame |
17. P2P Interface attribute
We see this Attribute in the below frame.
| (Re)association Request Frame |
18. Operating Channel Attribute
Observe the below capture to see this. Wireshark is not able to decode this.
We see this Attribute in the below frames.
| Probe Request frame |
| GO Negotiation Request frame |
| GO Negotiation Response frame |
| GO Negotiation Confirmation frame |
| P2P Invitation Request frame |
| P2P Invitation Response frame |
19. Invitation Flags attribute
We see this Attribute in the below frame.
| P2P Invitation Request frame |
P2P Public Action Frames
Below frames are the P2P Public Action Frames. And we have seen about the frames in the earlier posts as well.
You can have a look about Type 0, Type 1 and Type 2 of the Public Action Frames and their usage from the below links.
Public Action frames Type 4 and Type 5 can be seen from the below link.
Public Action frames Type 6 and Type 7 can be seen from the below link.
P2P Group Owner Services for Discovery
Public Action frames Type 7 and Type 8 can be seen from the below link.
P2P Provision Discovery Req/Res
P2P Action Frames
The below table shows the P2P Action Frames.
You can have a look at Type 0 Action frame from the below link.
You can find the Type 1 and Type 2 of P2P Action Frames from the below link.
You can find the Type 3 P2P Action Frame from the below link.
GO Discoverability Request Action Frame
Service Discovery Action Frames
The Service Discovery Query frame uses the GAS Initial Request action frame. We have seen all the sniffer captures already in the earlier posts about service discovery procedures. You can have a look at the below link for the detailed analysis of Service Discovery Procedure in P2P.
Service Discovery Request Frame.
The below are the Service discovery Content.
Find the below frame format for service discovery request frame.
Below are the service protocol types that will be sent in Service Discovery Request/Response Frames.
Find the below sniffer capture for Service Discovery Request Frame.
Service Discovery Response Frame
Find the below frame format for Service Discovery Response Frame Format.
Below figure is the status codes for service discovery.
Find the below service discovery Response Sniffer Frame.
These are the multiple posts related to the WFD Protocol, And with this I have finished writing about the WFD Protocol.
Praneeth's Blog 