Issue booting PXE on clients
-
Howdy, fellas. I am looking for help.
I have the newest version of FOG installed and I am working with the VMWare virtualizer.
I have my FOG server in a Ubuntu 18.04 virtual environment inside a windows server 2022 computer. I have configured the bridge network adapter so that ubuntu can be displayed on my LAN. PCs on my network can already access the dashboard through the FOG URL (the one that comes with the IP address of the FOG server). The problem comes when I try the network booting with PXE in my others PCs. I tried it with one computer with windows11 and another with w10, and it just doesn’t give me the FOG boot.
My FOG server, my Ubuntu environment and the wserver computer are within the same network, as are the other PCs. But I can’t get it to throw FOG when network booting.
I thought it was a problem that I first configured my FOG with nat adapter of my virtualizer. But I already changed the IP as advised in a forum post. But now I don’t know why I can’t get it to boot.
If anyone has had the same thing happen, I hope you could help me or advise me to know what I am doing wrong or misconfiguring. I have 1 month searching for information and I can’t find anything about it.
I apologize for my English, I am Hispanic but I tried to explain myself very well and thank you very much.
-
@Koffinny Please be more specific on what version of FOG you installed as “the newest” can mean different things.
Did you say yes when the installer asked if you want it to setup DHCP for you. If you said no and already have a DHCP server in your network (the one you bridged to in VMware) you need to configure DHCP option 66/67 to make PXE boot work.
-
@Sebastian-Roth said in Issue booting PXE on clients:
you need to configure DHCP option 6
Hello, good morning. Sorry but I took a vacation to clear my mind. Yes, I am working with the newest version of FOG. It was the version I installed.
Yes, when the DHCP option came up I wrote “no” because my network already works with a DHCP server, but I have not found a way to configure the 66/67 option for network boot. I don’t know if it is on the computer where I have my virtual environment, or on my DHCP server. I have searched for information and I can’t get a clear answer.
Sorry but I am new in this world
-
@Koffinny said in Issue booting PXE on clients:
but I have not found a way to configure the 66/67 option for network boot
What device is your dhcp server? Is it windows, linux, or some kind of router.
Usually that device will have the ability to either enter the pxe boot info directly or you need to add in dhcp option 66 which will contain the IP address of the fog server and dhcp option 67 will be the boot file name. For uefi computers enter snponly.efi and for bios computers enter undionly.kpxe for the boot file.
-
@george1421 said in Issue booting PXE on clients:
What device is your dhcp server? Is it windows, linux, or some kind of router.
Usually that device will have the ability to either enter the pxe boot info directly or you need to add in dhcp option 66 which will contain the IP address of the fog server and dhcp option 67 will be the boot file name. For uefi computers enter snponly.efi and for bios computers enter undionly.kpxe for the boot file.Sorry for taking so long.
It is a Tp-Link router and, according to what I was told, it should work automatically with pxe. But when I commented about option 66 and 67 they told me that they did not know how to do it. Should I go into the router configuration and change the file you mentioned? -
@Koffinny said in Issue booting PXE on clients:
It is a Tp-Link router
I have seen many soho routers not support pxe booting or have the options to set dhcp option 66 and 67. If your pxe booting computers and your FOG server is on the same subnet its probably the best solution (assuming your router doesn’t support pxe booting natively) to install DNSMASQ on the fog server to provide pxe booting info (only). DNSMASQ is kind of a swiss army knife of a tool, but supporting proxydhcp is one bit that we will use. It takes about 10 minutes to install and configure on your fog server and probably less time you’ve spent with yoru current router. Realize that dnsmasq will only give you the pxe boot information your main dhcp server will provide everything else. No changes are needed on your network unless you want to pxe boot across a router. Then there is one simple setting you need there.
I have a tutorial on how to install dnsmasq on your fog server here: https://forums.fogproject.org/topic/12796/installing-dnsmasq-on-your-fog-server?_=1681250221198
-
@george1421 said in Issue booting PXE on clients:
https://forums.fogproject.org/topic/12796/installing-dnsmasq-on-your-fog-server?_=1681250221198
Ok, let me check with my boss and give me a few days to see if I can fix it. Because we have some work to do. Thank you very much for the help and I hope it works because I’ve been trying to get this implementation out for about a month.
Practically, they let me do it all and no device information or anything hahaha.
