RARP - Reverse Address Resolution Protocol

AI Summary

An AI-generated summary of this video lecture.

This lecture introduces the Reverse Address Resolution Protocol (RARP), explaining how a diskless machine that knows only its physical hardware address can discover its logical IP address. The instructor presents a slide defining RARP as the protocol that finds the logical address for a machine knowing only its physical address. The teaching flow moves from conceptual motivation—hosts and routers are assigned unique logical IP addresses independent of physical hardware, and normally the IP is read from a disk configuration file—to the special case where a diskless machine boots from ROM and must obtain its IP via RARP. The second half of the video focuses on a two-part diagram illustrating the request/reply exchange: part (a) shows the RARP request being broadcast on the local network, with a yellow callout stating “My physical address is A4:6E:A5:57:82:36. I am looking for my IP address,” and part (b) shows the RARP reply being sent as a unicast from the server back to the host, with the callout “Your IP address is 141.14.56.21.” The instructor emphasizes that the requesting machine runs a RARP client while the responding machine runs a RARP server, and uses gestures to highlight the host icon and the broadcast/unicast distinction. The lesson is concise, centered on one slide set with a supporting diagram.

Chapters

1. 0:00 – 2:00 00:00-02:00

   The instructor presents a slide titled “RARP” defining the Reverse Address Resolution Protocol as finding the logical address for a machine that knows only its physical address. On-screen bullets explain that each host or router is assigned one or more logical (IP) addresses unique and independent of the physical hardware address, that an IP is usually read from a disk configuration file, but that a diskless machine boots from ROM and can only get its physical address by reading its NIC. The instructor gestures toward the slide to emphasize the relationship between physical and logical addresses, setting up why RARP is needed for diskless booting.

2. 2:00 – 3:28 02:00-03:28

   The slide shifts to the RARP exchange with two bullets stating that a RARP request is broadcast on the local network and that the requesting machine runs a RARP client while the responder runs a RARP server. Diagram “a. RARP request is broadcast” shows a Host sending a Request toward a RARP server, with a yellow note reading “My physical address is A4:6E:A5:57:82:36. I am looking for my IP address.” Diagram “b. RARP reply is unicast” shows a Reply arrow from the server back to the Host, with the note “Your IP address is 141.14.56.21.” The instructor enters, draws an oval around the Host icon, and points to it with a pen, reinforcing the client/server roles and the broadcast request versus unicast reply.

The core concept is that RARP reverses the usual ARP direction: given a known physical (MAC) address, it discovers the corresponding logical IP address. The lecture first motivates this by contrasting normal disk-based IP configuration with a diskless machine that boots from ROM and can only read its NIC’s physical address. It then demonstrates the protocol operation through a two-part diagram: the client broadcasts a request containing its physical address, and a RARP server on the local network replies with the mapped IP address using unicast. Key takeaways for revision are: (1) RARP maps physical to logical address; (2) the request is broadcast, while the reply is unicast; (3) the requester runs a RARP client and the responder runs a RARP server. The concrete example uses physical address A4:6E:A5:57:82:36 and IP 141.14.56.21, which students should recall as the canonical illustration of the exchange.