Solaris 9 box as bootp/tftpd server to install debian in SS1+

[Mauricio]

Easy question: I want to set my ss20 (solaris9) box so I can use
it to netinstall debian linux in my SS1+. So, I

o created a /etc/ethers file

# cat /etc/ethers
8:0:20:c0:ff:ee katrina
#

o added an entry to my /etc/hosts file

10.0.0.17 katrina.kushana.com katrina # SS1+ running Debian Linux

o manually started /usr/sbin/in.rarpd (as in /usr/sbin/in.rarpd -a -d),
which results in the following messages:

# /usr/sbin/in.rarpd -a -d
/usr/sbin/in.rarpd:[1] device le0 ethernetaddress 8:0:20:71:a0:87
/usr/sbin/in.rarpd:[1] device le0 address 10.0.0.13
/usr/sbin/in.rarpd:[1] device le0 subnet mask 255.255.255.0
/usr/sbin/in.rarpd:[3] starting rarp service on device le0 address
8:0:20:71:a0:87
/usr/sbin/in.rarpd:[3] RARP_REQUEST for 8:0:20:c0:ff:ee
/usr/sbin/in.rarpd:[3] trying physical netnum 10.0.0.0 mask ffffff00
/usr/sbin/in.rarpd:[3] good lookup, maps to 10.0.0.17

which, I would guess, indicates that it has successfully done the rarpd
part. So, I then went on to setup tftp so I could get the bloody
tftpboot.img file:

o Placed the tftpboot file in a known location,

-rw-r--r-- 1 root other 3161568 May 18 2002
/export/netboot/tftpboot.img

modified the tftp entry in /etc/inetd.conf to reflect that

tftp dgram udp6 wait root /usr/sbin/in.tftpd in.tftpd -s /export/netboot

(I am not horrible concerned about security since we are behind a firewall
and all the relevant ports are disabled in my router)

o Restarted inetd

# ps -e | grep inetd
182 ? 0:01 inetd
# kill -HUP 182

From the following messages int he SS1+, it seems not to be able to get
the tftpboot.img file:

ok boot net
Booting from: le(0,0,0)
Got error packet: Error Code 2 Message: Access violationreceive failed
Boot load failed
ok

What am I missing here?

--
Mauricio raubvogel-yahoo-com
(if you need to email me, use this address =)

[Darren Dunham]

Mauricio <uce@ftc.gov> wrote:

> Easy question: I want to set my ss20 (solaris9) box so I can use
> it to netinstall debian linux in my SS1+. So, I

> o created a /etc/ethers file

> # cat /etc/ethers
> 8:0:20:c0:ff:ee katrina

> o added an entry to my /etc/hosts file
> 10.0.0.17 katrina.kushana.com katrina # SS1+ running Debian Linux

> o manually started /usr/sbin/in.rarpd (as in /usr/sbin/in.rarpd -a -d),
> which results in the following messages:

> # /usr/sbin/in.rarpd -a -d
> /usr/sbin/in.rarpd:[1] device le0 ethernetaddress 8:0:20:71:a0:87
> /usr/sbin/in.rarpd:[1] device le0 address 10.0.0.13
> /usr/sbin/in.rarpd:[1] device le0 subnet mask 255.255.255.0
> /usr/sbin/in.rarpd:[3] starting rarp service on device le0 address
> 8:0:20:71:a0:87
> /usr/sbin/in.rarpd:[3] RARP_REQUEST for 8:0:20:c0:ff:ee
> /usr/sbin/in.rarpd:[3] trying physical netnum 10.0.0.0 mask ffffff00
> /usr/sbin/in.rarpd:[3] good lookup, maps to 10.0.0.17

> which, I would guess, indicates that it has successfully done the rarpd
> part. So, I then went on to setup tftp so I could get the bloody
> tftpboot.img file:

> o Placed the tftpboot file in a known location,

> -rw-r--r-- 1 root other 3161568 May 18 2002
> /export/netboot/tftpboot.img

You'll find that the unit will attempt to tftp a file with the name of
the client IP address converted to hex (capital letters), or the same
with the name of the architecture appended.

I believe the 1+ is a sun4c, so the likely files it will try to tftp
are..

0A000011
0A000011.SUN4C

You can make a symlink from your image to those files.

Running an ethernet sniffer (snoop) should show the exact requests made
by the client.

> ok boot net
> Booting from: le(0,0,0)
> Got error packet: Error Code 2 Message: Access violationreceive failed
> Boot load failed
> ok

> What am I missing here?

Seems strange. When the tftp file is messed up, I generally get nothing
from the client (it appears to hang). However, I would also expect that
'access violation' is an acceptable error that could also mean 'file not
found'.

--
Darren Dunham [email]ddunham@taos.com[/email]
Unix System Administrator Taos - The SysAdmin Company
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >