UEFI PXE boot
-
@tesparza do you have the centos firewall on? I would think you would have imaging issues if it was enabled.
-
@george1421 it’s enabled, but has the exception specified in the wiki guided
-
@tesparza for the purpose of these testing please stop the centos firewall with
systemctl stop firewalldthen use tcpdump command. We need to see packets that would normally be dropped by the firewall. -
@george1421 said in UEFI PXE boot:
systemctl stop firewalld
https://drive.google.com/open?id=14zDpA9fW6P6qE4Xs6J5Cpgvw4ZClQUd6link to the capture
-
@tesparza Hint: look at the forum chat bubble for additional info
-
@george1421 [mod note: linked removed because it contained sensitive data - geo]
-
-
-
@tesparza Update: after the OP supplied a clean pcap and reviewing it, we’ve determined that the issue is with the dhcp server. The target computer is behaving exactly as it has been told.
So lets focus back onto your dhcp server can you post a screen shot of your dhcp vendor classes? (Hint: the free application GreenShot or the Windows clipping tool will give us a better resolution picture. I like greenshot because it gives you the tools to annotate the picture.)
Your vendor classes should look like mine.
The xscale entry is not necessary for almost 100% of the installations. Your vendor class fields must match exactly what I have under the description.
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
-
@george1421 Then in the policy for the scope in question (could also be a global scope, but make sure you don’t have any local overrides) your polices should be set up similar. Just be aware you will need one policy for each vendor class you setup. Here is an example of one.
On the conditions tab you setup what to match in the packet
Then on the options tab, you need to set dhcp option 67 to the boot file you need. In this case its ipxe.efi.
-
-
@tesparza Well OK that one looks perfect. What about the policy now? Will you post images from the tabs I referenced below?
-
-
@tesparza While this is a bit off point, the dhcp 66 options for each policy is a bit redundant since you are not changing the boot server based on each policy, you only need to change the boot file name.
-
-
-
@tesparza Well that’s disappointing, because you have it setup correctly.
So why is not the policy matching in the scope??
-
@george1421
thats the server options within the scope for this particular hall im in. -
@george1421 It worked the policy was disable on each scope and the secure boot on enable, just had to activate the policy and and disable secure boot
