Packet:SOEProtocol - Revision history

Snow: /* Packet Type -- '''00 03''' */

2006-12-16T07:50:54Z

‎Packet Type -- '''00 03'''

Snow: /* Packet Type --> 00 01 */

2006-12-16T07:48:12Z

‎Packet Type --> 00 01

Snow at 07:46, 16 December 2006

2006-12-16T07:46:52Z

Snow at 07:39, 16 December 2006

2006-12-16T07:39:14Z

Snow at 07:35, 16 December 2006

2006-12-16T07:35:11Z

Snow at 22:40, 14 December 2006

2006-12-14T22:40:26Z

67.113.166.246 at 18:48, 14 December 2006

2006-12-14T18:48:52Z

Snow at 00:55, 9 December 2006

2006-12-09T00:55:14Z

Snow at 00:49, 9 December 2006

2006-12-09T00:49:57Z

Snow at 00:48, 9 December 2006

2006-12-09T00:48:48Z

@@ Line 135: / Line 135: @@
 In the case where the size exceeds 0xFF (255) bytes, the following sytem is used for the "Data Size" component.
-The first byte will be 0xFF. The next byte will be 0x01. The following byte will be how much to add to 255.
+The first byte will be 0xFF. The next byte will be 0x01. The following byte will be how much to add to 255. Because no packet can exceed 496 bytes, The 3rd bye will never exceed 0xFF. We believe the 0x01 is the amount of following bytes to add to 255, but that cannot be determined.
- Because no packet can exceed 496 bytes, The 3rd bye will never exceed 0xFF. We believe the 0x01 is the amount
+<pre>
 of following bytes to add to 255, but that cannot be determined.
 (0XFF 0X01 0X01) = 255 + 1 = 256 bytes
 (0xFF 0X01 0X0A) = 255 + 10 = 265 bytes
 (0xFF 0x01 0x25) = 255 + 37 = 292 bytes
-*NOTE: Because 255 may be done in a few ways, the following way is how we have seen it.
+* '''NOTE''': ''Because 255 may be done in a few ways, the following way is how we have seen it. (0xFF 0x00 0xFF) or 255 + 0 (do not add the following byte) = 255.''
 (0xFF 0x00 0xFF) or 255 + 0 (do not add the following byte) = 255.
 ==Packet Type -- '''00 04'''==

@@ Line 56: / Line 56: @@
 The following data is of packet breakdowns and explainations on each type. See the article "Packet Breakdown Format" for information on the specific used for documentation.
