summaryrefslogtreecommitdiff
path: root/sys/dev
diff options
context:
space:
mode:
authorMike Belopuhov <mikeb@cvs.openbsd.org>2016-10-06 15:40:21 +0000
committerMike Belopuhov <mikeb@cvs.openbsd.org>2016-10-06 15:40:21 +0000
commit401c6594aa8e09de76f948f1c16d75578c0c20d6 (patch)
tree0f845ed834e24f63b5762c9c5fd9abcd5e3e5a93 /sys/dev
parentd86ecc4963a794a41e1264be84544f49cd369fe3 (diff)
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.
Diffstat (limited to 'sys/dev')
-rw-r--r--sys/dev/pv/if_hvn.c2
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
}