I have an AS1200, and wish to be able to boot from network. After

> P00>>>boot ewa0
> (boot ewa0.0.0.3.1 -flags 1)
>
> Trying MOP boot.
> ........
> Trying BOOTP boot.
>
> Broadcasting BOOTP Request...
> ..file open failed for bootp/ewa0.0.0.3.1
> bootstrap failure
>
> Retrying, type ^C to abort...
>
> (boot ewa0.0.0.3.1 -flags 1)


I tried to search how to implement a server; i concluded i had the
choice between MOP and BOOTP. Since Google is really not verbose at all
about MOP (I only found one daemon, and no documentation about
configuration; the one which has docs only runs on BSD, have not been
ported to Linux), I am gone for BOOTP.

At the moment, I have a working PXE server; and take it as a start. Note
that this server only works for clients having PXE 2.0 cards; cards
using PXE 1.0 do not like it - no clue why. This means, I have a working
DHCP and TFTP servers. DHCP is ISC dhcp3-server; TFTP is tftpd-hpa, all
on Debian x86 testing.

Here is the relevant DHCP section:
> host AlphaBeta {
> hardware ethernet 00:00:f8:10:48:41;
> fixed-address 192.168.0.12;
> server-name "fly";
> next-server 192.168.0.205;
> filename "/home/tftp/alpha/vmlinuz-2.6.18-6-alpha-smp";
> }


(path are absolute PATH in regard to server, other wise, it does not
work at all for PXE or CLI tftp client)

Here is Alpha response to this:
> P00>>>boot -protocols bootp ewa0
> (boot ewa0.0.0.3.1 -flags 1)
>
> Trying BOOTP boot.
>
> Broadcasting BOOTP Request...
> ..file open failed for bootp/ewa0.0.0.3.1
> bootstrap failure
>
> Retrying, type ^C to abort...
>
> (boot ewa0.0.0.3.1 -flags 1)
>
> Trying BOOTP boot.


And what server says:
> Sep 30 00:03:43 fly dhcpd: BOOTREQUEST from 00:00:f8:10:48:41 via eth0
> Sep 30 00:03:43 fly dhcpd: BOOTREPLY for 192.168.0.12 to AlphaBeta (00:00:f8:10:48:41) via eth0
> Sep 30 00:03:45 fly dhcpd: BOOTREQUEST from 00:00:f8:10:48:41 via eth0
> Sep 30 00:03:45 fly dhcpd: BOOTREPLY for 192.168.0.12 to AlphaBeta (00:00:f8:10:48:41) via eth0


I use an Alpha Linux kernel, because I did not know what to put.

Shall BOOTP answer a bootloader like for PXE, or a kernel file ?

Where/how do I get a bootloader ? For x86, there is a syslinux project;
any equivalent for Alpha ? (maybe not required).

How to pass kernel arguments and initrd informations ?

Are there specific options/features I should set in DHCP conf ?

Am I right in focusing on BOOTP and forget about MOP ?
How/does ISC make the difference between a BOOTP and a PXE request ?

What does the server-name field should point to ? should this name have
public resolution ? when is it solved ?

*** *** ***

Just in case, i provide my complete /etc/dhcp3/dhcpd.conf ...

> fly:/home/tftp# cat /etc/dhcp3/dhcpd.conf |grep -v "^#" | grep -v "^$"
> ddns-update-style none;
> option domain-name "doublehp.org";
> option domain-name-servers 212.27.53.252, 212.27.54.252, 212.27.32.5, 212.27.32.130, 212.27.32.2;
> option subnet-mask 255.255.255.0;
> default-lease-time 3600;
> max-lease-time 7200;
> allow booting;
> allow bootp;
> next-server 192.168.0.205 ;
> filename "/home/tftp/i386/current/images/netboot/pxelinux.0" ;
> subnet 192.168.0.0 netmask 255.255.255.0 { # normal DHCP
> range 192.168.0.120 192.168.0.199;
> option broadcast-address 192.168.0.255;
> option routers 192.168.0.1;
> }
> log-facility local7; #forget what it is
> host twinintel {
> hardware ethernet 00:90:27:8f:bd:d1 ;
> fixed-address 192.168.0.99 ;
> next-server 192.168.0.205 ;
> filename "pxelinux.0" ;
> }
> host carte3comC { # PXE machine
> hardware ethernet 00:01:02:b9:4a:3e ;
> fixed-address 192.168.0.190 ;
> next-server 192.168.0.205 ;
> filename "/home/tftp/i386/current/images/netboot/pxelinux.0" ;
> }
> host sirius { # DHCP machine
> hardware ethernet 00:60:08:90:4F:36 ;
> fixed-address 192.168.0.98 ;
> }
> host KifAMD64 { # PXE machine
> hardware ethernet 00:11:09:d4:fa:c0 ;
> fixed-address 192.168.0.191 ;
> next-server 192.168.0.205 ;
> filename "/home/tftp/i386_netboot/pxelinux.0" ;
> }
> host AlphaBeta { # Alpha machine to set up as BOOTP
> hardware ethernet 00:00:f8:10:48:41;
> fixed-address 192.168.0.12;
> server-name "fly";
> next-server 192.168.0.205;
> filename "/home/tftp/alpha/vmlinuz-2.6.18-6-alpha-smp";
> }
> fly:/home/tftp#


Server is fly(192.168.0.205); client is Beta(192.168.0.12).

--
>o_/ DEMAINE Benoit-Pierre (aka DoubleHP) http://benoit.demaine.info/

If computing were an exact science, IT engineers would not have work \_o<

"So all that's left, Is the proof that love's not only blind but deaf."
(FAKE TALES OF SAN FRANCISCO, Arctic Monkeys)