Topics created by OmegaXis

@Patrix While you might have the same issue it could be a totally different problem as well. We just don’t know enough of you specs to tell yet.

So if you want help I ask you to open your very own topic and post all the information of you setup:

FOG version Init version Linux OS and version of your FOG server OS installed on the host you want to capture/deploy contents of d1.minimum.partitions of the particular image you want to deploy to a smaller size disk

@OmegaXis While I have not tried it myself I would think it’s not a big deal. Start reading up on bash scripting and start with simple scripts like this one:

#!/bin/bash # my installer script APT_GET_PATH=$(command -v apt-get) [[ -z $APT_GET_PATH && -x /usr/bin/apt-get ]] && APT_GET_PATH=/usr/bin/apt-get $APT_GET_PATH -y update $APT_GET_PATH -y install -o Dpkg::Options::=--force-confdef -o Dpkg::Options::=--force-confold name-of-new-package

Instead of name-of-new-package use the package you want to install.

@omegaxis said in Failed to get IP VIA DHCP:

I am able to pxe boot vm’s within the server just fine

when I try to boot a thin client that is attached to the same cisco catalyst 2960g switch, i am getting the dreaded failed to get ip error.

Meraki mx64 functioning as DHCP
Cisco Catalyst 3750-E as backbone
catalyst 2960g as endpoint switch where both the server and the computer I am trying to pxe are.

So lets think about what I’ve outlined. You can pxe boot a VM on the hypervisor just fine. But a physical machine attached to your 2960g can’t get ip error.

Is your meraki dhcp server issuing ip addresses to the VM, or is that coming from some other dhcp server? If you plug a windows computer into the 2060 does it get an IP address? Is the virtual switch where your FOG server is connected bridged to the physical network or is it Nat’d? (I don’t know unraid as a hypervisor to give directions to check) We may want to get a pcap (packet capture) of the pxe booting process to know what is really going on. We can/should use the fog server to capture its side and then a witness computer with wireshark to capture the virtual side. I have a tutorial on using the fog server to grab a pcap. https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue for wireshark you can use the capture filter of port 67 or port 68 if you don’t use a capture filter you can use a display filter of bootp. Capture both the what fog server sees and what the witness computer sees. My guess is the FOG server will not see the dhcp request.

Looking at the pcap you should see a typical DORA response.
Discovery (client sends)
Offer (server sends)
Request (client sends)
Ack (server sends)

If you look into the Offer packet, the dhcp server should set the {next-server} and {boot-file} fields in the ethernet header as well as dhcp options 66 and 67 in the options section. Both groups need to be there.

In my experience using a router or switch as a dhcp server does not give good luck because many do not handle the dhcp pxe boot settings well. Many for some reason will list the router/switch as the {next-server} even if they have a setting for a boot server. In this case you need the fog server IP configured in {next-server} and dhcp option 66.

@OmegaXis Strange error. Have never seen this before.