On Thu, May 09, 2002 at 04:34:23PM -0400, Roland Dowdeswell wrote:
> 
> On 1020972443 seconds since the Beginning of the UNIX epoch
> Matt wrote:
> >
> 
> >In all cases, I get "84 FAIL" and back to the ">>>" prompt. With the
> >netboot attempt, I get more messages:
> >
> >AUDIT_BOOT_STARTS ...
> >AUDIT_BOOT_REQ
> >Host server IP address is 192.168.1.1
> >AUDIT_BSERVER_FOUND
> >
> >...and on the BOOTP server, (Linux + ISC dhcpd), I can see the IP
> >request successfully, but I never see the TFTP session start.
> 
> What's your /etc/dhcpd.conf look like?

The necessary bits, (this dhcpd is under regular use), which I've
specifically added for this box:

allow bootp;
always-reply-rfc1048 on;

group {
	use-host-decl-names on;

	...

	host sandpiper {
		hardware ethernet 11:22:33:44:55:66;
		fixed-address 192.168.1.6;
		filename "boot.netbsd.alpha";
		next-server 192.168.1.1;
	}
}

The next-server line I added to see if that made any difference, it's
the IP of that dhcpd/tftp box.

In syslog I get BOOTREQUEST's from the Alpha, and the correct BOOTREPLY
goes out to the Alpha.

> Have you tcpdump(8)ed the
> traffic between the two boxes to see what is going on?

This is what I captured from starting the boot to it failing:

22:27:10.083622 0.0.0.0.bootpc > 255.255.255.255.bootps:  [no cksum] xid:0x5efa0000 [|bootp] (ttl 30, id 2447, len 328)
22:27:10.085314 snap 8:0:2b:60:2 8:0:2b:bb:c7:aa > ab:0:0:2:0:0 sap aa ui/C
>>> Unknown IPX Data: (35 bytes)
[000] 00 01 00 03 04 00 00 02  00 02 41 00 07 00 06 08  ........  ..A.....
[010] 00 2B BB C7 AA 64 00 01  AA 90 01 01 01 91 01 02  .+...d..  ........
[020] EE 05 00                                          ...
 len=35
22:27:10.085932 192.168.1.1.bootps > 192.168.1.6.bootpc: xid:0x5 efa0000 Y:192.168.1.6 S:192.168.1.1 [|bootp] [tos 0x10] (ttl 16, id 0, len 328)
22:27:10.086419 8:0:2b:bb:c7:aa ab:0:0:2:0:0 moprc 60:
                         2500 0700 0000 0100 0304 0000 0200 0241
                         0007 0006 0800 2bbb c7aa 6400 01aa 9001
                         0101 9101 02ee 0500 0000 0000 0000
22:27:10.087383 arp who-has 0.0.0.0 tell 192.168.1.6
22:27:17.374087 arp who-has 0.0.0.0 tell 192.168.1.6
22:27:25.197177 arp who-has 0.0.0.0 tell 192.168.1.6
22:27:33.099633 arp who-has 192.168.1.1 (11:0:0:0:0:0) tell 192.168.1.6
22:27:33.099777 arp reply 192.168.1.1 is-at 0:10:4b:93:b:40
22:27:33.101408 192.168.1.6.64095 > 192.168.1.1.tftp: [no cksum] 26 tftp-#0 [tos 0x1]  (ttl 30, id 2447, len 54, bad cksum e414!)

...so I can see that an attempt is at least made from the Alpha. I've
tested a TFTP get from another box on the same wire and that works okay.

> Have you had a look at:
> 
> http://www.netbsd.org/Documentation/network/netboot/intro.alpha.html

Yes, the first thing I see is the SRM point, I haven't yet worked out
how to find my current SRM version, but I doubt it's the latest. I
certainly don't have EWA0_PROTOCOLS, hence using ez0 as the boot device.

(Incidentally, I found s/readmes/archive/ was necessary for the firmware
URL to work. I'll try setting a MOP daemon up to get that sorted.)

Cheers

Matt

PS. I've managed to get the Alpha booted using the install image dd'd to
a spare external 500MB disk, but I'd still like to get netbooting
working as I'm probably going to have to use the same setup to get a
VAXstation/NetBSD install working.
-- 
"Phased plasma rifle in a forty-watt range?"
"Hey, just what you see, pal"