Hi all!

I try to install the current snapshot on my Indigo2 (IP22) according to
http://raisdorf.net/files//NetBSD/faq.html

My install server is a Linux 2.4.16 (i386) and has the ipaddr
192.168.2.3. The Indigo is called teal and has 192.168.2.253. 
I've setup the nfs-root directory in /home/indy/root (opposing to 
"/home/indy" as suggested in the FAQ) and made all devices. The entry 
"/home/indy/root -maproot=0() 192.168.2.253()" was added to 
/etc/exports.

I continued at "How to bootstrap NetBSD/sgimips" and ran the dhcp server
with following config:

ddns-update-style none;
subnet 192.168.2.0 netmask 255.255.255.0 {
        host teal {
                hardware ethernet 08:00:69:08:24:72;
                fixed-address 192.168.2.253;
                option host-name "teal";
                server-name="192.168.2.3";
                option root-path "/home/indy/root";
        }
}
 
After restarting dhcpd I enabled the line "tftp dgram udp wait root 
/usr/sbin/in.tftpd in.tftpd -s /tftpboot" in /etc/inetd.conf. I copied
the netbsd.ip22 kernel to /tftpboot and reloaded inetd. 

Then I verified that the indigo has still the correct ipaddr in the
PROM and tried to boot, but tftp failed :-(
  
>> printenv netaddr
netaddr=192.168.2.253
>> bootp():/netbsd.ip22
Setting $netaddr to 192.168.2.253 (from server 192.168.2.3)
Unable to execute bootp():/netbsd.ip22

After reading the FAQ carefully I noticed the comment about the default
tftp settings and set "net.ipv4.ip_local_port_range = 2014 32768".

Using ethereal I discovered that the server sends repeating packets. All
those packets from the server carry identical data, looks like a part of
the kernel file (surprise, surprise! :-) ). Some of the files are
displayed as TFTP packets, some are displayed as UDP packets btw.

The indigo sends sometimes a TFTP packet back. Ethereal displays the
packet headers but complains about "malformed frame". 
Here is the hexdump:
0000  00 10 dc 52 55 30 08 00  69 08 24 72 08 00 45 00   ..RU0.. i.$r..E.
0010  00 35 00 52 00 00 ff 11  35 15 c0 a8 02 fd c0 a8   .5.R... 5..
0020  02 03 1a 63 00 45 00 21  00 00 00 01 2f 6e 65 74   ...c.E.! ..../net
0030  62 73 64 2e 69 70 32 32  00 6f 63 74 65 74 00 7f   bsd.ip22 .octet..
0040  f5 60 00                                           `.              

Well some special chars are lost, but the malformed frame must be the
last four bytes (7f f5 60 00).

What does this error message mean? What am I doing wrong? And how can I
change this?

kind regards,
Andreas