Re: net install downloads bootloader program then complains about RARP request?

Hi Miod,


On 11/03/2012 06:52 PM, Miod Vallat wrote:
>> I've got a Sun Fire V210 platform which I'm trying to install
>> OpenBSD 5.2 sparc64 edition on. As it doesn't have a CDROM drive
>> unlike my Netra T105 I am unable to use the "ok>boot cdrom" method
>> of install.
> [...]
>> So far I have read through all documentation I could find:
> [...]
>> http://www.openbsd.org/cgi-bin/man.cgi?query=diskless&apropos=0&sektion=0&manpath=OpenBSD+Current&arch=sparc64&format=html
> Good. That's the first document I would have pointed to you, if you
> hadn't mentioned it.
>
> [...]
>> The server gets an IP address and downloads the boot file then bombs
>> out after a while?
>>
>> Here is output:
>>
>> {1} ok boot net bsd.mp
> [...]
>>>> OpenBSD BOOT 1.4
>> 100 Mbps full duplex  Link up
>> No response for RARP request
> Quoting from diskless(8) above:
>
> `` In phase 2, the boot program loads a kernel. [...] The procedure used
>     by the boot program is as follows:
>     1. The boot program gets the client IP address using RARP.''
>
> You need to have something on your network answering rarpd requests. On
> most Unix-like systems, there is a rarpd(8) daemon serving that purpose.

Yep I have!

On FreeBSD I'm doing this:

/usr/sbin/rarpd -a -s -v -f

Ethers file is as such:

# cat /etc/ethers
0:3:ba:9c:53:55 sunburst

00:27:0e:1b:a3:86 server

I did a similar thing on my Debian box too which I never got anywhere 
with either?

>> Am I using the wrong boot loader file or is it something to do with
>> my NFS server?
> You seem to have set up the bootloader and the tftp server correctly. As
> for your NFS server, you won't know until you have a reverse arp daemon
> set up, for the boot loader to try and mount the NFS filesystem where
> the bsd.rd kernel is located.
>
> Miod

Hmm... I'm not even getting there I think.

Something's wrong somewhere between:

rarp
tftp
nfs

I think here:

  1.   The boot program gets the client IP address using RARP.
      2.   The boot program gets the client name and server IP address by
           broadcasting an RPC/BOOTPARAMS/WHOAMI request with the client IP
           address.

-->

as I'm getting the IP address downloading the boot program in and then poof!


Regards,

Kaya