![]() I was unable to utilize this Intel I350 NIC Port as a direct PCI Passthrough WAN port for my testing purposes. However, due to issues with either the NIC, FreeBSD, OPNSense, or Kernel Drivers. Once this was done, the NIC appeared in OPNSense Console immediately and on reboot. $locationPath = (Get-PnpDeviceProperty -KeyName DEVPKEY_Device_LocationPaths -InstanceId $dev).Dataĭismount-VmHostAssignableDevice -LocationPath $locationPath -Force -VerboseĪdd-VMAssignableDevice -VM $vm -LocationPath $locationPath -Verbose ^^^ CAN BE FOUND IN DEVICE MANAGER - PROPERTIES - DETAILS - DEVICE INSTANCE PATH PROPERTY - # = omitted information for privacy (just in case)ĭisable-PnpDevice -InstanceId $dev -Confirm:$false The entered Windows Server 2016 PowerShell commands were the following: ![]() Using that guide as a base and making modifications. I used this as a guide, so I don't take credit for the base script: The hardware must be assigned to the virtual machine for it to be used." The virtual machine will require the appropriate driver to use the exposed hardware. Common devices are network cards, graphics cards, and special storage devices. "With Windows Server 2016 administrators can pass through PCI Express devices via the Discrete Device Assignment mechanism. However, I am not entirely sure and maybe someone can chime in with ideas.įreeBSD 11.1 fully supports this type of PCI Passthrough/DDA on a Windows Server 2016+ Host OS w/Hyper-V: I tried to do it this evening, but not without an error which may be driver related. Great for things like VLANs, intrusion detection and other plug-ins of that nature better suited with real NIC access. Which should treat OPNSense as if it was running on a metal box vs dealing with the Host Windows OS and Virtual Switch. ![]() I was just wondering if anyone has attempted setting up OPNSense using real PCI Express passthrough of the NIC, to bypass the software virtual switch in Hyper-V environments.
0 Comments
Leave a Reply. |