<H2>RARP</h2>
Printable View
<H2>RARP</h2>
Reverse Address Resolution Protocol: In June 1984, this address translation protocol was developed at Stanford by Finlayson, Mann, Mogul, and Theimer in order to establish a standard method for resolving a network host's protocol address on boot, given that the hardware address mapping is known. This is necessary for a network host device, such as a diskless workstation, printer, or X-terminal, to communicate using advanced protocols like IP. In order to work, RARP requires a server host containing a database of hardware address mappings. ARP, a protocol developed by Plummer, solves the opposite problem; it resolves a host's hardware address providing that it has a protocol address.
Consult rfc903 for more information. http://www.augustknights.com/ubb/smile.gif
------------------
[AK]Palooka
August Knights Administrator
Xearic: 48 Necromancer
Burwell: 40 Cleric
Alright. If you want to look up the answers the questions are going to be a bit more involved.
1. Give me an example of this 'hardware address' mentioned in your answer.
2. What are other terms used to describe a 'hardware address'? Identify two(2) other names is it sometimes called.
3. Define how it differs from a protocol address.
4. Identify, compare and contrast which layer(s) of the OSI model hardware addresses and protocol addressies are associated with.
[ Given your workstation at home and a webserver (somewhere) ]
5. In a step by step fashion, give an example in detail of what a RARP process looks like. Take us through the process regarding this resolution so those following along at home may further understand the concepts involved.
Regards,
The Wraith
ROFL...
I knew what it was...that one was easy...
[AK]Zorro
Chief Operations Officer
<a href="http://www.augustknights.com" target="_blank">AugustKnights.com</a> WizOp