SUMMARY+HELP?: bootp + Solaris

From: Greg Coleman (
Date: Thu Mar 30 1995 - 12:06:05 CST

> 1) Has anyone set up a Solaris machine as a bootp server and can
> share some info?
> 2) Can anyone direct me to bootp source?

Sun Masters,
        I was waiting to summarize this until I had it completely
working. Since that plan failed and its been a few weeks, I will
summarize now. I was directed to bootp source at

I took 2.4.2 and compiling it (Solaris 2.4) was real straight forward
and easy. I followed instructions in the README files and also some
that were sent to me. (included below) Soon I had a bootp daemon running
on my SS10.

Problems remaining;
The damn PC's. I want to manage all the IP address for them from this
BOOTP server. I hoped to have each PC not care about what its host name
is or IP address is and BOOTP will assign it when they boot up. Here is
my test config file; (/etc/bootptab)

        :gw= \
If the PC TCP stack on gregc has an IP address, bootpd responds with
the router, subnet, bcast, etc. BUT if I set the IP addr to,
it just times out. I want to manage the IP addresses from my SS10. Can't
I set up the bootptab file to indicate a pool of IP addresses to choose
from? Why do I need a host name in there? Can't it just key off the MAC
address? (Alot of users just have some bogus host name set up)

Anyhow, more help is very appreciated. I'll keep trying and summarize
again once it is working. Here is my list of Thanks....

I got bootp on solaris2.x
I've gotten the executables off the HP JetDirect CD. The should
also be on het NCDWare CD (in case you have NCD X-terminals).
If you do not have these CD's, I'm willing to send the executables
to you via email (uuencoded).
Just let me know (and be patient).
Bye the bye, it runs fine! Don't understand why SUN doesn't support
it by default.

Yes I have setup a Solaris 2.3 system as a bootp server for
diskless clients, it works well.
You don't need any source, the /usr/sbin/rpc.bootparamsd, the
executable already exists.
The problems I ran into were:
1) We use NIS and the nsswitch.conf file wasn't correct.
2) To solve the problem above, I modified my nsswitch.conf
   file to look in to the files for host, ethers and bootparams
   before looking in the nis maps.

We are running bootp on a 4.1.3 and a Solaris 2.x machine, so perhaps I can
help you.
You can grab the ftp source from:
untarred and edited the makefile to set the path names and bootptab file
appropriate to our site.
Then compiled on Solaris with:
   make sunos5 CC=gcc
And on Sunos with:
    make sunos4
To complete the installation, added the following lines to the services
NIS map:
bootps 67/udp bootp # BOOTP Server
bootpc 68/udp # BOOTP Client
And finally updated the /etc/inetd.conf file on the server machines with:
# bootp server
bootp dgram udp wait root /pub/bootp/prod/bootpd bootpd -i
It works great! Less Filling! :->

I set up a machine running Solaris 2.3 as a bootp server. The only
bootp client on this subnet is an HP printer with a jetdirect ethernet
card. It works fine. I ftp-ed the source for bootpd from

I'd used bootp service on Solaris 2.4 to use a node as an NCD terminal
server. This is how I did it:
1. Edit /etc/hosts and make sure you have all hosts and their
    corresponding IP addresses that you want to serve listed there
2. Edit /etc/inetd.conf and search for the line beginning with
    "tftp." The default is set for "secured tftp." If you would
    rather use it in "nonsecure" mode, delete "-s /tftpboot" from
    the line:
      tftp dgram udp wait root /usr/sbin/in.tftpd in.tftpd
3. Add the following line in this same file:
      bootps dgram udp wait root /etc/bootpd bootpd
4. Reread this file
      # ps -ef | grep inetd
      # kill -HUP pid#
5. Edit /etc/services to add the following lines (these lines are for
    NCD terminal server and client but I assume we can use these for
    any bootp server and client):
      bootps 67/udp # bootp server
      bootpc 68/udp # bootp client
6. I also created the /tftpboot directory (I then made links from my NCD
    files to this directory)
I hope this will help a little. Good luck!

I have bootpd sources here, that I've been using to boot alpha's
diskless, from Solaris 2.[34] machines.

> From: Greg Coleman <>
> Hi and thanks for the info. Is there a difference between
> rpc.bootparamsd and bootp? I amd confused about the hostconfig manpage
> stating something about bootp being unsupported.
> Thanks again,
> Greg
I looked at the man page and saw the unsupported. I guess that I
haven't kept up enough with what is going on in the world.
Here we have devices that resolve their IP address via rarp and
then load software via tftp.
I did a quick check of the RFC's and found the following had BOOTP
in their title:
If you need a copy of these RFC's they can be found on:
or I could mail them to you.

The bootparams protocol is not the same as the bootp protocol. At first
I thought it was, and tried to set things up so my HP printer would boot
from it. It didn't work, and I had to get the bootpd program. Bootparams
pretty much serves the same function as the bootp protocol. Suns use it
to boot off the network. Which one you can use depends on the devices
that you intend to have as clients; if they support bootparams you can
use that, otherwise you have to go with bootp. Installing bootp was
pretty easy. I think the only thing I had to modify was the makefile,
and the comments were pretty clear (you know, "uncomment this if you're
running on a SVR4-based unix").

>> Thu Mar 16 08:57:25 1995
What are you trying to do?
>> Thu Mar 16 10:23:28 1995
> >
> I want to manage IP addresses from my SS10 for a few hundred
> PC's running Ftp software and also some diskless workstations.
I mainly deal on the UNIX side of the house, and we use NIS or YellowPages (YP)
to maintain these lists. Our PC machines are listed in here, so all our UNIX
systems know all the PC systems. I don't know about PC's though. I'm assuming
if you can configure your PC to have a nameserver point to your SS10 (UNIX)
box which will be running YP, and named, then you can manage it on your SS10.
If you are running Solaris as a YP server, then you may have to run NIS+. We
currently are not doing that. Our YP servers are all 4.1.3 machines.
This is a big issue at our company too, but I personally haven't had to mess
with the PC stuff. But our UNIX stuff is running great, with a central place
for all our IP addresses and user accounts. When you have 200+ machines, you
need something to maintain it.
We also use whats called "rdist" to shoot out copies of various files that each
system needs. I don't know if it is available for PC's but you probably could
use FTP to copy the UNIX list of IP addresses to your PC for use by your PC
Now as far as your Diskless Workstations, they would probably all boot from
your SS10, which you can configure using "admintool".

Greg Coleman  ||  New York City  ||

This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:10:21 CDT