Squirrel_CA

Managed to get it working last night. My main issue was that I would get PFSense working but then I could not access Unraid from my laptop while on the network, so I would have internet access but 192.168.1.2 (Unraid) would not be reachable. I would have to manage it directly from the server itself with a monitor, keyboard and mouse plugged into the server. Ok so my issue was that my HP 4 port switch shows all 4 ports as the same ID. Therefor I cannot pass all 4 though to PFSense as individual ports (PFSense sees all 4 as just one port, even though I separated all 4 into separate IOMMU groups). Because of this I had to add 2 more pcie 1G ethernet ports (1x for WAN and 1x for LAN). First to get the 4 port onboard network card to work on PFSense, you need to set bridge to true on the port you going to use for PFSense (in my case eth0 bridge set to yes). Next you need to statically assign an I.P to this port. I.E 192.168.1.2. (Note that this will only show up as 1 port on PFSense. You can just bond all 4 ports in Unraid if you like for better throughput. Will need to bond the ports on the switch side too or else the ports will not be accessible *Supported switch will be required to do this*) So now on PFSense Console it looked something like this: Virtio (this is the bridge port on Unraid "eth0") re0 (WAN) re1 (LAN) I then set re0 as WAN and re1 as LAN and Virtio as Optional1 (Opt1) Next I went to "Interfaces" on PFSense and added a new interface and set a static I.P address, set DNS to PFSense I.P and clicked on Done. (Just to be safe I statically assigned Virtio to 192.168.1.2 DHCP leases too. Its fairly easy. Click on the + sign on the right hand side of any lease, it will open a new window and auto fill that leases MAC address. Now delete that MAC address and add Virtio MAC address and click on done. (services - DHCP Server - Leases). To do this, check the MAC address assigned to Virtio (can be done by clicking on Settings in Unraid - Network settings, and then scrolling down right to the bottom and there will be a list of all interfaces with MAC addresses. Alternatively should be able to see it by clicking on Edit on the PFSense VM in Unraid and going to the network section at the bottom). Now I have Network connection on the network and I am able to manage Unraid as well from the network. I will see if I can EDIT this post when I get home tonight and add screenshots of my config to help anyone in the future. I ran out of time last night, ended up coming right at 1am. EDIT: OH and if at anypoint during this process, you get an error when trying to start your PFSense VM that says: Just open the console in Unraid(top right hand side) and enter the following: This will sort it out for you.

I was having a similar issue with my Virtio port showing down. You can fix this by clicking on the Shell icon on the top right, then typing this in: virsh net-start default That brought my interfaces up. Now I just need to get access to Unraid from the virtio network. I am using a PCI ethernet adapter as my WAN interface and then I want to use the Virtio-net interface for my LAN interface. So I will be troubleshooting this tonight. I started working on this last night at 7pm and went to bed at 2am this morning. I am running a HP Proliant DL380p G8 , I tried splitting up the 4 port NIC using ACS but unfortunately for what ever reason, all 4 ports have the same serial, so even if I split them into separate IOMMU groups, restart, then add each port individually to PFSense, when PFSense starts up, it just shows up as one port. EDIT: Just to be clear, my Virtio-net is using my servers 4 port network card, the one I mentioned above: HP 4-port 684208-B21 Ethernet 1Gb 331FLR Adapter The issue I have is that PFSense is a VM, so when Unraid is rebooted, PFSense starts after Unraid (Obviously), but due to this, Unraid marks the NICS as "Shutdown-inactive" because nothing is currently using the ports, this causes a chain effect, where PFSense looses connectivity to that port now when the VM auto starts because Unraid has turned that port off. I have to manually start the port, then reboot PFSense to see the port then redo the interface assignments again. I might be doing something wrong, I will tackle this again tonight when I get home. EDIT: I will document my steps and post my config if I manage to come right tonight.

THANK YOU SO MUCH! This was exactly what I was looking for. Moving over from vSphere 7, I needed to expose 2 ports for my PFsense. Now I am confident that I will be able to accomplish what I need.