For those following my saga of trying to get the Sun4 architecture to
remote boot..

Got to playing with my boot params and tcpdump again today... :o)
Anywho, latest news is the 1.4.2 GENERIC kernel is making more
progress.. Still using the 1.4.1 2nd stage loader. I get the following
on the TCP dump:

>>[Log, after kernel downloaded.]<<
rarp reply 8:0:20:8:af:24 at sparcy.neonshadow.net
arp who-has sparcy.neonshadow.net tell sparcy.neonshadow.net
sparcy.neonshadow.net.1023 > 10.255.255.255.sunrpc: udp 96
sparcy.neonshadow.net.1023 > 10.255.255.255.sunrpc: udp 96
sparcy.neonshadow.net.1023 > 10.255.255.255.sunrpc: udp 96
sparcy.neonshadow.net.1023 > 10.255.255.255.sunrpc: udp 96
sparcy.neonshadow.net.1023 > 10.255.255.255.sunrpc: udp 96
sparcy.neonshadow.net.1023 > 10.255.255.255.sunrpc: udp 96
sparcy.neonshadow.net.1023 > 10.255.255.255.sunrpc: udp 96
sparcy.neonshadow.net.1023 > 10.255.255.255.sunrpc: udp 96
>>[End of log, boot process timed out.]<<

I'm using the 10.1.2.0/24 subnet/mask. Tcpdump was running on
darkspacei, the internal network nic for my linux box, which is hosting
the remote boot.

sparcy.neonshadow.net           => 10.1.2.139
darkspacei.neonshadow.net       => 10.1.2.254

Is it me or is the kernel determining wrong netmask?

>>[/etc/bootparams]<<
sparcy root=10.1.2.254:/export/client/root \
        gateway=10.1.2.254:0xffffff00
>>[EOF]<<

Shouldn't the bootparam whoami be getting the proper netmask for the
kernel?

The complete tcpdump ('bout 450k) is available for those that feel an
urge to look through it... :o/

-Gerald

-- 
/*******************************************************************
* glassman1@neonshadow.net ->  Lord  Phear  <- ICQ UIN 8838302     *
*    ACP II: Reincarnation ->  telnet to neonshadow.net            *
*******************************************************************/