NWMUDS:StartScan - Revision history

Steveice10: Steveice10 moved page NWMUDS:RecvBeaconBroadcastData to NWMUDS:StartScan

2023-07-23T04:38:51Z

Steveice10 moved page NWMUDS:RecvBeaconBroadcastData to NWMUDS:StartScan

← Older revision		Revision as of 08:38, 23 July 2023
(No difference)

Yellows8: /* Description */

2016-04-06T21:42:27Z

Description

← Older revision		Revision as of 01:42, 7 April 2016
Line 47:		Line 47:

	=Description=		=Description=
	This returns beacon data for all UDS wifi beacons received by this system.		This returns beacon data for all UDS wifi beacons received by this system, with the specified wlancommID+ID8. See also the scaninput struct.

	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.		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.

			This command can ''only'' be used when not connected to a network.

Yellows8 at 15:13, 5 April 2016

2016-04-05T13:13:29Z

@@ Line 12: / Line 12: @@
 |-
 | 2-14
-| 0x34-byte input structure.
+| Input [[NWM_Services|ScanInputStruct]].
 |-
 | 15
@@ Line 44: / Line 44: @@
 | 1
 | Result code
 |}

Yellows8: /* Input structure */

2016-04-04T18:11:13Z

Input structure

← Older revision		Revision as of 22:11, 4 April 2016
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
	\| ~~Unknown, usually zero / uninitialized?~~		\| Uninitialized for UDS.
	\|}		\|}

Yellows8 at 01:14, 4 April 2016

2016-04-03T23:14:31Z

← Older revision		Revision as of 03:14, 4 April 2016
Line 24:		Line 24:
	\|-		\|-
	\| 18		\| 18
	\| Input handle		\| Input event handle
	\|-		\|-
	\| 19		\| 19
Line 67:		Line 67:
	=Description=		=Description=
	This returns beacon data for all UDS wifi beacons received by this system.		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.

Yellows8 at 00:56, 4 April 2016

2016-04-03T22:56:59Z

← Older revision		Revision as of 02:56, 4 April 2016
Line 64:		Line 64:
	\| Unknown, usually zero / uninitialized?		\| Unknown, usually zero / uninitialized?
	\|}		\|}

			=Description=
			This returns beacon data for all UDS wifi beacons received by this system.

Yellows8 at 00:53, 4 April 2016

2016-04-03T22:53:46Z

← Older revision		Revision as of 02:53, 4 April 2016
Line 30:		Line 30:
	\|-		\|-
	\| 20		\| 20
	\| Output buffer ptr		\| Output [[NWM_Services\|BeaconDataReply]] buffer ptr
	\|}		\|}

Line 64:		Line 64:
	\| Unknown, usually zero / uninitialized?		\| Unknown, usually zero / uninitialized?
	\|}		\|}

	~~=Description=~~
	The input maxsize is written to outbuf+0. The total amount of data written to the output starting at offset 0x0, is written to outbuf+4. Outbuf+8 is zero when the buffer contains no actual received data, 1 otherwise. Therefore, when the output contains no actual received data the size value at outbuf+4 is set to 0xC.

	The following is the structure of the data at outbuf+0xC. The data starting at +0x1C is the data from the entire raw beacon data, starting at the 802.11 management frame header. It's unknown what exactly the data prior to that is.

Yellows8 at 23:45, 3 April 2016

2016-04-03T21:45:39Z

@@ Line 11: / Line 11: @@
 | Output buffer max size
 |-
-| 2
+| 2-14
-| ?
+| 0x34-byte input structure.
 |-
 | 15
@@ Line 53: / Line 44: @@
 | 1
 | Result code
 |}

Yellows8: /* Description */

2014-09-21T23:23:08Z

Description

← Older revision		Revision as of 03:23, 22 September 2014
Line 57:		Line 57:
	=Description=		=Description=
	The input maxsize is written to outbuf+0. The total amount of data written to the output starting at offset 0x0, is written to outbuf+4. Outbuf+8 is zero when the buffer contains no actual received data, 1 otherwise. Therefore, when the output contains no actual received data the size value at outbuf+4 is set to 0xC.		The input maxsize is written to outbuf+0. The total amount of data written to the output starting at offset 0x0, is written to outbuf+4. Outbuf+8 is zero when the buffer contains no actual received data, 1 otherwise. Therefore, when the output contains no actual received data the size value at outbuf+4 is set to 0xC.

			The following is the structure of the data at outbuf+0xC. The data starting at +0x1C is the data from the entire raw beacon data, starting at the 802.11 management frame header. It's unknown what exactly the data prior to that is.

Yellows8: Created page with "=Request= {| class="wikitable" border="1" |- ! Index Word ! Description |- | 0 | Header code [0x000F0404] |- | 1 | Output buffer max size |- | 2 | ? |- | 3 | ? |- | 4-5 | MAC a..."

2014-09-21T22:25:36Z

Created page with "=Request= {| class="wikitable" border="1" |- ! Index Word ! Description |- | 0 | Header code [0x000F0404] |- | 1 | Output buffer max size |- | 2 | ? |- | 3 | ? |- | 4-5 | MAC a..."

New page

=Request=
{| class="wikitable" border="1"
|-
! Index Word
! Description
|-
| 0
| Header code [0x000F0404]
|-
| 1
| Output buffer max size
|-
| 2
| ?
|-
| 3
| ?
|-
| 4-5
| MAC address? The 6-bytes located here are normally all 0xFF.
|-
| 6-14
| Unknown, usually zero / uninitialized?
|-
| 15
| [[NWM_Services|wlancommID]]
|-
| 16
| This is the ID also located at offset 0xE in the CTR-generation [[NWM_Services|structure]].
|-
| 17
| Value 0x0
|-
| 18
| Input handle
|-
| 19
| (Size<<4) <nowiki>|</nowiki> 12
|-
| 20
| Output buffer ptr
|}

=Response=
{| class="wikitable" border="1"
|-
! Index Word
! Description
|-
| 0
| Header code
|-
| 1
| Result code
|}

=Description=
The input maxsize is written to outbuf+0. The total amount of data written to the output starting at offset 0x0, is written to outbuf+4. Outbuf+8 is zero when the buffer contains no actual received data, 1 otherwise. Therefore, when the output contains no actual received data the size value at outbuf+4 is set to 0xC.