@george1421 WOL is now working as intended and DNSMasq is working a treat. I do not know why it was not working but the clients are now reliably receiving their packets since moving the DHCP server back to the Ubiquiti router. I can only assume there was some config stuff that I missed, but I am happy to run it like this.
Best posts made by Riry
-
RE: WOL and Host OS discovery issues.
Latest posts made by Riry
-
RE: PXE boot stuck at "Initializing devices" on HyperV legacy boot
@george1421 I’ll give that a try, thanks. Is this Github link the correct one?
-
RE: PXE boot stuck at "Initializing devices" on HyperV legacy boot
@george1421 A separate question that you may be able to help with, if I use some other service that creates images using Partclone would I be able to add and register that image to the FOG server’s image directory as a workaround for this?
I only need to capture these images once, really.
-
PXE boot stuck at "Initializing devices" on HyperV legacy boot
Legacy Hyper-V network boots utilizing undionly(all versions) hang on “Initializing devices” instead of properly booting. Server boots Gen2 machines fine.
I am using these legacy machines to create a baseline for older machines that aren’t compatible with windows 10 (Yes they are actually that old)
It will boot fine to the physical devices.
-
RE: WOL and Host OS discovery issues.
@george1421 WOL is now working as intended and DNSMasq is working a treat. I do not know why it was not working but the clients are now reliably receiving their packets since moving the DHCP server back to the Ubiquiti router. I can only assume there was some config stuff that I missed, but I am happy to run it like this.
-
RE: WOL and Host OS discovery issues.
@george1421 As I understand, WoL broadcasts to every IP address on the subnet to find a match for the MAC? I figured the DHCP server for some reason not behaving properly could have an affect on that, since I’ve tried sending magic packets outside of the FOG system on a few other VM’s or even the host machine now with no luck.
The main reason I am not just using the Ubiquiti DHCP server is that I couldn’t get it to play nice with both EFI and BIOS boot over PXE at the same time, the hardware I have to work with is varied and not all the CSM settings seem to work universally. Shifting DHCP over to the FOG Server gave me more flexibility to have whatever hardware is needed booting off the network.
I think I will give DNSMasque a try and see how that goes. Thanks for your help.
-
WOL and Host OS discovery issues.
Hello all,
Currently I am working on setting up a FOG instance for my company as they have been using macrium or an extremely outdated version of Ghost for image deployment prior to my coming on board.
Currently I am having issues with WoL, packets are being sent out but are not being received. I assume this has something to do with how FOG handles DHCP, as both that and the Host discovery were working perfectly prior to shifting DHCP services over to the FOG server.
The network is all managed by a Ubiquiti USG Pro, there are several V-Lans to segregate the network, however I only need WoL to work on one of those.
FOG is running on Debian 10.10, a clean, headless install with nothing else running on it. I am just using the default FOG DHCP Server that it installs, but I can see that a lot of people prefer DNS Masque.
My thought is that it is either the DHCP config on the FOG server or the way the VLAN is set up causing the issue?