@billsecond said in PfSense + Hyper-V + VLANs: Get-VMNetworkAdapter -VMName "lab1-pfsense" | Set-VMNetworkAdapterVlan -Trunk -AllowedVlanIdList "1-2048" -NativeVlanId 90 Hi, please any one can help me to reverse this command? I mess up my connection with these powershell: Get-VMNetworkAdapter -VMName "PfSense-home" | Set-VMNetworkAdapterVlan -Trunk -AllowedVlanIdList "1-2048" -NativeVlanId 1030 PS C:\Windows\system32> Get-VMNetworkAdapter -VMName "PfSense-home" | Set-VMNetworkAdapterVlan -Trunk -AllowedVlanIdList "1-2048" -NativeVlanId 1031 PS C:\Windows\system32> Get-VMNetworkAdapter -VMName "PfSense-home" | Set-VMNetworkAdapterVlan -Trunk -AllowedVlanIdList "1-2048" -NativeVlanId 1032 PS C:\Windows\system32> Get-VMNetworkAdapter -VMName "PfSense-home" | Set-VMNetworkAdapterVlan -Trunk -AllowedVlanIdList "1-2048" -NativeVlanId 1033

After RTFM I was able to stop the Intel i40en driver from disabling trusted mode on the virtual functions on every reboot, but that didn't resolve the error message. The good news is now the firewall doesn't come up from a boot in a broken state every time, but this confirms the AQ returned error VIRTCHNL_ERR_PARAM to our request CONFIG_RSS_KEY! error is unrelated to the i40en driver's handling of trusted mode. Anyone else have any brilliant ideas for what could be causing the error message? Anyone have any guess as to whether it can safely be ignored? It doesn't stop pfSense from passing traffic on the NIC so it seems to "work," but God forbid it's creating some sort of security vulnerability!

I think the thread was posted in the wrong category. @mods could you please move the thread to the right category? I think installing pfsense or so would be the right?

@pfsense2023 In top it shows high interrupt [image: 1712387749317-fcff96ff-3aae-46e4-bb8d-4a36c88e9f7a-image.png]

@faraguti glad you sorted it. Such thing often take longer than they would with the aid of hind sight.

@eiger3970-0 Solved.

@skveen Your the very first that shows me a system with more RAM as (hard/SSD°VM) disk space ... I've never seen that before. Why insisting with such very small disks ? Does pfSense even fit on a 1 GBytes drive, leaving close to no free space available ? Not even talking about swap space, which is 'normally' twice the RAM size .... edit : Google told me you should read this : PfSense Hyper-V .vhdx growing like crazy

@Sergei_Shablovsky said in pfSense 23.09 Intel QAT 4xxx passthrough question: Right now on USA eBay (where PP able to make chargeback, opposite to many DOA from Chinas sellers) QAT8950 cost USD$50-80 I bought mine over a year ago from a Chinese seller for $37, in fact I bought two because at that price each, why not, while at the time, the QAT 8970 by US sellers priced at $800+ So, priced had fallen...that's good. Both mine are installed in work stations, a Lenovo and a Dell...see sig.

@SolPain A WAN address is usual DHCP. I guess you want to place pfSense behind Express VPN, so it would be one of 10.184.16.x and you need to select another subnet for pfSense LAN and AD.

Is it a fair assumption that pfSense does not support SRV-IO passthrough? It seems like it used to work. Just wondering if I should continue the effort or give up.

@viragomann Duh, 'obviously'! Well, thanks, now the Debian KVM can ping the WAN via the KVM router.

@elcalzado said in Can't get VLANs to work in pfsense on proxmox: Would I create a Linux VLAN in proxmox and call it vmbr2.16 for example? If so would I then go into pfsense and delete my vlan interface I made in there? Or, would I pass in another vmbr2 w tag 16 into the vm and use that as the interface for vlan 16? All you have to do is to enter the VLAN ID in the virtual NIC settings for pfSense like this: [image: 1710006334840-5efdfd91-4431-4cd5-861d-5de3e4c4b44d-grafik.png] You can do this all in the Proxmox GUI. In your case it will be 16 for this one. For the next VLAN add an additional network device and state the respective VLAN ID. In pfSense you would have to remove the VLANs and configure conventional interfaces. Also do I need to give the Linux VLAN a default gateway, ip, etc? No. This settings are for Proxmox only and would give it an IP. Just check "VLAN aware" in the bridge settings.

@aarcane Did you ever find a solution to this problem? I've reproduced it on pfSense 2.7.2 and Proxmox 8.1.4.

@eiger3970-0 Fixed, LAN cable was in, but needed an extra push. Must have been bumped when I removed and added a new USB device.

@DD check this link from redmine, is working for us. Redmine History

@penne Looks well. Did you disable hardware checksum offloading?