Return to BSD News archive
Xref: sserve comp.protocols.tcp-ip.ibmpc:12859 comp.protocols.tcp-ip:20886 comp.unix.bsd:8572 Newsgroups: comp.protocols.tcp-ip.ibmpc,comp.protocols.tcp-ip,comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!uunet!zaphod.mps.ohio-state.edu!caen!batcomputer!ghost.dsi.unimi.it!newsserver.di.unipi.it!pical2!luigi From: luigi@iet.unipi.it Subject: Re: BOOTP ROM problem: SOLVED Message-ID: <1992Nov25.181758.24448@cli.di.unipi.it> Originator: luigi@pical2 Sender: luigi@iet.unipi.it Nntp-Posting-Host: pical2.iet.unipi.it Reply-To: luigi@iet.unipi.it Organization: Dip. di Ingegneria dell'Informazione, Univ. di Pisa (ITALY) References: <1992Nov25.135026.18329@cli.di.unipi.it> Date: Wed, 25 Nov 1992 18:17:58 GMT Lines: 60 In article <1992Nov25.135026.18329@cli.di.unipi.it> luigi@iet.unipi.it writes: >We are having problems with a BOOTP prom for WD8003 cards. The BOOTP >PROM is Beame & Whiteside v.1.1a for WD8003, and works perfectly with an >Ultrix 4.1 server. But when trying to make it work with AIX 3.2, or with >a port of CMU bootpd we made to 386bsd, it doesn't work anymore. It Well, the problem has been solved now, at least with 386bsd (and thus I think it will work with AIX as well, given the symptoms). But a few words of explaination might help other people with the same problem: >appears that the PC sends the bootp request, the host replies, the PC >receives the reply and then simply asks "Enter boot volume name: " >instead of getting the file via tftp. tftp seems to work on all of the >machines, without special configurations or permissions. >So which one of these is true ? > >1) I didn't do something I should have on the host. >2) Ultrix 4.1 bootp replies differ from the ones produced by CMU bootpd > (which is likely to be the source of AIX bootpd), and the latter > are either buggy or non-recognized by B&W BOOTP ROM >3) there is some bug in the ROM code > >Of course I hope 1) is the right explaination. Any help from the net ? 1) is true, 2) is (more or less) false, 3) is (more or less) false. To be precise, the problem has nothing to do with bootpd, but with tftpd. The version of tftpd on 386bsd (and probably on AIX 3.2) will not prepend anything to the pathnames of the requested files. Thus, even if I specify something like tftpd /mytftpdirectory in /etc/inetd.conf or its equivalent for AIX, requests for /bwboot/default.wd8003 will look for the absolute pathname. BTW, this tftpd will not send files which are not in the trees specified as parameters to tftpd. On Ultrix 4.1 instead, the above situation would cause tftpd to look for /mytftpdirectory/bwboot/default.wd8003 and to send the file as requested. This is also what B&W documentation says: The file "default.wd8003" must be created in the directory "bwboot" which is a subdirectory of the tftpd's working directory. See the file "default.set" about the make up of the "default.wd8003" file. For 3C501 cards substitute "default.3c501" for "default. and is the reason why things did work fine on Ultrix 4.1 but not on the other, newer machines. So, the bug is mainly in the documentation. Oh well, as a fallout of all this, now at least I have a working bootpd under 386bsd... Thanks for the interest Luigi Rizzo ==================================================================== Luigi Rizzo Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it Universita' di Pisa tel: +39-50-568533 via Diotisalvi 2, 56124 PISA (Italy) fax: +39-50-568522 ====================================================================