Commit 715da835 authored by Robert Ricci's avatar Robert Ricci

Try to clear up some confusion - boss has to be the nameserver.

parent 3d009ba0
......@@ -8,12 +8,13 @@
# servers' IP addresses, the router's IP, and see the comment about nodetypes
# below.
#
server-identifier 155.101.128.70;
server-name "155.101.128.70";
next-server 155.101.128.70;
server-identifier 155.101.128.70; # boss's IP address
server-name "155.101.128.70"; # boss's IP address
next-server 155.101.128.70; # boss's IP address
option domain-name-servers 155.101.128.70;
option domain-name "emulab.net";
option domain-name-servers 155.101.128.70; # boss's IP address
option domain-name "emulab.net"; # should be the same domain
# boss is in
option root-path "/tftpboot";
......
......@@ -94,12 +94,13 @@ addresses. However, at this point, we don't know those MAC and IP addresses, so
we have to set up DHCP to actually do some dynamic stuff. Copy
dhcpd.conf.template from the dhcpd/ directory of the source tree into
/usr/local/etc . Edit it to get your actual boss IP, domain, control network
subnet and mask, etc. into it. Now, see that line that says 'range ...'?
Uncomment that line, and put in a range of IP addresses that is in the control
network, but is _not_ going to be used by nodes. Ideally, this range should be
large enough to fit all the nodes into it. If it's smaller, remember this for
later, when we get to bringing up the rest of the nodes. Make the config file
from the template with:
subnet and mask, etc. into it. For things to function properly, boss will need
to be listed as the nameserver in this file. Now, see that line that says
'range ...'? Uncomment that line, and put in a range of IP addresses that is
in the control network, but is _not_ going to be used by nodes. Ideally, this
range should be large enough to fit all the nodes into it. If it's smaller,
remember this for later, when we get to bringing up the rest of the nodes. Make
the config file from the template with:
/usr/testbed/sbin/dhcpd.makeconf dhcpd.conf.template > dhcp.conf
... then (re) start dhcpd with:
/usr/local/etc/rc.d/2.dhcpd.sh restart
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment