aboutsummaryrefslogtreecommitdiffstats
path: root/contrib
diff options
context:
space:
mode:
authorMichael Brown <mcb30@ipxe.org>2022-12-13 14:45:44 +0000
committerMichael Brown <mcb30@ipxe.org>2022-12-14 11:51:52 +0000
commitd879c8e4d9f3b00c09a7d199a2681705fc5b55d0 (patch)
tree03fa45c25742b4f605d9391c776146331b040f11 /contrib
parent5e62b4bc6c7bd7c6929b3fe540fb1ba8744fd16c (diff)
downloadipxe-d879c8e4d9f3b00c09a7d199a2681705fc5b55d0.tar.gz
[efi] Provide VLAN configuration protocol
UEFI implements VLAN support within the Managed Network Protocol (MNP) driver, which may create child VLAN devices automatically based on stored UEFI variables. These child devices do not themselves provide a raw-packet interface via EFI_SIMPLE_NETWORK_PROTOCOL, and may be consumed only via the EFI_MANAGED_NETWORK_PROTOCOL interface. The device paths constructed for these child devices may conflict with those for the EFI_SIMPLE_NETWORK_PROTOCOL instances that iPXE attempts to install for its own VLAN devices. The upshot is that creating an iPXE VLAN device (e.g. via the "vcreate" command) will fail if the UEFI Managed Network Protocol has already created a device for the same VLAN tag. Fix by providing our own EFI_VLAN_CONFIG_PROTOCOL instance on the same device handle as EFI_SIMPLE_NETWORK_PROTOCOL. This causes the MNP driver to treat iPXE's device as supporting hardware VLAN offload, and it will therefore not attempt to install its own instance of the protocol. Signed-off-by: Michael Brown <mcb30@ipxe.org>
Diffstat (limited to 'contrib')
0 files changed, 0 insertions, 0 deletions