Posts made by Gribbly

@george1421 Thank you! Please let me know if you need any more info or for me to test anything here!

@george1421

Yes sir, i’m using VLAN_ID 2223 here.

I am able to load the Ubuntu Installer Kernel, which has VLAN support. Using the Expert configuration, it gives me the ability to configure a VLAN ID.

@george1421

Thank you for your time. This is what my conclusion had been - apologies if I wasn’t clear with what I was trying to get across!

I’ll go back to my pxe ubuntu install - which I am able to get working, but obviously without the benefit of just imaging!

@george1421

The machine I am trying to image is on a trunk port. I am using ubuntu there. The fog server is natively in the vlan no trunking.

Effectively this is what happens:

BIOS -> Allows me to configure a VLAN TAG for PXE.
Machine boots, PXE gets a DHCP address from the configured trunk port - using the configured VLAN TAG, and downloads the kernel.
The kernel loads and attempts to grab a DHCP address. It does this without the VLAN TAG.
As the blade only has access via a trunk port, it fails to get the DHCP at this point and is unable to continue accessing the FOG server.

@george1421

In this example, the target machine is a blade in a chassis. The network which I need to communicate with my fog server from is tagged (on VLAN ID 2223) to the host, not native/untagged.

My BIOS allows me to configure a VLAN ID for the PXE boot. The machine boots, PXE grabs an IP address via the tagged VLAN, and downloads the undionly.kpxe kernel. This is then attempting to get an IP address via DHCP on eth0 and failing, so unable to continue the communication with the Fog server. Ideally, I would like it to be using eth0.2223 (VLAN 2223 on the eth0 interface).

Hi,

I have an environment where I do not have the ability to configure a native VLAN.

I have the ability to configure a VLAN for PXE in the BIOS, which is working correctly, but I am struggling to see if it’s possible to then have the system continue to use that VLAN ID for imaging etc. It is failing currently to get an IP as I believe it’s dropping back to native vlan once it’s pulled the ‘udionly.kpxe’ loader.

Any hints/kernel options etc would be appreciated - or a ‘no, this isn’t possible’.