On Wed, 2002-09-11 at 11:49, John Clay wrote:
> I justed installed the dhcp server.
>
> Is /etc/dhcp.conf the only file that will need to be configured?
>
> Apparently dhcp is run like so: # dhcpd
>
> I'm doing all this work while connected to our NT/2K based LAN. I'm concerned
> about unanticipated interaction between my 2K dhcp server and the Linux dhcp
> server. How would you handle that - disconnect from the main LAN and connect my
> Linux server and ThinkNIC via a spare hub?
Well, here's the thing: you really can't have more than one DHCP server
on a segment unless you statically add host entries by hand. If you
define a range of IPs for anyone to use, the first DHCP server to
respond will "win" that client.
So, to not confuse yourself, I would recommend using only one or the
other.
PXE requires specific records to be defined (PXE extensions) in a DHCP
response else it will not work. It isn't as simple as turning on a
generic DHCP server and PXE clients start booting. If you're using dhcpd
v2.2, for example, you will need the following at the top of your
dhcpd.conf:
allow booting;
allow bootp;
option dhcp-class-identifier "PXEClient";
option vendor-encapsulated-options
09:0f:80:00:0c:4e:65:74:77:6f:72:6b:20:62:6f:6f:74:0a:07:00:50:72:6f:6d:70:74:06:01:02:08:03:80:00:00:47:04:80:00:00:00:ff;
Then, you will need to have a host section for each host you wish to
boot:
host devnull1 {
filename "devnull" ;
hardware ethernet 00:e0:06:e7:fe:0c;
fixed-address 10.0.0.101;
next-server 10.0.0.4;
}
This will tell the client "devnull1" with a MAC of 00:e0:06:e7:fe:0c to
boot with the IP 10.0.0.101 and use tftp to grab the file "devnull" (or
/tftpboot/devnull as you used -s) from the TFTP server at 10.0.0.4
That's basically it. All other DHCP options are up to you and your
network configuration.
- Ian
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 19:18:15 EDT