Specify different pxeclients "next-server" for different subnet?
drew.weaver at thenap.com
Mon Jan 12 16:52:03 UTC 2009
No quotes here; it makes a difference.
Now that I think about it, the server might not accept an IP address here;
in theory, the RHS of an assignment can be any expression type, but I can't
remember if the parser is clever enough to do the right thing with an IP
address. Perhaps someone who touches the parser internals more often than
I would like to comment (David?).
> I also tried replacing option server.next-server = pxe_server; with
> next-server pxe_server;
That won't work. Without the =, it becomes an option declaration rather
than an executable-statement, with the result that it's processed too early
and that the RHS is treated as a hostname/ip address and not as an
Is it possible to put classes inside of subnets and not globally, or can you think of any other way that I could achieve this?
It seems like it should be fairly trivial to assign separate next-server options for PXEClients on a per subnet basis.
More information about the dhcp-users