|
Figure 19.1 |
A simple internet with routers R1 and R2 connecting three physical networks; each network has two host computers attached. A computer can only resolve the address of a computer attached to the same physical network. |
|
|
Figure 19.2 |
An example address binding table. Each entry in the table contains a protocol address and the equivalent hardware address. |
|
|
Figure 19.3 |
An example of direct lookup for a class C network. The host portion of an address is used as an array index. |
|
|
Figure 19.4 |
Comparison of address resolution using a table lookup (T), closed-form computation (C), and dynamic message exchange (D). |
|
|
Figure 19.5 |
An ARP message exchange. (a) Computer W begins to broadcast an ARP request that contains computer Y's IP address. (b) All computers receive the request, and (c) computer Y sends a response directly to W. |
|
|
Figure 19.6 |
The format for an ARP message when used to bind Internet protocol addresses to Ethernet hardware addresses. |
|
|
Figure 19.7 |
Illustration of an ARP message encapsulated in an Ethernet frame. The entire ARP message travels in the data area of the frame; the network hardware neither interprets nor modifies contents of the ARP message. |
|
|
Figure 19.8 |
Illustration of the type field in an Ethernet header used to specify the frame contents. A value of 0x806 informs the receiver that the frame contains an ARP message. |
|
|
Figure 19.9 |
Layered protocol software in a computer and the conceptual boundary between the network interface layer and higher layers. Software above the boundary uses protocol addresses; software below the boundary translates each protocol address to an equivalent hardware address. |
|
Animation 15_1 |
Binding protocol addresses with ARP |
|
Data file 1 |
Trace of all IP traffic on Ethernet segment. Contains approximately 87,000 packets and 6.5Mb. Trace includes packet headers only. |
|
|
Data file 2 |
Anonymous FTP session with dir, get and put. Contains approximately 930Kbytes and 2300 packets. |
