@george1421 Currently, I am engaged in scientific research across several buildings utilizing the university’s network infrastructure. The university manages this network, granting us limited control for adjustments while restricting access to configurations and firewalls. Within our campus, four buildings fall under our management, including the switches. Our FOG server operates effectively within this cluster. An additional building, located 4 kilometers away, shares the same network subnet. Both our campus and the university utilize a common DHCP server for this subnet, while we employ DNSMASQ to enable FOG functionality.
While we can successfully ping and access services within the network, FOG booting remains unsuccessful. We talked with the university to check if they are blocking some services and they told us that they aren’t (they are willing to help us with this problem). Sending traffic to the FOG server’s UDP port 69 from the distant building results in successful packet capture, as observed using tcpdump’s UDP feature. But when it comes to PXE booting, It simply doesn’t work.
Considering this, we contemplated employing a dedicated storage node within the distant building to serve as a TFTP server, aiming to address the issue. Despite attempts to configure a storage node and disable DNSMASQ on the primary FOG server, PXE booting only advances to the login screen before encountering a chainload error upon accessing “boot.php” from the main server.
We have tried many things and surely there are couple of things that we checked but I dont actually remember. If someone knows any method to check why things are failing, or alternative solutions would be greatly appreciated.