James Harper via luv-main writes:

>> Your router had to support the option 60. It cannot be done separately.
>> The option 60 tells the client the ip and path to you tftp server.
>>
>
> That is incorrect. You can have a regular DHCP server, and then have the boot 
> options supplied by the PXE server (Microsoft's WDS does this). The 
> communication goes (very approximately) like:
>
> Client: Give me the info I need to boot
> DHCP Server: Here is an IP address, subnet mask, DNS Server, gateway, etc
> PXE Server: Here is your tftp server and path
>
> It is possible to run PXE on the same server as the DHCP server, but
> it's a bit hacky. In this case the DHCP server sets option 60 that
> tells the client to do another DHCP request on port 4011, so it
> doesn't try to use the standard DHCP port.
> (http://www.experts-exchange.com/articles/2978/PXEClient-dhcp-option-60-what-is-it-for-Can-I-use-PXE-without-it.html)
>
> You can still do it the old fashioned way and just set next-server and path 
> on the DHCP server, which would work but my DHCP server is in the router and 
> doesn't support this.

I don't understand how this works.
Assuming the DHCP server can't be configured,
i.e. it does not send 'next-server' (66) & 'filename' (67),
how does the PXE server provide it?

They write:

| When using a PXEService, dhcp options 66 and 67 are sent to the PXE
| clients by the PXE service itself, not by DHCP service.

So the DHCP client does a DISCOVER,
and the DHCP and PXE servers both reply with independent OFFERs,
and the client somehow merges them together?  <VERY CONFUSED>

Can you share a .pcap of where this is happening?

...ah, never mind:

https://en.wikipedia.org/wiki/Preboot_Execution_Environment#Integration

It sounds like you're talking about this "proxyDHCP" thing,
and "the client somehow merges them together" is right.
YUK.


PS: Just so we're all on the same page re DHCP options,

https://en.wikipedia.org/wiki/Dynamic_Host_Configuration_Protocol#DHCP_options

| 60   Vendor class identifier    minimum of 1 octet
| 61   Client-identifier          minimum of 2 octets
| 66   TFTP server name           minimum of 1 octet
| 67   Bootfile name              minimum of 1 octet

_______________________________________________
luv-main mailing list
[email protected]
https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main

Reply via email to