Ce site est optimisé pour être consulté depuis un navigateur moderne dans lequel JavaScript est activé.

Envoyer du texte directement à une VM dans Hyper-V 2012

ayi

I’m setting up OpenBSD as a VM in HyperV 2012. It would be easier for me to just create one interface on the vm and have OpenBSD take care of setting up the vlans.
Is it possible to tell HyperV to send all traffic to a port whether it’s tagged or not?
If I uncheck the “Enable virtual LAN identification” it looks like HyperV is only sending untagged traffic to the port.
<hr>
Source : <a href="http://technet.microsoft.com/en-us/library/hh848475.aspx" rel="noopener nofollow ugc">Server Fault</a>

ayi_2

Using the PowerShell <a href="http://technet.microsoft.com/en-us/library/hh848475.aspx"><code>Set-VMNetworkAdapterVlan</code></a> cmdlet, you can turn on trunk mode on the virtual NIC. I don’t think there is an equivalent GUI option for this.
<pre><code class="lang-auto">Set-VMNetworkAdapterVlan -Trunk -AllowedVlanIdList "100,101" -VMName "VmName" -VMNetworkAdapterName "TrunkNic" -NativeVlanId 1

</code></pre>
<ul>
<li>
<code>-Trunk</code> turns on trunk mode, which leaves the VLAN tags intact.
</li>
<li>
<code>-AllowedVlanIdList</code> specifies which VLAN’s to allow the guest to use. This parameter is mandatory in trunk mode. If you have a largeish number of VLANs, you also can use ranges like <code>-AllowedVlanIdList "1-4000"</code>
</li>
<li>
<code>-NativeVlanId</code> is required, too. It specifies which VLAN outgoing untagged packets belong to. I think that it also has strips off the VLAN tag for incoming packets on that VLAN. Or something like that. I remember that there was a weird behavior here that I completely sidestepped by just setting this to an unused, blackholed VLAN and not using the untagged interface in the guest, because that was easier to configure and seemed less fragile to me.
</li>
</ul>