Difference between revisions of "NWMUDS:StartScan"
Jump to navigation
Jump to search
Line 53: | Line 53: | ||
|- | |- | ||
| 0 | | 0 | ||
− | | | + | | Two unknown u16s. |
|- | |- | ||
| 1 | | 1 | ||
− | | | + | | Two unknown u16s. |
|- | |- | ||
| 2-3 | | 2-3 | ||
Line 62: | Line 62: | ||
|- | |- | ||
| 4-12 | | 4-12 | ||
− | | | + | | Uninitialized for UDS. |
|} | |} | ||
Revision as of 21:11, 4 April 2016
Request
Index Word | Description |
---|---|
0 | Header code [0x000F0404] |
1 | Output buffer max size |
2-14 | 0x34-byte input structure. |
15 | wlancommID |
16 | This is the ID also located at offset 0xE in the CTR-generation structure. |
17 | Value 0x0 |
18 | Input event handle |
19 | (Size<<4) | 12 |
20 | Output BeaconDataReply buffer ptr |
Response
Index Word | Description |
---|---|
0 | Header code |
1 | Result code |
Input structure
Index Word | Description |
---|---|
0 | Two unknown u16s. |
1 | Two unknown u16s. |
2-3 | MAC address? The 6-bytes located here are normally all 0xFF. |
4-12 | Uninitialized for UDS. |
Description
This returns beacon data for all UDS wifi beacons received by this system.
Official user processes create a new event handle which is then passed to this command. However, those user processes don't save that handle anywhere afterwards.