Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Categories
Random page
Top Contributors
Recent changes
Contribute
Create a page
How to help
Wiki policy
Adapt videos to articles
Articles in need of work
Help
Frequently asked questions
Join the discord!
Help about MediaWiki
Consumer_Action_Taskforce
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Futotemporarywikipage
(section)
Page
Discussion
English
Read
Edit
Edit source
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
Edit source
View history
Purge cache
General
What links here
Related changes
Special pages
Page information
Cargo data
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
== Why pfSense? == I chose '''pfSense''' ten years ago because: # It’s open-source. # It’s fast. # It gets regular updates for security issues. # The parent company has paid corporate & business clients relying on their software, which is based on an open source core. The developments with regards to making certain network cards work well with FreeBSD get included upstream to the free versions. # This means that me, as a scrub who didn’t pay for it, get something that is very similar to what corporate clients who are paying $10,000 or more are getting. # If I mess something up with my very unusual custom setup, I can pay the developers of the software to fix it for me. This level of support is not common in many open source projects. If I want to cry uncle & pay them an annual fee, they will respond to my questions & provide me with '''''REAL''''' answers rather than tell me to go ''“rtfm”''. # It comes with features like '''pfBlockerNG''' to block ads, scams, and malware at IP & DNS level with regular updates. I use '''pfSense''' now because: # I’m used to it. # The idea of redoing my complicated setup from scratch gives me hives. # See #2, in regard to becoming acquainted with the unique quirks of other open source software. I had very good reasons for choosing '''pfSense''' ten years ago – and I have good reasons to use it today. That doesn’t mean it’s the best. Feel free to use whatever you want to use. For the purposes of this guide, I will be using '''pfSense'''. There’s a bit of a debate between '''pfSense''' and <code>OPNsense</code>. TL;DR, the developers of '''pfSense''' are [https://opnsense.org/opnsense-com/ not the nicest people sometimes]. If this bothers you, consider checking out <code>OPNsense</code>. Since I’ve been using '''pfSense''' for a decade, I’ve built much of my infrastructure around it. I am well aware of its quirks and don’t feel like setting up my network from scratch, so I am using '''pfSense''' for this tutorial. Regardless of the [https://news.ycombinator.com/item?id=17431809 developers], you are infinitely better off using '''pfSense''' on your own hardware than standard routers. <span id="choosing-the-right-hardware"></span>
Summary:
Please note that all contributions to Consumer_Action_Taskforce are considered to be released under the Creative Commons Attribution-ShareAlike 4.0 International (see
Consumer Action Taskforce:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
To protect the wiki against automated edit spam, we kindly ask you to solve the following hCaptcha:
Cancel
Editing help
(opens in new window)