[Dnsmasq-discuss] Feature request: make dnsmasq able to work
as a proxydhcp
Simon Kelley
simon at thekelleys.org.uk
Tue Mar 31 21:44:55 BST 2009
Guilherme Moro wrote:
> Ok, now working, but why proxy DHCP is attached with boot menus? There
> should be a option to just throw the bootfilename to the client using proxy,
> I think.
I kind of assumed that proxy would need the full PXE protocol, with
options 60 and 43 in the reply. Does it really work just to send a
filename in the proxy reply? It's possible to boot straight to a
particular file by setting the prompt timeout to zero, and sending only
one menu option.
> Sorry for the confusion, I have made tests here with my 3com card, and using
> pxe-menu the card accepts the OFFER.
> its not the spec behavior, but should work with almost all clients.
> Perhaps my proxyDHCP implementation have some other problem that pass
> unnoticed.
>
I found an old 3C905, with PXE 2.0 and it seems to work fine there.
> Great work, now we have a open source solution for proxyDHCP. =)
I did some more testing, using PXE to chainload gPXE, and it turns out
that gPXE sends the PXEClient vendorclass, but can't talk the protocol
:-( So I need to still send the filename in DHCPACK packets even when
the client claims to be PXE so that gPXE can still work the old way.
gPXE also asks for option 67 but ignores it when it gets the filename
that way, so it needs the --no-dhcp-override dnsmasq option. :-( :-(
I've put 2.48test9 which fixes this in the usual place.
Simon.
>
> Guilherme Moro
>
More information about the Dnsmasq-discuss
mailing list