PXE Boot to different VLAN
Having and issue where the fog server is not seeing any pxe devices outside of the management vlan.
Have server on Server Management vlan 340 (10.141.0.0/24) and the pxe machines are on vlan 306 (10.136.6.0/23).
Any reason why the pc is not seeing the server?
@Technolust FWIW, since you have a Windows 2012 DHCP server you might want to look over this wiki page if you need to support both uefi and bios systems in your environment: https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence#Using_Windows_Server_2012_.28R1_and_later.29_DHCP_Policy
@Sebastian-Roth Hey Sebastion-Roth, Looks like only the legacy option was selected in the BIOS and in the DHCP options I have it set for UEFI only including 32bit and 64 but I did not allow the unidonly option. I made them change the bios to UEFI and Legacy. Also they had SecureBoot enabled so we disabled that and we are up and running.
Hope that helps for future users.
@Technolust Ok, please let us know if you need further help or how you solved the issue (might be helpful for others reading in the forums!)…
@astrugatch Yeah the dhcp option for both vlans are configured. If you are referring to option 66 & 67 along with the vendor classes.
@Technolust I don’t think bios setting has any impact on if the target computer works on one vlan or the other. PXE booting or not, maybe but not vlan reference. I would tend to think you don’t have the dhcp options 66 and 67 published on vlan 306.
If you still can’t get it to work, we’ll have you use wireshark on a computer on the same subnet as the pxe booting computer to capture what the target computer is being told. For wireshark use the capture filter of
port 67 or port 68to only collect dhcp pxe boot information. What we will be interested in is the one or more dhcp offer packets. But we can cross that bridge if necessary.
@Sebastian-Roth I think we figured out the issue but to clarify. We are running Windows 2012 R2 DHCP server and the routes allow the subnets to see each other as trunks. I think the issue had to do with the BIOS configs and not the vlan communication.
@Technolust Do you use DHCP-relay/ip-helpers or anything similar to forward DHCP broadcast which don’t usually go beyond a subnet!?
astrugatch last edited by
Have you configured your DHCP options in your DHCP server for the 340 VLAN scope?