94362550   
   XPost: comp.arch.embedded, sci.electronics.design   
   From: gah@ugcs.caltech.edu   
      
   In comp.protocols.tcp-ip Didi  wrote:   
   (snip)   
      
   > In an attempt to solve it I spent 10 minutes adding RARP reply   
   > to our device Ethernet related stuff - so it would reply to an ARP   
   > inquiry #3 by sending its IP address (it only has one); and then spent   
   > perhaps 3 hours googling, moogling, you name it, searching for some   
   > piece of code to do that at the wintel side. Even rebooted the wintel   
   > laptop to ubuntu to try it out from there (thought arp -r or something   
   > would just work), oh no. No way. Spent perhaps half an hour of   
   > moogling for linux rarp, same thing.   
      
   It seems unlikely that RARP will be useful.  RARP is from the   
   days before BOOTP, from which DHCP was derived.  RARP was,   
   at least, used for diskless Sun systems to find their IP address.   
      
   The Sun boot ROM would use RARP to find its IP address, then   
   tftp to load the rest of the boot code.  The first thing the   
   second level boot code does is RARP to find its address.   
   Then IP based bootparamd to find the rest of the data it needed   
   to boot, such as the address of its NFS server, and name of   
   the root file system.   
      
   These days, everyone just used DHCP to get an IP address,   
   either dynamically or statically assigned.   
      
   -- glen   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)