-==Packet Type --> 00 01==
+==Packet Type -- '''00 01'''==
 {{InfoboxPacketDetail|Packet Type 00 01|
@@ Line 79: / Line 79: @@
 Note* This opcode DOES NOT have a footer.
+==Packet Type -- '''00 02'''==
 {{InfoboxPacketDetail|Packet Type 00 02  -  Session Response(Server -> Client)|
@@ Line 102: / Line 102: @@
+==Packet Type -- '''00 03'''==
-−
 {{InfoboxPacketDetail|Packet Type 00 03  -  Multiple SOE Protocols(Various)|
@@ Line 146: / Line 145: @@
 (0xFF 0x00 0xFF) or 255 + 0 (do not add the following byte) = 255.
+==Packet Type -- '''00 04'''==
-−
 {{InfoboxPacketDetail|Packet Type 00 05  -  Disconnect(VARIOUS)|

← Older revision		Revision as of 07:46, 16 December 2006
Line 55:		Line 55:

	The following data is of packet breakdowns and explainations on each type. See the article "Packet Breakdown Format" for information on the specific used for documentation.		The following data is of packet breakdowns and explainations on each type. See the article "Packet Breakdown Format" for information on the specific used for documentation.
		+
		+	==Packet Type --> 00 01==

	{{InfoboxPacketDetail\|Packet Type 00 01\|		{{InfoboxPacketDetail\|Packet Type 00 01\|

@@ Line 148: / Line 148: @@
 {{InfoboxPacketDetail|Packet Type 00 05  -  Disconnect(VARIOUS)|
 <pre>
 SOE Opcode	- Net Byte SHORT
@@ Line 154: / Line 153: @@
 Reason ID	- Net Byte SHORT
 </pre>
 Connection ID is the ID number assigned during the session request. Each client sends its own Connection ID.
 Reason ID is an ID number that corresponds for a reason for the disconnection.
@@ Line 168: / Line 167: @@
-06   -  Keep Alive(VARIOUS)
+{{InfoboxPacketDetail|00 06   -  Keep Alive(VARIOUS)|
 SOE Opcode	- Net Byte SHORT
+</pre>
 This packet is simply a keep alive to tell the other side that is still connected, but idle.
@@ Line 176: / Line 177: @@
+{{InfoboxPacketDetail|00 07  -  Client Network Status Update|
-07  -  Client Network Status Update
+<pre>
 SOE Opcode	- Net Byte SHORT
 Data..
 These packets consist of various data and network statistics. Because we do not care about network statistics,
@@ Line 187: / Line 190: @@
+{{InfoboxPacketDetail|00 08  -  Server Network Status Update|
+<pre>
 08  -  Server Network Status Update
 SOE Opcode	- Net Byte SHORT
 Data..
 This packet is supposed to contain the Servers network statistics, however we felt it was a waste of time to reverse
@@ Line 201: / Line 206: @@
+{{InfoboxPacketDetail|00 09  -  Channel 0 Data|
+<pre>
 09  -  Channel 0 Data
 SOE Opcode	- Net Byte SHORT
 Sequence #	- Net Byte SHORT
 SWG PACKET..
 Sequence # is a sequence number applied to every data packet. It increments in order for each packet and is used to help determine
@@ Line 225: / Line 231: @@
+{{InfoboxPacketDetail|00 0D  -  Fragmented Data Packet|
-0D  -  Fragmented Data Packet
+<pre>
 SOE Opcode	- Net Byte SHORT
 Sequence #	- Net Byte SHORT
 *FragmentSize	- Net Byte INT
 SWG Packet...
 Sequence # is the same type of sequence number described in the "00 09  -  Channel 0 Data" section. All the same rules apply.
@@ Line 238: / Line 246: @@
 Next is just the piece data of the large SWG Packet. Fragments are made when the total UNCOMPRESSED packet
 exceeds the packet buffer size, which is 496 bytes.
@@ Line 270: / Line 277: @@
 An out of order packet will be sent for all 3 of the out of order sequences.

@@ Line 241: / Line 241: @@
+{{InfoboxPacketDetail|Packet Type 00 11  -  Out of Order Packet|
-11  -  Out of Order Packet
+<pre>
 SOE Opcode	- Net Byte SHORT
 Sequence #	- Net Byte SHORT
+</pre>
 Sequence # is the sequence number of the out of order packet recieved.
@@ Line 274: / Line 275: @@
+{{InfoboxPacketDetail|Packet Type 00 15  -  Acknowledge|
-15  -  Acknowledge
+<pre>
 SOE Opcode	- Net Byte SHORT
 Sequence #	- Net Byte SHORT
 Sequence # is the sequence number of the packet to acknowledge to the sender that it was recieved correctly.

@@ Line 11: / Line 11: @@
 01		Session Request				(SOE_SESSION_REQUEST)
 02		Session Response			(SOE_SESSION_REPLY)
-03		Multiple SOE Protocols			(SOE_MULTI_PKT)
+03		Multiple SOE Protocols			(SOE_MULTI_SOE)
 04		Not Used				(SOE_NOT_USED)
 05		Disconnect				(SOE_DISCONNECT)
@@ Line 38: / Line 38: @@
 18		Channel 3 - Acknowledge Packet		(SOE_ACK_D)
-19		*Channel 0 - Unknown(Reserved)
+19		Channel 0 - Multi SWG Packets		(SOE_MULTI_SWG_A)
-1A		*Channel 1 - Unknown(Reserved)
+1A		Channel 1 - Multi SWG Packets		(SOE_MULTI_SWG_B)
-1B		*Channel 2 - Unknown(Reserved)
+1B		Channel 2 - Multi SWG Packets		(SOE_MULTI_SWG_C)
-1C		*Channel 3 - Unknown(Reserved)
+1C		Channel 3 - Multi SWG Packets		(SOE_MULTI_SWG_D)
-1D		**Serious Error Acknowledge		(SOE_FATAL_ERR)
+1D		*Serious Error Acknowledge		(SOE_FATAL_ERR)
-1E		**Serious Error Reply			(SOE_FATAL_ERR_REP)
+1E		*Serious Error Reply			(SOE_FATAL_ERR_REP)
 </pre>
 }}
 * Note: These functions are seen on very malformed packets. Very rare occurance and the client will usually disconnect. It's inclusion in the documentation is for completion ONLY. SWGEmu will disconnect automatically when reciving a Error Acknowledge, and it will NOT send any, rather just disconnect itself.
@@ Line 99: / Line 97: @@
   So far the client has not sent anything large enough to fill this, or be fragmented. This size is equal to 496 bytes.
-* This opcode DOES NOT have a footer.
+Note* This opcode DOES NOT have a footer.
@@ Line 145: / Line 143: @@
 *NOTE: Because 255 may be done in a few ways, the following way is how we have seen it.
 (0xFF 0x00 0xFF) or 255 + 0 (do not add the following byte) = 255.
@@ Line 184: / Line 179: @@
 we will ignore these. To ignore these we send a special malformed Server Network Status Update.
-Note: This packet is ALWAYS compressed.
+Note: This packet is usually compressed but is optional.
@@ Line 198: / Line 193: @@
 and tosses out the packet as malformed. Because it recieved the packet it continues on without erroring.
-Note: This packet is ALWAYS compressed.
+Note: This packet is usually compressed but is optional.

@@ Line 1: / Line 1: @@
-SOE's Protocol is a systematic way to enhance the UDP protocol to make it more reliable, and also save bandwidth by merging and
+SOE's Protocol is a systematic way to enhance the UDP protocol to make it more reliable, and also save bandwidth by merging and grouping packets. It can be combined in various ways, or not be used at all.
 grouping packets. It can be combined in various ways, or not be used at all.
-The format of the SOE Protocol varies depending on what type of operation it is.
+The format of the SOE Protocol varies depending on what type of operation it is. SOE Protocol can function as a stand alone packet, or as a Header to SWG Packets. What is true about all of the SOE Protocol is that the beginning contains 2 bytes known as the SOE Opcode. Majority also contain a footer. Assume all packets have footers unless otherwise mentioned. The table of opcodes are as follows:
 SOE Protocol can function as a stand alone packet, or as a Header to SWG Packets.
 What is true about all of the SOE Protocol is that the beginning contains 2 bytes known as the SOE Opcode.
 Majority also contain a footer. Assume all packets have footers unless otherwise mentioned. The table of opcodes are as follows:
 Note- An SOE Opcode is stored as an unsigned short (uint16), and is in net byte order.

@@ Line 52: / Line 52: @@
 }}
-*Note: These sets of opcodes are reserved for some function not used by SWG. Purpose is unknown.
+* Note: These sets of opcodes are reserved for some function not used by SWG. Purpose is unknown.
-**Note: These functions are seen on very malformed packets. Very rare occurance and the client will usually disconnect.
+* Note: These functions are seen on very malformed packets. Very rare occurance and the client will usually disconnect.
 It's inclusion in the documentation is for completion ONLY. SWGEmu will disconnect automatically when reciving
 a Error Acknowledge, and it will NOT send any, rather just disconnect itself.
@@ Line 66: / Line 66: @@
 See the article "Packet Breakdown Format" for information on the specific used for documentation.
+{{InfoboxPacketDetail|Packet Type 00 01|
+<pre>
-−
-−
 01  -  Session Request (Client -> Server)
 SOE Opcode	- Net Byte SHORT
@@ Line 75: / Line 73: @@
 Connection ID	- Net Byte INT
 ClientUDPSize	- Net Byte INT
+</pre>
 The SOE Opcode is just the opcode number to identify the packet.