diff options
| author |   mikeb <mikeb@openbsd.org> | 2016-10-06 15:40:20 +0000 |
|---|---|---|
| committer | mikeb <mikeb@openbsd.org> | 2016-10-06 15:40:20 +0000 |
| commit | 31d4d78ae63a2094b71c265cd372cfb26794a2ba (patch) | |
| tree | 3e74a81631cb997be8cf637446397a462338badd | |
| parent | Build kernels as root for now. Otherwise we run into permission issues (diff) | |
| download | wireguard-openbsd-31d4d78ae63a2094b71c265cd372cfb26794a2ba.tar.xz wireguard-openbsd-31d4d78ae63a2094b71c265cd372cfb26794a2ba.zip | |
Enable hardware VLAN tagging
Turns out that hardware VLAN tagging is required to use VLANs at all
(while QinQ VLANs are not filtered regardless...). On top of that a
PowerShell command needs to be executed to configure Trunk mode on
virtual interfaces. An example of such command is:
Set-VMNetworkAdapterVlan -VMName OpenBSD -Trunk \
-AllowedVlanIdList 10-100 -NativeVlanId 5
This will enable trunking mode on all hvn(4) interfaces. An option
-VMNetworkAdapterName can be passed to turn trunking on one interface,
and although by default all networking interfaces have the same name
"Network Adapter", a "Rename-VMNetworkAdapter" command can be used
to rename them one by one.
| -rw-r--r-- | sys/dev/pv/if_hvn.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/sys/dev/pv/if_hvn.c b/sys/dev/pv/if_hvn.c index 801ac5b15e4..ecd8703c529 100644 --- a/sys/dev/pv/if_hvn.c +++ b/sys/dev/pv/if_hvn.c @@ -278,7 +278,7 @@ hvn_attach(struct device *parent, struct device *self, void *aux) if (sc->sc_proto >= HVN_NVS_PROTO_VERSION_2) { ifp->if_hardmtu = HVN_MAXMTU; -#if NVLAN > 0 && notyet +#if NVLAN > 0 ifp->if_capabilities |= IFCAP_VLAN_HWTAGGING | IFCAP_VLAN_MTU; #endif } |