Connecting FOG to Virtual Machine

[Sebastian Roth]

@agray Which IP do you get within the VM (Windows booted)?

[agray]

@Sebastian-Roth 192.168.1.141

[Sebastian Roth]

@agray Maybe you have some Windows firewall security software running on the host machine?!

[agray]

@Sebastian-Roth Firewall is completely off for Domain, Private, and Public and it doesn’t have an AV

[Quazz]

Given that it connects to the DHCP server and gets an IP as we can see from the screenshot but fails after loading the IPXE file, I’d suggest serving a different IPXE boot file and see if that works.

You’ll have to modify your router DHCP settings to serve a different file (eg ipxe.pxe instead of undionly.kpxe)

[agray]

@Quazz My router doesn’t have the option to change the file. Let me try booting into iPXE.pxe and i’ll update you.

[Quazz]

@agray Well, if I’m following this thread correctly, the IP of the DHCP server initially is the FOG server itself, not the router.

If you can’t change IPXE options on the router and still want to use its DHCP server rather than FOG DHCP, then you have to set up proxyDHCP via dnsmasq on the FOG server (and disable the dhcp server on it)

[agray]

@Quazz It might be the FOG server serving IPs. I’ve never had an issue booting to PXE and FOG with a physical machine, only this VM.

[agray]

@Quazz I booted to iPXE.pxe but i’m sure what i’m doing with this CL to boot to FOG. I’ve tried ‘autoboot’ but i got the output “Nothing to boot: No such file or directory”

[Quazz]

@agray Where did you change these things?

[agray]

@Quazz I mounted the .iso to my VM and booted to it.

[Quazz]

@agray You need to serve the ipxe.pxe file that’s on the FOG server, since it seems to be the DHCP server.

That being said

I can boot VirtualBox 5.2 VMs to IPXE on undionly.kpxe as well as ipxe.pxe just fine.

Do you have the VirtualBox extension pack installed?

[agray]

@Quazz said in Connecting FOG to Virtual Machine:

Do you have the VirtualBox extension pack installed?

Yes, but my VirtualBox is 6.0. Would that make a difference?

[agray]

Is there a way to use FOG off a usb to capture. that may be a work around i can use

[agray]

@Quazz @Sebastian-Roth Would my physical machine being on my domain be causing this issue?

[Sebastian Roth]

@agray What exactly do you mean by “Domain”? As in Windows Domain? This has nothing to do with PXE boot. Or as in network domain like VLAN or subnet? That might play a hole.

I think the best would be you capture the network traffic on your host machine using wireshark, save as PCAP file, upload to a file share and post a download link here.

[agray]

@Sebastian-Roth Here is the .pcap file of my VM attempting to PXE boot from the host point of view: https://drive.google.com/file/d/1zbHmSCoOC2tzi8xp5EVnj6KrhQwvSOcU/view?usp=sharing

After attempting to PXE boot with host off AD Domain. I’m getting a nicer looking wireshark output but still no dice on the PXE boot: https://drive.google.com/file/d/11GiICfArOKqcFUWdF6hQHV51r8oHTebV/view?usp=sharing

[Quazz]

@agray I’m assuming that if it’s on the domain that there already is a DHCP server on the network and that it is conflicting with the FOG one. Haven’t taken a look at the PCAP (don’t have time), though

[agray]

@Quazz Our domain is strictly static and FOG is isolated completely off it. A rough topology of our FOG network is on the second page of this thread

[Quazz]

@agray Yes, and around that same area it is mentioned that there is a DHCP server on the router?