I'm not a networking guy after all. The major shortcoming is the damn virtualized server that runs pfSense in a VM, so obviously, when it goes down, everything stops working. Also when I need to take the server down to do whatever, there's no internet. I do have a router a...
There aren't any special caveats for a virtualized host Source:WikiMedia Commons Most of the hard work is done when it comes to setting up pfSense for virtualization. You can now run pfSense effectively as you would on any other router or custom box. You'll want to configure one of your...
in a different way With their hardened traffic rules, firewall operating systems can add an extra layer of protection to all the devices on your LAN connection. Given how you’ll probably run your NAS 24/7, it makes sense to deploy a VM for pfSense, OpenWRT, OPNsense, or another ...
Interfaces (I hope this is what you mean) and rules attached. The tracert is from my PC on the 192.168.0.0 network. That network is connected via a switch but there are no Vlans at all. The DMZ is actually connected from the pfsense directly into a VM host which is hosting the serve...
I'm in a similar boat here and have been trying to figure this out for weeks. And no, I will not enable Hair-Pin NAT as pfSense (my gateway) has it off by default for security concerns (and I trust pfSense dev's to know good practices of such things). ...
Interfaces (I hope this is what you mean) and rules attached. The tracert is from my PC on the 192.168.0.0 network. That network is connected via a switch but there are no Vlans at all. The DMZ is actually connected from the pfsense directly into a VM host which is hosting the serve...