|
Figure 21.1 |
An IP datagram encapsulated in a hardware frame. The entire datagram resides in the frame data area. In practice, the frame format used with some technologies includes a frame trailer as well as a frame header. |
|
|
Figure 21.2 |
An IP datagram as it appears at each step during a trip across an internet. Whenever it travels across a physical network, the datagram is encapsulated in a frame appropriate to the network. |
|
|
Figure 21.3 |
An example of a router that connects two networks with different MTU values. A frame that travels across network 1 can contain 1500 octets of data, while a frame that travels across network 2 can contain at most 1000 octets of data. |
|
|
Figure 21.4 |
An IP datagram divided into three fragments. Each fragment carries some data from the original datagram, and has an IP header similar to the original datagram. |
|
|
Figure 21.5 |
An example internet in which hosts can generate datagrams that require fragmentation. Once a datagram has been fragmented, the fragments are forwarded to the final destination, which reassembles them. |
|
Animation 17_1 |
In an internet, the protocol software on the source computer constructs an IP datagram and transmits it to a router using a hardware frame header by encapsulating the datagram in a hardware frame |
|
Data file 1 |
Trace of all IP traffic on Ethernet segment |
