We use pfSense as the main firewalls coming into most of the companies we support. I work for an MSP. We've used different things. Our higher-end customers even run pfSense high availability clusters, and those work like a champ.
It has made deploying firewalls a faster process due to ease of configuration.
One of the features we use the most is the OpenVPN and IPsec VPN tunneling built within it. We have places that are headquarters and multiple locations where we create tunnels. We support police departments and stuff like that. Part of our use case is one of our police departments that does their own dispatching, so they have software that they run in-house. So we set their points out where the points themselves dial back in through OpenVPN using client certificates to create that always-on tunnel. Prior to us taking that over, they were using FortiGates, and the FortiGate FortiVPN was constantly dropping, and they were constantly having to re-authenticate. They would have to put 2FA back in. Since we've put in pfSense, we have the cradlepoints in cars establish the VPN connection, and we hardly ever hear from them since there seem to be no issues.
pfSense's flexibility is great. If you don't have the money to buy the NetGate hardware, anything works with it. You can toss it on any low-end piece of hardware or virtualize it if you choose to virtualize it. It is super flexible.
It's easy to add features to pfSense or configure them, especially if you're familiar with pfSense. They have a complete repository of apps that you can choose from and different types of monitoring packages you can put on it. They're all very, very straightforward and very easy to set up. I even run a pfSense for my home firewall. I've got AT&T fiber coming into my house. I bridge the public IP through, patch the modem into my pfSense, and have no issues whatsoever. I even run multiple VLANs off of it. I replaced a FortiGate with this setup.
The benefits are witnessed immediately after you deploy it. Immediately after you deploy it you're no longer having to read articles to figure out what flaw has been found in this version of FortOS or what flaw has been found in this version of SonicWall that's being run. You just you don't seem to have that in the pfSense platform.
pfSense provides with a customizable dashboard landing page. You can add widgets to show you any piece of information you want to see. I can add in a widget where, from the dashboard, it'll show me, what OpenVPN clients I have connected. It'll show me traffic graphs from LAN, optional ports, uptime, what version of BSD I'm on, what version of pfSense I'm on, whether there's an update available for PFSense, IP information, et cetera. It gives me all this within the main loading dashboard screen.
To manage multiple devices, you would have to subscribe to a third-party service to have the ability to do that.
This is truly set it and forget it. We didn't quite run into that as much with FortiGate. Even with the third-party add-ons, we don't seem to run into issues with the pfSense product where we have to be so hands-on.
There are two versions of pfSense, the community edition, which is free, and the paid version, Plus. We run both. We're getting more away from the community edition since we're starting to just purchase NetGate appliances. We're buying it strictly through NetGate. At this point, we're even starting to add on the tech support, which is top-notch.
pfSense can help to minimize downtime. You can set them up in a high-availability cluster, and that pretty much minimizes all downtime. Your secondary appliance picks up if your primary appliance goes down. It makes it really easy to apply updates or reboot the one firewall. It switches over so seamlessly. Your users never know the difference. When the primary firewall comes back up, it'll take over the primary function again, and then you can reboot your secondary firewall.
The visibility in pfSense enables us to make data-driven decisions. You can use traffic graphs and the historical data of those traffic graphs, especially if you're monitoring your WAN connection, to know whether you're oversaturating your line and whether you need to update your bandwidth coming into your building or not. That way, if you're seeing slowdowns on the internet, you can go back to your traffic graphs and figure out if you are seeing the slowdown from your provider or just oversaturating the line. If that's the case, I just need to call and order some more bandwidth.
As far as optimizing the performance goes, I like the fact that you can take interfaces within pfSense and put bandwidth limits on them. If I have a guest network, I can put a throttle limit on it to make sure that somebody doesn't hook to my guest and eat up so much bandwidth that my primary network can't function.
They're very affordable for what they offer. However, they should become more MSP-centric. They could design a centralized dashboard that I, as an MSP provider, can create sites and load my pfSense in there. That way, I can schedule updates to run after hours and things along those lines. They need to design for MSPs that are using their products and make centralized management easier.
I've been using pfSense for 20 years.
pfSense doesn't ever crash. If I had any gripe about these things, it's the fact that sometimes the update process will break the appliance. I'm not sure what causes it. I've had a few appliances where they've been running fine, and I go to apply an update, and then they just don't boot back normally. At that point, I reach out to support. They give me the reload file that I need. I reload the appliance. I dump the config back on it, and then it's good to go.
As long as you're buying an appliance that will support the bandwidth that you need to push through it, scalability is fine.We've got some of them running 10 to 12 VLANs. We've got one particular one that has no less than five different OpenVPN setups depending upon the department you're in.
Their paid support is top-notch.
With the community edition, and this probably is one of my gripes to pfSense, and this is more on the NetGate side, is that they don't make their images readily available to you. So you have to open a support ticket. You have to give them the hardware ID. You have to give them the serial number of the appliance, and then they will send you the file that you need to reload the operating system. Even so, we're talking about less than an hour of waiting time, and somebody will respond to the ticket and give you a link where you can download the software to reload it.
We've used SonicWall. We've used FortiGate. We always seem to go back to the Netgate and the PS pfSense just due to the fact being open source, they seem to have fewer security flaws in them than running something that is a closed proprietary system. With FortiGate, you constantly need to update, since they're constantly finding flaws in the FortiOS, and we just don't seem to have that from pfSense and the NetGate supply of products.
There was more hands-on work with FortiGate. If you're doing any type of web filtering, they would come out with an update where a website that did work would start getting miscategorized. And then all of a sudden, it would stop working. And you would have to go in and make a white list and an exception for it.
We buy the appliances and then install the appliances on our customer sites.
The initial deployment is easy. How long it takes depends on how simple or how complicated it is. As far as just a simple firewall goes, I can have one of them up and running in 15 to 20 minutes.
Even if you are not too knowledgeable, it would be very easy. When you first boot into it and go to the web interface, it has a wizard that walks you through setting the IP address on your LAN and configuring whether you're using DHCP or static on the LAN. That wizard that walks you right through what to do right out of the box.
Just one person is generally needed for deployment.
After the deployment, it's pretty much set it and forget it. I will go in and I will check quarterly if an update needs to be applied, however, they don't come up with updates that often. Maybe once a quarter, once every six months, an update has to be applied to the appliance. Other than that, I am only logging into these appliances if I need to make rule changes or if I need to bring up an additional VLAN in the network.
The licensing model is good. It's probably a little expensive for the hardware that you get. However, a part of that price is the support. And their support is top-notch. Even if you're only using the community support, and you're not paying for the extra support, they probably pad the hardware prices a little bit to help offset their support people.
I love the TCO (Total Cost of Ownership) of pfSense. That's one of our selling points to our customers. You can buy this, buy once, or, you can look at going to Meraki or FortiGate or something like that, but, be paying licensing fees every single year to keep that product up and running.
I'm an MSP.
I'd rate the solution ten out of ten.
If you're going with the NetGate appliance, I'd let new users know that they are already optimized for pfSense. If it's something that you're looking to virtualize or if you're looking to use a community edition on your own hardware, my recommendation would be just to make sure that you use Intel network cards. I have never had a problem out of an Intel NIC for getting the OpenBSD underlying platform to recognize those network cards and load the proper drivers for them. That way, they show up within the pfSense software.