Hi,
On Mon, Apr 30, 2012 at 11:45, Dick Davies <rasputnik(a)hellooperator.net>wrote:
I might be misreading the links.
Our main DHCP server knows nothing about Cobbler, and we don't run
a dhcpd on the Cobbler host.
we use Cobbler to server the /pxelinux.0 (and associated gubbins) and the
rest of the kickstart stack
and just set next-server in the main DHCP server config
(which we don't control) to point at the Cobbler TFTP host.
That works fine; am I misunderstanding your setup (I'm still stocking up
on coffee)?
Apparently you got to set the next-server setting in the DHCP server. So
you had enough control to do it that way.
I faced the situation where there was no option of adding any settings at
all to the DHCP reply. So I was "forced" to find a solution. (and this is
it)
I found that there are two common reasons this may happen:
1) The central sysadmin is not willing, capable, able or allowed to make
the change.
2) The currently deployed DHCP server does not have the option to set the
required options. I see this a lot with ISP provided home routers.
Does this clarify it for you?
--
Met vriendelijke groeten,
Niels Basjes