Worst case I'll have to set up a virtual machine with ISC DHCPD, but I'd much prefer a small, simple solution. To download its configuration file and when. Or recover from a protocol application invalid message. Or if TFTPD32 can't do this, is there another equally easy to use piece of software that he can run on his Windows laptop? Since the TFTPD part is working fine, a DHCP server with the ability to serve PXE only would do. How do I configure TFTPD32 to ignore these non-PXE DHCP requests? I know this is (by allowing only requests from PXEClient vendor ids), but a nice windows GUI would be preferred. However I'm not sure how to configure TFTPD32 to only respond to PXE DHCP requests (the ones with the magic flag) and ignore all normal DHCP requests (so that the production machines don't get a non-routed address from the PXE server). I've set up a configuration which does just that, and our normal DHCP server ignores the PXE DHCP requests due to them having some magic flag, so this part works as desired. I want to give our Windows guy a way of easily PXE booting machines for deployment by plugging his laptop into one of our site networks.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
February 2023
Categories |