Jon Hamilton <hamilton@pobox.com> probably said:
> <<< 14:48:44.477257   Addr: 08:00:09:15:1b:bc   Intf: ae0
>         802.2 LLC: DSAP:f8 SSAP:f8 CTRL:300
>         HP Ext:    DXSAP:608 SXSAP:609
>         Boot Request: (Send Server ID)
>                 RetCode:0 SeqNo:0 SessID:ffff Vers:2
>                 Machine Type: HPS300              
>                 File Name (0): <>
> 
> >>> 14:48:44.498213   Addr: 08:00:09:15:1b:bc   Intf: ae0
>         802.2 LLC: DSAP:f8 SSAP:f8 CTRL:300
>         HP Ext:    DXSAP:609 SXSAP:608
>         Boot Reply:
>                 RetCode:0 SeqNo:0 SessID:0 Vers:2
>                 File Name (6): <snoopy>
> 
> over and over indefinitely (for hours until I get tired of it).  Has anyone 
> seen this before?  Have I overlooked something simple?  It's as if the 425 
> is ignoring the response from the server.  The rbootd is the stock version 
> from NetBSD-1.3.3.  This is all taking place on a local thinnet network with 
> very low traffic.  Any help or useful comments would be most welcome.

That looks like the problems I was having with FreeBSD/rbootd.
My experiences and eventually the problem (byte order was broken so the
reply wasn't inteligable to the client) went into the network boot HOWTO.
(Hi, Michael, I'm not dead, just veryvery busy still).

http://www.netbsd.org/Documentation/network/netboot/rbootd/index.html

may help - look at the freebsd section about removing fixes in the rbootd
code. This doesn't explain your problems using a NetBSD server, but it
might give you somewhere to start with the FreeBSD server.

P.

-- 
pir               pir@pir.net      pir@shore.net      pir@leftbank.com