D-Link 3250TG Product Manual - Page 38

Packet Headers

Get D-Link 3250TG - Switch PDF manuals and user guides
UPC - 790069250682
View all D-Link 3250TG manuals
Add to My Manuals
Save this manual to your list of manuals

Page 38 highlights

D-Link DES-3250TG Standalone Layer 2 Switch Because these functions are required by a large number of applications, they are grouped into a single protocol, rather than being the part of the specifications for just sending e-mail. TCP is then a library of routines that application software can use when reliable network communications are required. IP is also a library of routines, but with a more general set of functions. IP handles the routing of packets from the source to the destination. This may require the packets to traverse many different networks. IP can route packets through the necessary gateways and provides the functions required for any user on one network to communicate with any user on another connected network. The communication interface between TCP and IP is relatively simple. When IP received a packet, it does not know how this packet is related to others it has sent (or received) or even which connection the packet is part of. IP only knows the address of the source and the destination of the packet, and it makes its best effort to deliver the packet to its destination. The information required for IP to do its job is contained in a series of octets added to the beginning of the packet called headers. A header contains a few octets of data added to the packet by the protocol in order to keep track of it. Other protocols on other network devices can add and extract their own headers to and from packets as they cross networks. This is analogous to putting data into an envelope and sending the envelope to a higher-level protocol, and having the higher-level protocol put the entire envelope into its own, larger envelope. This process is referred to as encapsulation. Many levels of encapsulation are required for a packet to cross the Internet. Packet Headers TCP Most data transmissions are much longer that a single packet. The data must then be divided up among a series of packets. These packets must be transmitted, received and then reassembled into the original data. TCP handles these functions. TCP must know how large a packet the network can process. To do this, the TCP protocols at each end of a connection state how large a packet they can handle and the smaller of the two is selected. The TCP header contains at least 20 octets. The source and destination TCP port numbers are the most important fields. These specify the connection between two TCP protocols on two network devices. The header also contains a sequence number that is used to ensure the packets are received in the correct order. The packets are not numbered, but rather the octets the packets contain are. If there are 100 octets of data in each packet, the first packet is numbered 0, the second 100, the third 200, etc. To insure that the data in a packet is received uncorrupted, TCP adds the binary value of all the octets in the packet and writes the sum in the checksum field. The receiving TCP recalculates the checksum and if the numbers are different, the packet is dropped. 30

  • 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
D-Link DES-3250TG Standalone Layer 2 Switch
Because these functions are required by a large number of applications, they are grouped into a single
protocol, rather than being the part of the specifications for just sending e-mail.
TCP is then a library of
routines that application software can use when reliable network communications are required.
IP is also a library of routines, but with a more general set of functions. IP handles the routing of
packets from the source to the destination. This may require the packets to traverse many different
networks. IP can route packets through the necessary gateways and provides the functions required for
any user on one network to communicate with any user on another connected network.
The communication interface between TCP and IP is relatively simple. When IP received a packet, it does
not know how this packet is related to others it has sent (or received) or even which connection the
packet is part of. IP only knows the address of the source and the destination of the packet, and it
makes its best effort to deliver the packet to its destination.
The information required for IP to do its job is contained in a series of octets added to the beginning of
the packet called headers. A header contains a few octets of data added to the packet by the protocol in
order to keep track of it.
Other protocols on other network devices can add and extract their own headers to and from packets as
they cross networks.
This is analogous to putting data into an envelope and sending the envelope to a
higher-level protocol, and having the higher-level protocol put the entire envelope into its own, larger
envelope. This process is referred to as encapsulation.
Many levels of encapsulation are required for a packet to cross the Internet.
Packet Headers
TCP
Most data transmissions are much longer that a single packet.
The data must then be divided up
among a series of packets.
These packets must be transmitted, received and then reassembled into the
original data. TCP handles these functions.
TCP must know how large a packet the network can process.
To do this, the TCP protocols at each end
of a connection state how large a packet they can handle and the smaller of the two is selected.
The TCP header contains at least 20 octets. The source and destination TCP port numbers are the most
important fields.
These specify the connection between two TCP protocols on two network devices.
The header also contains a sequence number that is used to ensure the packets are received in the
correct order. The packets are not numbered, but rather the octets the packets contain are. If there are
100 octets of data in each packet, the first packet is numbered 0, the second 100, the third 200, etc.
To insure that the data in a packet is received uncorrupted, TCP adds the binary value of all the octets
in the packet and writes the sum in the checksum field. The receiving TCP recalculates the checksum
and if the numbers are different, the packet is dropped.
30