@george1421 I apologize for not getting back sooner. I restarted my server and made sure that DNSMASQ was actually running. This time when I attempted to PXE boot it actually completed! One little quirk that I noticed was that one of my machines took a really long time to obtain an IP…
Now, I’m not sure if this is possible, but would it be difficult to make this work cross vlan? Or will it only work with clients within the infrastructure vlan?
My current setup is this:
Fog server is on infrastructure vlan(172.16.1.x)
I need to use Fog on Staff vlan (172.16.10.x), and Student vlan (172.16.20.x)
Here is a section from my setup file:
# This range(s) is for the public interface, where dnsmasq functions # as a proxy DHCP server providing boot information but no IP leases. # Any ip in the subnet will do, so you may just put your server NIC ip here. # Since dnsmasq is not providing true DHCP services, you do not want it # handing out IP addresses. Just put your servers IP address for the interface # that is connected to the network on which the FOG clients exist. # If this setting is incorrect, the dnsmasq may not start, rendering # your proxyDHCP ineffective. dhcp-range=172.16.1.31,proxy,255.255.0.0
Thank you guys so much! You have no idea how much you have helped me!