D-Link DGS-3308FG Product Manual - Page 50

TCP Packet Header

Page 50 highlights

8-port Gigabit Ethernet Switch User's Guide The TCP header is added to the beginning of each packet. This header contains at least 20 octets including the source and destination TCP port numbers. Each packet is given a sequence number that is used to ensure that the packets are received in the correct order. The packets themselves are not numbered, instead, the octets the packet contains is numbered. So if there are 100 octets of data in each packet, the first packet would be numbered 0, the second 100, the third 200, and so on. A checksum is calculated by adding up all the octets in the packet and the result is put in the header. The receiving TCP calculates its own checksum and if the two checksums differ, the packet is dropped. Figure 5-11. TCP Packet Header An acknowledgement is sent to indicate that the packets have been received. This is simply a packet with its acknowledgement number field filled in. The acknowledgement number is the number of octets of data received at the time the acknowledgement packet is sent. If the sender does not receive an acknowledgement within a reasonable amount of time, the data is resent. The window field controls the amount of data in transit at any one time. Each end of a connection indicates how much data it is currently able to receive by putting that number of octets in the window field. As the computer receives data, the number in the window field is decremented and when it reaches zero, the sender must stops transmitting. As the recipient processes data, it increases its window, indicating that it is ready to receive more data. IP TCP sends packets to IP, along with source and destination IP addresses. IP is not concerned with the contents of the packets or with the TCP header. IP routes the packet from the source to the destination. IP adds its own header to the packet to allow intermediate gateways or other network devices to forward the packet. The header contains the source and destination IP addresses, a protocol number, and a checksum. The protocol number allows IP to pass the packet to the appropriate protocol (usually TCP) at the receiving end. The checksum is calculated in same way as the TCP checksum and allows IP to verify that the data was not corrupted in transit. 40

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237

8-port Gigabit Ethernet Switch User’s Guide
40
The TCP header is added to the beginning of each packet. This header contains at least 20 octets including the source and
destination TCP port numbers.
Each packet is given a sequence number that is used to ensure that the packets are received in the correct order. The
packets themselves are not numbered, instead, the octets the packet contains is numbered.
So if there are 100 octets of
data in each packet, the first packet would be numbered 0, the second 100, the third 200, and so on.
A checksum is calculated by adding up all the octets in the packet and the result is put in the header. The receiving TCP
calculates its own checksum and if the two checksums differ, the packet is dropped.
Figure 5-11.
TCP Packet Header
An acknowledgement is sent to indicate that the packets have been received. This is simply a packet with its
acknowledgement number field filled in. The acknowledgement number is the number of octets of data received at the time
the acknowledgement packet is sent.
If the sender does not receive an acknowledgement within a reasonable amount of time, the data is resent.
The window field controls the amount of data in transit at any one time. Each end of
a connection indicates how much data
it is currently able to receive by putting that number of octets in the window field.
As the computer receives data, the number in the window field is decremented and when it reaches zero, the sender must
stops transmitting.
As the recipient processes data, it increases its window, indicating that it is ready to receive more
data.
IP
TCP sends packets to IP, along with source and destination IP addresses. IP is not concerned with the contents of the
packets or with the TCP header.
IP routes the packet from the source to the destination. IP adds its own header to the packet to allow intermediate
gateways or other network devices to forward the packet.
The header contains the source and destination IP addresses, a protocol number, and a checksum.
The protocol number allows IP to pass the packet to the appropriate protocol (usually TCP) at the receiving end.
The checksum is calculated in same way as the TCP checksum and allows IP to verify that the data was not corrupted in
transit.