Privacytools.io: Consider change pfsense to opnsense
I saw you suggesting pfsense. but recently pfsense is buyed by company. and another and better fork is here.
https://opnsense.org/
even m0n0wall (pfsense forked) advice opnsense rather than pfsense
bitdegree67
All 6 comments
OPNsense - Wikipedia
https://en.wikipedia.org/wiki/OPNsense
Source code
https://github.com/opnsense
Hillside502
on 18 Aug 2018
@bitdegree67 who bought them recently? I don't see any news about it. And why do you want to replace PFSense with OPNSense? The only reason is it's a better fork? How? Why? Also PFSense is still open source the last time I check and they're both on the same level.
If anything, you should say, add OPNSense alongside with PFSense. If you want to replace it, you have to have some damning news about them, they went closed-source, or have a really good argument more than "it's better".
dnguyen01
on 22 Aug 2018
A real concern with pfSense is transparency. Since Netgate bought the majority share of pfSense and renamed the company to ESF it has been difficult to understand the direction they want the project to go. Removing the tools from github without prior warning and using the brand name to fence off competitors has scared quite a lot of people. Also the license had changed for no apparent reason…
In 2014, pfSense® software was upgraded from a BSD license to an Apache 2 license, with numerous very restrictive clauses on project contribution and re-distribution terms.
These changes contributed to the mobilization of the companies that participated or financed the pfSense® project (directly or indirectly) that encouraged the OPNSense fork and thus enabled its launch.
OPNsense® offers significant advances over its counterpart pfSense® software in security, code quality and interface.
I invite you not to trust me and see for yourself how opnsense has better features than pfsense plus is more transparent
bitdegree67
on 22 Aug 2018
A good trawl through the OPNsense website reveals the thoroughbred --- a racing certainty!
Hillside502
on 22 Aug 2018
In any case, I have to use the informations I find
bitdegree67
on 22 Aug 2018
Potentially a duplicate of https://github.com/privacytoolsIO/privacytools.io/issues/497 ?
Mikaela
on 6 Jul 2019
Related issues
BurungHantu1605
·
3Comments
0verk1ll
·
3Comments
ghost
·
3Comments
johnozbay
·
3Comments
MarkusZoppelt
·
3Comments
Most helpful comment
A real concern with pfSense is transparency. Since Netgate bought the majority share of pfSense and renamed the company to ESF it has been difficult to understand the direction they want the project to go. Removing the tools from github without prior warning and using the brand name to fence off competitors has scared quite a lot of people. Also the license had changed for no apparent reason…
In 2014, pfSense® software was upgraded from a BSD license to an Apache 2 license, with numerous very restrictive clauses on project contribution and re-distribution terms.
These changes contributed to the mobilization of the companies that participated or financed the pfSense® project (directly or indirectly) that encouraged the OPNSense fork and thus enabled its launch.
OPNsense® offers significant advances over its counterpart pfSense® software in security, code quality and interface.
I invite you not to trust me and see for yourself how opnsense has better features than pfsense plus is more transparent