<div class="gmail_quote">2009/3/31 Simon Kelley <span dir="ltr"><<a href="mailto:simon@thekelleys.org.uk">simon@thekelleys.org.uk</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Guilherme Moro wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">
hello all,<br>
<br>
You implemented the pxe menu system (really messy spec), great work !<br>
<br>
for the proxyDHCP, cant make it work here, what exactly to add to dnsmasq.conf ( never used the dnsmasq before ) ?<br>
<br>
I put only :<br>
<br>
interface=eth0<br>
dhcp-range=192.168.1.0,proxy<br>
log-dhcp<br>
<br>
it output something showing the received packet, but dont respond to the DISCOVER, the output :<br>
<br>
dnsmasq-dhcp: DHCP packet: transaction-id is 2735344808<br></div>
dnsmasq-dhcp: Available DHCP subnet: <a href="http://192.168.1.0/255.255.255.0" target="_blank">192.168.1.0/255.255.255.0</a> <<a href="http://192.168.1.0/255.255.255.0" target="_blank">http://192.168.1.0/255.255.255.0</a>><div class="im">
<br>
dnsmasq-dhcp: Vendor class: PXEClient:Arch:00000:UNDI:002001<br>
<br>
</div></blockquote>
<br>
You need a pxe-prompt line and at least one pxe-service line too: it's not clear if you have those or not.<br>
<br>
If dnsmasq detects a PXE DISCOVER and sends a proxy reply, it will log something like:<br>
<br>
dnsmasq PXE(eth0) <MAC address> proxy<br>
<br>
Any DHCPDISCOVER packet which has option 60 as "PXEClient*" will trigger a broadcast DHCPOFFER reply.<br>
<br>
Simon.</blockquote><div><br>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. <br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
About the 4011 port, the first version of my proxy responded only the DISCOVER with an OFFER, as you described, but some clients (specifically the 3com client of some cards I have here) follows the spec strictly, and if detect a proxyDHCP, they only accept to boot from a filename that come from a REQUEST on port 4011 , they just thrown away the empty IP OFFER that he get on the DISCOVER.<br>
</blockquote>
<br></div>
I'm confused: you are saying that the bootserver request moves to port 4011, or the proxyDHCP request? Can you tell me what 3com cards hit the problem? I may be able to get hold of one for testing.<br>
</blockquote><div><br>Sorry for the confusion, I have made tests here with my 3com card, and using pxe-menu the card accepts the OFFER.<br>its not the spec behavior, but should work with almost all clients.<br>Perhaps my proxyDHCP implementation have some other problem that pass unnoticed.<br>
<br>Great work, now we have a open source solution for proxyDHCP. =)<br><br>Guilherme Moro<br></div></div>