[Dnsmasq-discuss] proxy dhcp does not send dhcp-options
jochen.dekeyser at gmail.com
Tue Apr 10 10:15:52 BST 2012
I looked into the pxespec.pdf and the RFC's 2131 and 2132. If I get
this right, theoretically, it is possible, but it probably has never
So, I will be looking for other solutions :-).
Thanks for helping me out!
On Mon, Apr 9, 2012 at 8:54 PM, Simon Kelley <simon at thekelleys.org.uk> wrote:
> On 09/04/12 18:24, Jochen Dekeyser wrote:
>> I previously tried it using only dhcp-option 17, like they do here:
>> Dhcp-option 17 is the root-path: the path which should be used by the
>> pxe-client to boot from. This should be proxy dhcp-stuff, not?
> I quick look through the old dnsmasq releases shows that this hasn't ever
> changed, so the UbunutuLTSP can never have worked in the proxy format.
> I consulted the PXE spec:
> and on page 25 it says:
> In this state, the client must also be prepared to receive one or more
> standard DHCPOFFER messages from servers. Each of these messages will
> contain configuration information as specified in RFC 2131. Each extended
> DHCPOFFER message can also contain configuration information as specified in
> RFC 2132. Which, of these configurations, if any, is used by the client is
> not defined by this specification. If the client decides to accept one of
> the configurations offered, then it must engage in further communications
> with the server as specified in RFC 2132.
> So this method is, at least theoretically possible. I wonder if any clients
> implement it in a sane way?
More information about the Dnsmasq-discuss