HVN(4)

💖 hvn(4) from the Kernel Interfaces Manual: Hyper-V networking interface 💖

🌸 NAME 🌸

hvn — Hyper-V networking interface. That's the whole name, bestie, and it ate. 👑

✨ SYNOPSIS ✨

hvn* at vmbus?

That's it. No extra flags, no secret sauce — just this line. 🫶

🦋 DESCRIPTION 🦋

Okay so the hvn driver provides support for a Network Virtual Service Client (NetVSC), a virtual networking interface that relays device requests to the Virtual Service Provider (VSP) in the management operating system via the VMBus. literally the whole plot. 💅

NetVSC emulates an RNDIS 1.0 compliant device on top of a custom NVS protocol operating over the VMBus channel ring. custom protocol? over a ring? we love a niche vibe. 🌀

Individual networking interfaces can be renamed by issuing a Rename-VMNetworkAdapter PowerShell command in the management domain. 🏷️ And in order to enable sending and receiving of IEEE 802.1q (VLAN) frames, the virtual port needs to be put into Trunk mode with the Set-VMNetworkAdapterVlan command. Periodt. 🎀

🔥 SEE ALSO 🔥

• arp(4) — on the reading list, bestie
• netintro(4) — also on the reading list
• vlan(4) — yes, VLAN lore
• ifconfig(8) — the classic, you know it

🌈 HISTORY 🌈

The hvn driver first appeared in OpenBSD 6.1 and appeared in NetBSD 8.0. history was made, and we were all living for it. 💖

👑 AUTHORS 👑

The hvn driver was written by Mike Belopuhov <mikeb@openbsd.org> based on the FreeBSD driver by the Microsoft BSD Integration Services Team ⟨bsdic@microsoft.com⟩ and ported to NetBSD by NONAKA Kimihiro. respect the lineage, no cap. 🫶

footer vibe check: Debian • October 12, 2021 • HVN(4) — bye bestie, mwah 💋