pfsense VS OPNSense

tommy here from lauren systems we're going to talk about a popular topic i say popular but it's really someone asking in the youtube comments so persistently they wore me down and had me do a video on it but i think there's some real reasons i should cover this it is the open sense versus pf sense debate it comes up a lot specifically as i said on youtube occasionally on twitter and of course there's two places on reddit one for psense one for open sense and i think there's some ping ponging back and forth between homeland people of who makes the best firewall and why their answer is the best now i'm gonna weigh in on this and i will at least let people know as if you didn't already that we are a long time user of pfsense and don't plan on right now here in may of 2021 changing that i bring that up because time matters when it comes to context of whether or not we like a product there's products i don't like from the past but i'd like them then and right now i still like pfsense that's still my position on things we still plan to keep deploying and using it but that's right now if you catch me 10 years from now because this thing changed hey why not this is why we have dates on videos and this is the experience in may of 2021. before we dive into this and all the details which will of course be linked down below so you can just skip ahead to the time index that interests you the most if that's what you'd like to do let's talk about the sponsor of today's video me if you'd like to learn more about me or my company head over to lawrences.com i'd like to hire your project there's a hire us button right at the top if you'd like to support this channel in other ways there's affiliate links down below to get you deals and discounts on products and services we talk about and other ways to connect with us except you won't find an affiliate link to netgate or pfsense we are not a reseller we're also not a reseller of open sense but that was probably obvious by anyone who's followed this channel for any length of time because we don't really do open sense videos but not being a reseller is one of our ways we've always kept a separation and just wasn't lucrative for us to become a reseller matter of fact by telling people and this is frequently for a lot of the products that are not channel partner we tell people go ahead and buy the product directly from you know xyz company or in this case if you want to buy a netgate appliance and our task is frequently to integrate not just the psn firewall or do consulting with it but usually an overall network stack it's a lot of what we do is build and engineer these things for companies for internal it teams and even for small businesses or even people building different you know labs and things like that we offer a range of consulting services and pfsense has been one of the things that we consult on but we have done consulting on opensense as well but not being a reseller i just want to be up front so this is not paid for endorsed by either those companies i sponsor this video and the video is my own thoughts now the first thing we'll talk about though is the common ancestor of pf sense and open sense which is mono wall in the early days in the before times and the earliest times of technology as it feels because it was so many years ago now and technology iterates fast there was a move towards some of these different types of open source firewalls or just basically completely softer to find firewalls using old hardware there was actually a lot of competitors in the early market for this in the 2000s and maybe one day i'll dive into the history of all them because it might be really fun but mono wall was among those and model wall was a really cool project based on bsd versus a lot of the other ones at the time were based on linux there's some cool features that bsd had ahead of linux back then for large scalable systems so you've seen a lot of enterprise use of this because it could do things the other systems couldn't and they could do it without some of the you know hardware and licensing that came with some of the enterprise offerings of that time swing it all the way now most firewalls are more software defined than they are hardware defined but not to get too off topic on that but it's it's changed a lot in the market over the last 20 years but monowall is defunct pf sense was the fork of that code that took over the project to carry it on then comes open sense who like all things in open source when a group of developers can't agree on something fork it man just fork it and this is what happened in 2014. i think the first original release was 2015. so there's obviously some arguing that went back and forth this is how these go i'm not going to dive into it but i'm sure there's forum post people can watch and developers argue and have different opinions but the fork why did they fork let's read their words right here from the open sense page which is back in 2014 after having sponsored pf sense for years we felt there was no other option than to fork the project to keep the spirit of the original monowall-based fork alive below you can read about the original motivations and the birth of open sense so they you know cover this here one of the reasons though that is kind of funny and these are some of the arguments and there is some validity to this of saying hey the gui should not perform tasks that require route access and that's something they were going to fix so this is back in like 2015 but here we are and i have both of these open sense we'll get to the interfaces shortly here uh but i have both open sense and pf sense virtualize so we can talk about this uh but right here is logged into opensense and everything's still running is root you can go through their code commits and read they say it's because they brought over so much legacy code it's one of those things like i get the goal like hey we want to separate things and do things differently but it ended up that they still haven't really changed over from that seven years later and i just want to bring this up because this is where the comments come in when i do a pf sense video but i want to address it it's not that they are more or less secure they're much the same because they're still running things the way pf sense did the way psn still does now and that's just because it's really difficult to write it in a different manner the other thing we want to talk about is their choice of hardened bsd versus your standard freebsd this is another talking point that people think make open sense substantially different than pfsense and while they're still based on it right now they are parting ways and moving away from it as of april of 2021 but i wanted to bring this up because there are differences and it's not a bad thing that they were using that but it just comes down to implementation this is where it gets a little bit more nuanced both projects are secure both projects have good track history of security so whether they implement it as pfsense has done with standard bsd and then apply their own compilation tweaks to it and you know fine tune things or you start with the patches from hardened bsd they are different approaches but they both have achieved in both products i can't name any major security breaches now there's always security fixes and a lot of security fixes came from the underlying tools and open source things that they integrated in there you know for example there was a problem with unbound at one point in time and both projects were using it but the way it was compiled means it was not something that was immediately exposed or a default config that could have been a problem matter of fact i believe it was the way it handled some of the dns sectors a while ago but this is just an example but both projects because they are based on a lot of the same bsd packages that type of security problem still occurred but both of them because of the mitigations they have didn't really have any problems directly from it so this is where there's a little bit of nuance and you know it's a bold statement but it actually in reality as long as you're implementing it properly and writing secure code is hard as long as you're doing that all properly yes it should work great now on to the controversial topic that i'm going to spend a little bit of time on because you know flame wars have nothing to do with technology but boy do people love them and let's talk about that and i'm only going to talk about it briefly because what happened was you have the fork of open sense now i think there's always more to the story that we just don't have the full context for of everything that happened we can see externally what did happen in the court of law because there's published papers on this the folks over at or specifically i believe his name is jim over at uh decate did typo not typo squad domain squad it's not really a typo they had opensense.org he registered opensense.com and squatted on it essentially saying open sense sucks childish behavior i don't condone this at all i think that's uh yeah that's just childish but uh not as an excuse i am once again being very clear i don't condone this behavior i think people make mistakes i think people make horrible choices this was one of them and the case was ruled against them and they had to surrender domain back over to open sense and the reason i think we're missing some of the nuance there is netgate is the foundation that sells hardware that funds the developers that develop pf sense and that hardware funding you know people say why does the netgate product cost x well that extra money over the actual cost of the physical product that goes into software development is what gets you the pfsense software and what gets all the other things that netgate sponsors and that's one of those little nuances that shouldn't be glossed over too much that netgate spends a lot of money sponsoring and paying some of these developers to develop the bsd kernel and other open source projects i just know this because i know some of the people that are you know working there or working on the payroll that work on bsd contributions i know there's a lot of people that you know all the software should be free but the reality is it still takes very skilled developers to write this and someone has to pay their bills it turns out their computer isn't free their electric bill and utilities aren't free so they may have some free time but they still have to eat and they still have to buy the technology that they type on to write the code so there has to be money somewhere or it becomes a hobby project and unfortunately when some projects are less supported they well fall by the wayside and lack features and bsd is an ecosystem that is substantially smaller than the linux the linux world is very much propped up by many commercial enterprises you know google and red hat and ibm and all these other companies do massive contributions that end up in the kernel end up everywhere else on linux the bsd community is a lot smaller with a fewer number of developers and the two biggest projects i can think of well three i guess if you count netflix uh who does use bsd under back end but you have ix systems and the pf sense and of course open sense and those are the big projects that are on the bsd front everything else and i know there'll at least be one or two comments but isn't it system starting truenass scale which is also based on debian yeah so they're going to have uh you know development on both sides but back to the point bst development costs money and netgate is contributing to it i don't really know or at least i couldn't find i'm not saying open sense isn't i just couldn't really find it but they are both backed by hardware company because by the way openses has another hardware company i don't know how to say it it's des ico but they sell appliances that fund the development of open sense so there's a very similar uh business model that both of these have and here we go high quality dutch engineering and we don't really run into many of these over here in the us but i believe my thoughts would be they're probably more popular in europe because being that it's based over there um i've had people complain that there's you know because i'm not expert on this point you import some of the devices from the us over there there's a lot of fees that may get added on to it versus things you buy directly in the eu but that's a certainly outside of what i do every day but they do like i said have some more business models on there all right now back to finalizing this they surrender the domain over and open sense.opensense.com and everyone loves to complain about this controversy i i think it's something that they regret doing but hey take it for what it's worth i'm willing to move on forgive when someone makes a horrible mistake because if i hated every software where someone was just an ass that's all i can say i would probably not use any software at all software development is peppered with people who are less than good behavior but hopefully regret it grew up and became more adult later all right moving on to some technical topics and i do consider this somewhat of a technical topic and it it's just kind of where my leanings are for uh pf sense it's a job search i know job search doesn't sell you technical topic but hear me out technical people using pfsense i have covered this before and there's something that i'm under nda for that i can't talk about which is the large companies that have hired us to help integrate pfsense with some of their other systems the same thing with netgate many companies when they buy products they don't want you to know what product stack they're using they don't disclose that all the time this is why when you look at some of the larger companies you're becoming quieter and quieter about the technology because from a security standpoint this reduces threat surface because if you know that a company is running any particular stack and then you know there's a flaw in that stack now you have a vector of attack to potentially go after that company because you're like hey cool there's a flaw in this product and we know the target that we're looking for uses that product this can be one of the reasons like they obscure it but i bring that up the way you can sometimes find out what stacks companies are using is by looking at the job postings and when you look at the job postings i put in open sense over here indeed which i think is probably more focused on the us maybe there's a way i could look in europe and it would be a little bit different but i don't see many of these open sense systems uh operations people being hired matter of fact i find it interesting i think that um there's just it's more like mention like do you know some of the open sense stuff in here and there's like a little bit in here but when you look at the job offerings for pf cents there's 58 job listings for people looking for pf cents and i bring this up because one we've run into it in the wild very frequently like we've taken over you know random client that needed it helper they lost their i.t admin and they need someone to take over and we'll find apfsense device in there or software defined or however they've got it loaded whether they bought it from netgate or virtualized or anything else in between that is very very common we run into these data centers we have just been in them and noticed hey look a neck gate a neck gate a neck gate they're really common in there when we're at colo locations i've seen a lot of them out there i just have never seen anything from open sense and like i said maybe because they're more european but this is also where my start came from in using pf senses at a bank in around 2014 or 15 uh was a banking system and we were surprised to learn that their system had it which was a little bit of consulting that was going on back then and uh like i said we've run into it a while constantly and you know we just see a lot more for it so it's one of the reasons that you know i'm so well versed in it and uh yeah that's kind of the same thing going for the job thing now that is not a reason not to use open sense but it's just a you know my perspective of how much we run into it and one of the reasons we stay kind of focused on it so now we can get into the actual technical topics and looking at the interfaces because i notice what a lot of people want to do is talk about what makes it really different and what makes it really different is this dashboard that looks different here than it does here right well this is where the nuance is and this is where a lot of engineering went into open sense to change things the big change is the interface it's a lot different the underlying technology is the same this is one of the reasons that they're both solid solutions for firewalls is because they're still based on bsd they're still based on a lot of the same core functionality at the bottom but how you address and how you get to that functionality is where the nuances start coming in so the dashboards do look a little bit different but also look kind of the same in some ways when you start at the dashboard so if we started the dashboard here uh we know when lan services and go over here very very similar now let's look at something like the firewall and nat rules if we go over here or we can go over here this is part of the experience you get we can go to firewall and uh or we can even type in nat and uh cool now pfsense no such universal search bar this is where if you're starting from ground zero and you've never used one of these before either one of these devices there may be where you find the open sense a little bit easier because you can just use the universal search without having to go through the menus such as firewall nat now that is one of those things that's just going to be different so actually let's start with this rule here let's look at the wan role because i have a very similar rule in both and uh it's the open up to the outside world rule and this is the allow firewall rule let's edit this one and actually we'll go here and go to rules we'll go to wan and then here's our you know what allows me to remotely access this on the outside of both of these networks action pass we have the option to disable the rule interface direction in protocol and let's actually go show hide the advanced options there's just all these features here you know tcp flags and things like that scroll down interface address protocol disable the rule source destination logging display advanced tcp flags they both have tagging so we have the tag options right here tagging is actually a pretty cool feature where you can tag a rule to then have it processed by a second rule essentially chaining rules together but there's just some neat stuff that's in here that both of them have because other than a slight interface design when it comes to writing out the rules they're very similar and much the same the only thing that becomes a little bit different and i haven't researched how they handle it but they do handle it is like how they do the qos it's done a little bit differently because you can do your qos and out pipes uh and queues here for things but overall like i said other than slight implementation differences they're very very similar now let's go back over to nat rule because this is where they did diverge a bit and here is the remote access to a system behind it and we'll edit this rule this was confusing and they say filter rule association now to explain what a filter rule association is when you gnat something you bring it in and we want to redirect port 22 on the land side of the firewall and bring it to forwarding it with nat translation to a device behind here so it hits port 22 on the device behind there there's actually a two-step process that goes on and some firewalls consolidated into a single step or obscure especially the consumer ones are known for obscuring it you just put forward something there's actually the forwarding option and then there's the allowing that rule to happen on when the filter rule that happens they've done this in pf sense if we go over to firewall nat and we look at this right here they have done it by filter association rule and we have a click to say view the filter rule and here is the filter rule versus the nat rule i'm confused because there's the rule for filter association rule that says i should create a filter rule that passes it but where the confusion comes in is when we go over to rules and we go over to when that rule doesn't exist over here which causes me a little bit of confusion but these little nuances are some of the differences that sometimes make it difficult when people say tom why don't you do more open sense videos i'm like i'd have to learn some of these nuances now you can usually reverse engineer and sort this out but i also consulted a documentation which wasn't clear on this this is one of the things that i did kind of notice is the documentation isn't quite as thorough in open sense as in pfsense to address those changes the underlying system may be the same but the nuances do kind of matter for you know if you want to make sure you're doing all these things right all right now let's talk about the alias system they actually both have an alias system so firewall aliases we can do ip we can do ports we can do urls they did the same thing here but once again there's the nuances of how they change it to make it a little bit different but this may come down to preference for how you want to do it they group them all here you hit the little plus and they're just done differently where you do a pull down here instead of a series of tabs goip url tables i was actually at first slightly confused about how they did this but it turns out you do it this way so once again they do offer aliases they do have port aliasing and all those features implemented slightly differently and uh that's a little bit of nuance now what about an intrusion detection system do they have that yes there is intrusion detection so if we go over here to services intrusion detection administration or did it not go there we go intrusion detection they have this now the difference between the way it's implemented is you get to use cerakata you only get to use cerakata versus in pfsense you install a package it's not natively installed it is a separate package but you get to choose which package you want they're both official whether it's the snort package or the package uh for cerakata so you have two options they're using cerakata and opensense and both are great so that's just a nuance if you have a preference for sorry it's not available you can only use cerakata in there now i did notice too i could be me of not knowing where everything is it feels like there's a lot more fine tuning that can be done and a lot more options you can dig into for here but like i said it could be just me not knowing in open sense where it is but overall they both do have that feature now let's talk about qos and the traffic shaper so here's a traffic shaper here's a wizard for the traffic shafer where we can go through and enter a number of lan interfaces uh this is virtualized and doesn't have proper alt queue so it does give an error because they can't do alt q on this particular interface but they just call it shaper inside of here you have pipes cues and rules i didn't see a wizard but they do have the ability here to create some of the rules i'm less familiar with how it works in here but nonetheless it is an available option in here and they do have cuddle cue so that's good vpn options this is interesting because there are different ways apparently the way it handles wire guard and wire guard is one of those little controversial ones so yes it has it but it's got wire guard go implemented currently but my understanding is they're moving over to the kernel wire guard now this is a development version of pfsense and let's talk about the wireguard situation real quick here in the 2.5 version it came out in the 2.51 it was removed the reason why was there some code problems found let's swing all the way over here to the code commits by jason doanfield and this is where some of that confusion comes in i'll leave a link to it so you can read so i'm not going to read you all the code commits on there but i'll leave a link so you can go through it what happened was the team over at netgate hired a developer that yes they hired someone who did not do a great job apparently of writing the code but did do a lot of the code writing and that's a sponsored project that went into the bsd kernel that now anyone who uses the bsd kernel i.e opensense is going to be able to use that code and you're saying no jason donfield is writing it jason donfield imported all the code and that's actually he took the code that was written and then made the changes now i know someone will say it was terrible it was broken etc etc but you can actually look through the commits if you understand how code work and see the incremental and small changes now incremental small changes it doesn't take much code change to change something from hey you've broke something and made a port open or offered an insecure way for something to happen which was also kind of an edge case with an mtu problem if you use an oversized mtu that won't even transport across the internet and accepted that mtu with the special filter rule yes you could buffer overrun the particular experience in there and that was one of the things they did they had a couple race condition issues but it mostly is the same code that's now in here that's been ported back and brought into freebsd for both projects to now enjoy or any project that runs on bsd so it's coming back as a package in 2.6 but it is available as a go implementation currently in open sense but my understanding is they are going to be moving to that kernel implementation so hey i'm so glad someone sponsored the code because they got the ball rolling because it wasn't happening without someone being paid to do it so that's kind of the bottom line on that now moving on to the next topic and that's openvpn once again much the same so we look at openvpn which is long time well established and still a very popular vpn for managing remote users and we look through all the options they have in here like tls authentication and certificate management and all these check boxes plus the ability to add advanced features let's go ahead and look at our test vpn here yep much the same now i didn't check to see if absolutely everything was in feature parity here but you get the idea that they're very similar which is of course when i've done many videos on openvpn people say hey i was able to use your video to figure out how to make the same thing happen inside of opensense because they're very similar to the way they work and of course they do have ipsec in here as well same thing tunnel settings rsa key pairs etc next topic is package management this is where there's definitely a lot of the same packages so we'll go over to the package manager in here and we'll look for h a proxy and this is one of them we can load so hit the little plus here if we want to load h a proxy you can also do the let's encrypt with acme so it's cool once again something else we have and we have those over here installed i don't think i've installed here but it's system and package manager type in proxy all right cool we can find different proxies or specifically we can find uh h a proxy in here what maybe yeah it is right there so there's h a proxy if you want to put in so that's a popular feature i mentioned i really like on pfsense but yes it does exist not used it but it does exist over in the open sense world as well and once again that's pretty cool the one thing where we have a big divergence though is in this pf blocker hugely popular project on pfsense there's not a direct equivalent that i'm aware of because pf blocker natively does not exist in open sense but that package is different but you may have noticed or maybe seen it flipping through here we have this installed now this is a separate third-party package but can be loaded through their package manager called scentsy and it's pretty neat i don't know a ton about it i play with it a little bit it gives you some cool graphs and tells you where people went it has some filtering options when you pay a subscription for it and it's a cool add-on here there's not an equivalent in psense to this particular package for doing this filtering i don't know much more than the review that you can probably find here a feature comparison of the open sense plug-in by scentsy by sunny way valleys by the home network guy and uh film network guy uh i will leave a link to this particular review and he goes down and dives into all the features that it has that is more extensive than i've taken the time to research but he appears to have done a lot more time in it so if you want to read more about this particular plugin and this description seem reasonable to it it is a cool feature on opensense that does not exist in pf sense so that's worth mentioning on to the diagnostics let's talk about pf top i love pf top because pftop allows me to do things like type in host and uh go like i think i can type that host which one yeah there we go we see some connections here um vote here there's one for this all right i like using pf top when i'm doing research to try to figure out what's connecting to what and trying to trace things out it's a great tool and someone's probably already said yeah doesn't open sense have pf top well yes but they just dump the list and don't give you a way to filter it so that's kind of one nuisance i did find right off the top here when i started looking at diagnostics secondly diagnostics there's a lot of them here inside of pfsense so but they're all in one place so i have all these options here i can even do cool things like execute a shell command and you know halt the system and reset the defaults and edit a file and everything else it's a little more confusing how they did it at least to me it is this is my opinion of course someone may think this is better there is a subcategory of diagnostics there's system diagnostics which are going to be under system then diagnostics interface diagnostics firewall diagnostics and it's just a different way of grouping the tools so at first i was confused as to where those things were because i'm used to using menus not using a universal search but maybe that's just the way i am and because i spent too much time i personally do like it better in one list but that's just the way they designed it but props to the open sense people because i've always thought this was stupid in pf sense and i know they've gotten plenty of people complaining about this before is we have a power option to reboot or power it off npf sense to me that absolutely belongs in the short little system menu that's would make a whole lot of sense where do i restart this thing i should be able to go to system and have a power do i want to reboot it or do i want to you know turn it off but pf senses insisted that's a diagnostic tool which i guess in some ways is we reboot things because we're not sure what went wrong so we reboot it to see if it fixes all the problems we're having um and this is just true for most things in tech but they've decided to have halt system and reboot system under diagnostics so i definitely will give props open sense for fixing that when they did the new ui because that's where it belongs i don't know it needs its own separate menu but i think it should be a system function not a diagnostic function but that's my opinion again and uh clearly the people over at neck or pf sense developers don't agree with me maybe someone does but anyways it's such a minor problem honestly once in production we rarely ever reboot a firewall except for updates now i want to talk about logging system logging the logging seems a little bit more dispersed in here and it became a little bit more confusing for me to just see all the logs i am favoring the way the logs are done here um where they're just tabular and i can go through all the different logs in one place to be able to dive into things this just um yeah it's kind of uh consolidated here and in here i don't know it just feels like it's not but the good news is i know there is a way to push all the logging somewhere else so if i push the logs out somewhere that would probably do it but i'm not sure where that is but the logging just feels like system gateway log file they've dispersed it because kind of the way they diagnostic each one's a subheading under each thing so it made it a little bit trickier to go through log files but because we do a lot of troubleshooting this is why i think about this we actually spend a lot of time looking at you know diagnostics and log files because if someone calls us for a consulting project on integrating to our network it's not because it's integrated into your network it's because they're having a problem with it so troubleshooting is a huge piece of the consulting work that we end up doing and having in one place does make my life a lot easier now one minor little thing i'll mention i do like that they've integrated the net flow right here into the system as opposed to having it as a plug-in it's a plug-in inside of pf sense you can use n-top png to dive into some of the net flow data and look at it but they did integrate it natively with netflow and then you tell it to either use an external destination server or you tell it to use localhost here which gives you some insight into some of the traffic uh with literally what's called insight right here this can be helpful when you want to look at certain aspects of things on the land or the land uh how things in traffic and what i p addresses or do some reverse look up on some of the ip addresses that it is reaching out and touching do this it'll pause a second and do that you can do this with n top but like i said it's an add-on plug-in in the packages that you can load for pfsense but it's natively built into here but overall the reporting on this with the traffic reports and things like that are very similar once again to what you can do here looking at packets you can look at system processor traffic vpn users and dive into this and create these views under the monitoring so they they both have a way to do it and frequently when you get into the enterprise market you start piping all the logs and all that netflow data to something that can really do it and there's plenty of projects that support both open sense and pf sense for exporting all of that data into something like grafana and making some really pretty graphs and much more actual intelligence on there so neither one of them i think does an amazing job of giving you the most in-depth reporting but they both have different ways of handling it but the netflow being natively built and i thought was you know plus for the open sense side now finally the question which one should you use now they're both open source projects pf sense though this is the way they've been doing things they have their community edition which is just called pfsense ce or community edition and then they have the psense plus which is the community edition with some closed source add-ons on there there's something similar because i don't believe the full sensei system is fully open source so there's add-ons you can get to pay for or buy the licenses for opensense they do have a business model where they sell support and licenses just like the folks that pf sense and netgate do so there's different ways you can have certain components and add-ons put onto these and this is where people say well it's not truly open source if there's add-ons but the base components are and that's a lot of nuance you can you know spin around and debate about and really go crazy about if you want bottom line of which one you should use pf sensor open sense i don't know just use some common sense that's kind of where i'm going to leave you with this i'm not here to tell you not to use either one because i think they're both good products i think they're both secure products they both have different ways of implementing things from the interface to use a similar underlying system so on there so i can't make those decisions for you but hopefully this video helped you understand the two different product bases and let you use your common sense to make a decision that works for you thanks and thank you for making it to the end of this video if you enjoyed this content please give it a thumbs up if you'd like to see more content from this channel hit the subscribe button and the bell icon to hire a shared project head over to lawrences.com and click on the hire us button right at the top to help this channel out in other ways there is a join button here for youtube and a patreon page where your support is greatly appreciated for deals discounts and offers check out our affiliate links in the descriptions of all of our videos including a link to our shirt store where we have a wide variety of shirts and new designs come out well randomly so check back frequently and finally our forums forums.lawrences.com is where you can have a more in-depth discussion about this video and other tech topics covered on this channel thank you again and we look forward to hearing from you in the meantime check out some of our other videos you

Channel: Lawrence Systems

Views: 77,757

Rating: 4.9402514 out of 5

Keywords: LawrenceSystems, opnsense, opnsense vs pfsense, opnsense firewall, opnsense vs pfsense 2021, opnsense vs pfsense 2020, opnsense vs pfsense performance, opnsense vs pfsense reddit 2021, opnsense vs pfsense speed, opnsense vs pfsense 2.5, opnsense vs pfsense features, pfsense router, network security, firewalls built like a tank, opnsense review 2021

Id: y8R5-xNeHY8

Length: 35min 0sec (2100 seconds)

Published: Thu May 27 2021