1.\" $NetBSD: hvn.4,v 1.2 2021/10/12 07:43:41 wiz Exp $ 2.\" 3.\" $OpenBSD: hvn.4,v 1.5 2016/10/07 14:42:27 jmc Exp $ 4.\" 5.\" Copyright (c) 2016 Mike Belopuhov 6.\" 7.\" Permission to use, copy, modify, and distribute this software for any 8.\" purpose with or without fee is hereby granted, provided that the above 9.\" copyright notice and this permission notice appear in all copies. 10.\" 11.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES 12.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF 13.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR 14.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES 15.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN 16.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF 17.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. 18.\" 19.Dd October 12, 2021 20.Dt HVN 4 21.Os 22.Sh NAME 23.Nm hvn 24.Nd Hyper-V networking interface 25.Sh SYNOPSIS 26.Cd "hvn* at vmbus?" 27.Sh DESCRIPTION 28The 29.Nm 30driver provides support for a Network Virtual Service Client (NetVSC), 31a virtual networking interface that relays device requests to the Virtual 32Service Provider (VSP) in the management operating system via the VMBus. 33.Pp 34NetVSC emulates an RNDIS 1.0 compliant device on top of a custom NVS 35protocol operating over the VMBus channel ring. 36.Pp 37Individual networking interfaces can be renamed by issuing a 38.Cm Rename-VMNetworkAdapter 39PowerShell command in the management domain. 40In order to enable sending and receiving of IEEE 802.1q (VLAN) frames, 41the virtual port needs to be put into 42.Em Trunk 43mode with the 44.Cm Set-VMNetworkAdapterVlan 45command. 46.Sh SEE ALSO 47.Xr arp 4 , 48.Xr netintro 4 , 49.Xr vlan 4 , 50.Xr ifconfig 8 51.Sh HISTORY 52The 53.Nm 54driver first appeared in 55.Ox 6.1 56and appeared in 57.Nx 8.0 . 58.Sh AUTHORS 59The 60.Nm 61driver was written by 62.An Mike Belopuhov Aq Mt mikeb@openbsd.org 63based on the 64.Fx 65driver by the Microsoft BSD Integration Services Team 66.Aq Mt bsdic@microsoft.com 67and ported to 68.Nx 69by 70.An NONAKA Kimihiro . 71