Hi Everyone- I took a look at ISC DHCP last week and found it quite easy to use. I've set up AI configurations quite a few times, and everytime I do, I run into all kinds of problems with the Sun DHCP set up.
Here is a brief summary of what I've done so far in evaluating the ISC DHCP server. To begin with, my system configuration consists of a private network with a linksys router connecting it to the internet. I have an ultra 40 running the latest build of opensolaris on it (in this case 106). I connect various laptops to the network and test AI images. To get ISC DHCP, I added blastwave.org to my pkg authorities and downloaded the ISC DHCP package. #pkg set-authority -O http://blastwave.network.com:10000 blastwave #pkg install IPSdhcp The two files that we interact with (at least as far as I know thus far) are: /etc/opt/csw/dhcpd.conf.CSW /opt/csw/sbin/dhcpd The first one is the configuration file. The second is the command to start the service. The man pages are included in the package. I've attached two configuration files. They mirror the steps that I took in getting things running. The dhcpd.conf.basic file contains a simple instantiation of a dhcp server. Contents include: ddns-update-style - defines whether to allow the DHCP server to dynamically update the Domain Name System. This is set as a global variable The rest of the configuration file sets up the server subnet as the authoritative DHCP server on the |192.168.1.0| subnet. It will hand out addresses from |192.168.1.10| to |192.168.1.20 | (the range option) to any host that asks for one. The router option is the ip address of my linksys router, which gives access to the rest of the internet. I think all of the other parameters are pretty self-explanatory. Once I had this configuration file, I ran the following command to activate the dhcp server: #/opt/csw/sbin/dhcpd -d -f -cf /etc/opt/csw/dhcpd.conf.basic I confirmed the server was working by plugging in a laptop. It obtained a dhcp address, and I was able to get out to the internet. The dhcpd.conf.pxe file contains a slightly different configuration, as well as the options required for PXE. The first entries are global. These include the DNS information and Lease time, as well as the ddns-update-style statement. The additional use-host-decl-names statement sets how the clients will receive host names from dhcp. The next entries enable the PXE boot. I'm going to gloss over those except to say that they just work. For this example, I used a very simple instance to test the PXE and AI. I input the MAC, gave it a fixed address, and manually pointed it to the boot file ( the filename statement). I realize that for AI this needs to be more dynamic, but I wanted to just see if I could get it to work. The last entry is basically the same subnet info. The nice thing about this is that I set up the dhcpd.conf.pxe file, started the dhcp server, ran the installadm create-service and installadm create-client commands, and the whole thing worked cleanly. My plan is to next take a look at how to make the client configuration less static. I am interested in any and all feedback. thx, -- Ginnie -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/caiman-discuss/attachments/20090210/007fce60/attachment.html> -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: dhcpd.conf.basic URL: <http://mail.opensolaris.org/pipermail/caiman-discuss/attachments/20090210/007fce60/attachment.ksh> -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: dhcpd.conf.pxe URL: <http://mail.opensolaris.org/pipermail/caiman-discuss/attachments/20090210/007fce60/attachment-0001.ksh>
