[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Installing Potato with tftp on UDB



Hi,
Try setting your ewa_protocols to BOOTP in SRM. 

Peter 


Bart-Jan Vrielink wrote:
> 
> Hello,
> 
> I finally found some time to try to re-install Linux on my Multia. Today I
> tried to use tftp/bootp to boot the Potato tftpboot.img.
> The server is running Potato/i386.
> 
> I have dhcpd installed (already use it to serve a few dhcp clients) and
> did a apt-get install tftpd. I have added 'allow bootp' to the subnet and
> host part of my dhcpd.conf:
> subnet 10.2.1.0 netmask 255.255.255.0 {
>   allow bootp;
>   host centauri {
>     hardware ethernet 08:00:2b:e4:41:27;
>     option domain-name "vrielink.net";
>     fixed-address centauri.vrielink.net;
>     allow bootp;
>   }
> }
> 
> and restarted dhcpd.
> I have enabled tftpd in inetd.conf and restarted inetd. tftpboot.img is
> placed in /boot but because the installation manual is a bit vague on
> choosing the correct name for the image I decided to test the bootp part
> and issued the boot command:
> >>>boot ewa0
> (boot ewa0.0.0.8.0 -flags 0)
> 
> Trying MOP boot.
> .Switching network ewa0.0.0.8.0 from Thin Wire to Twisted Pair...
> .......bootstrap failure
> Retrying...
> 
> and so on. On the server I see the following a few times in tcpdump:
> 20:58:09.378421 centauri ab:0:0:1:0:0 mopdl 79:
>                          3f00 0849 0102 0000 0100 0304 0000 0200
>                          0279 0003 0006 0000 0000 0000 0400 023c
>                          0005 0002 4000 0600 0200 0207 0006 0800
>                          2be4 4127 6400 0149 9001 0101 9101 02da
>                          05
> There is no reply from the server and I'm certain that there is no other
> bootp/dhcp server available on my network.
> 
> What goes wrong ?? and if I get past this point: how should I name the
> tfpboot.img ??
> 
> --
> Tot ziens,
> 
> Bart-Jan
> 
> --
> To UNSUBSCRIBE, email to debian-alpha-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org



Reply to: