Good luck, you only need dnsmasq if you need to resolve to your file, if lets say for some reason your offered file is not received completely.
I use dnsmasq because there are IP helpers in my network that over ride my dhcp settings. I also use an out dated netware environment that has limitations on the boot file name length.
This length issue is also present in dnsmasq, that is why you have to symlink undionly.kpxe to undionly.0
Yes it is true that in the ltsp.conf file you have supplied the boot file name in its entirety, but when we began working to provide the undionly.kpxe as a boot file name, dnsmasq still had limitations. I do not know if these limitations are still present.
I hate to see you give up on trying to get dnsmasq to work, I feel it’s a wonderful solution, and with the use of dnsmasq you do not need to even edit the dhcp information to include the fog server or it’s boot file, dnsmasq works as a proxy dhcp server and issues the proper boot information to the client. If you choose to take it up again, dnsmasq that is, I would be happy to help you troubleshoot.
Yes I restart dnsmasq.
Now, I remove the server name, and make the symlink to undionly.0 (don’t understand why have to do it to this file?) in the ltsp.conf Irefer to undionly.kpxe.
The proxy thing, I don’t know, may be in my newtork this doesn’t work?
Did you restart dnsmasq after updating your ltsp.conf?
Try removing the server name from the ltsp.conf file and restart the service again.
There is suppose to be a line in the screenshot you provided Directly after DHCP: X.X.X.X there should be a PROXY: and its value should be the same as the FOG server IP address.
I also do not see a proper symlink to undionly.0, you will need to create a symlink to the file you are using, it appears that you are attempting to use undionly.kpx.INTEL
to use this file you need to issue the following command to your terminal\