2.2.2 PATH_TEST
The PATH_TEST messages are sent to trigger outbound NAT and firewall mappings.
|
|
|
|
|
|
|
|
|
|
1 |
|
|
|
|
|
|
|
|
|
2 |
|
|
|
|
|
|
|
|
|
3 |
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
bZero |
bCommand |
wMessageID |
|||||||||||||||||||||||||||||
|
ullKey |
|||||||||||||||||||||||||||||||
|
... |
|||||||||||||||||||||||||||||||
bZero (1 byte): An 8-bit identifier used to distinguish this message from DirectPlay 8 Protocol: Reliable messages to the same UDP port. It MUST be set to 0.
bCommand (1 byte): An 8-bit command code identifying this message as a path test message. It MUST be set to 0x05, PATH_TEST_DATA_KIND (Path Test message type).
wMessageID (2 bytes): A 16-bit value used to uniquely identify an individual PATH_TEST message. This can be any value desired by the sender and MUST be ignored by the receiver. It SHOULD change each time a PATH_TEST message is retried.
ullKey (8 bytes): A 64-bit digest value used to validate the PATH_TEST message. This MUST be generated by using the procedure outlined in section 3.1.3 and MUST be validated by the receiver prior to acting on it.