3 ms·

> the originals remain dominant for enterprise and free users anyways. I'm a former pfSense user that reluctantly moved to OPNsense a handful of years ago afte

> the originals remain dominant for enterprise and free users anyways. I'm a former pfSense user that reluctantly moved to OPNsense a handful of years ago after a lot of bad press around Netgate started circulating widely causing me to believe that support for the community offering might wane over time. I was under the impression that many people had moved off of pfSense for home use. I'm surprised by your assertion that it "remains dominant" for free users, and I wonder how you might know this? OPNsense has been rock solid for me, btw. I was reluctant to switch only because of the time sink and perceived risk. Nobody wants to spend a weekend debugging VLAN tagging on their WAN port or some such. Luckily for me, there were no such issues when switching over.

SpecialistK 2y ago
pfSense maintains some momentum due to name recognition, but anyone who digs a little deeper will see that they're clowns and go with OPN instead.
- luckman212 2y ago
  Can you please cite some recent examples of this clownlike behavior?
  - riedel 2y ago
    Out of curiosity I googled 'pfsense clown' and found this thread: https://old.reddit.com/r/opnsense/comments/1ct683k/clown_moment_by_pfsense/ https://old.reddit.com/r/opnsense/comments/1ct683k/clown_mom...
  - IntelMiner 2y ago
    They harassed the OPNsense team, registering a domain to besmirch them and then pretended to have nothing to do with it until ICANN got involved Oh, and they knowingly shipped a broken and insecure Wireguard to their customers, and tried to use their FreeBSD commit status to force it upstream
    - SpecialistK 2y ago
      This is the most recent one I'm familiar with. Jason D even had to get involved and there was a lot of bad blood.
  - guiambros 2y ago
    Try compiling pfSense. No, here's an even simpler task: try compiling packages for pfSense. The clowns from Netgate made it unbelievably difficult, for no good reason other than being antagonist to the open source community.
    - SpecialistK 2y ago
      Meanwhile, I've never tried building OPN but it looks well documented and can be added to a vanilla FreeBSD install. https://github.com/opnsense/core https://github.com/opnsense/core
cromka 2y ago
I did the same and while I never had any issues with pfSense staff being rude or condescending, I had experience such attitudes on multiple occasions with OPNSense staff, and that included my bug reports with fixes provided. I was scratching my head a lot wondering if “I was me, not them” but no, I saw this with others, too, and then realized there’s something wrong there. I don’t even bother reporting anything anymore because of that. This is all very ironic because that kind of attitude was the main drive for many to move away from pfsense.
justsomehnguy 2y ago
> OPNsense has been rock solid for me, btw Well, it works. But try to add some custom parameters to a daemon, which aren't listed on the page. Or try to run more routers than one. Or diag network states even on 4k monitor. There are a thousands cuts using OPNsense in anything more than a home router. Despite ten years of trying this year I ripped it off where it was installed and replaced back with pfSense.

SpecialistK 2y ago

pfSense maintains some momentum due to name recognition, but anyone who digs a little deeper will see that they're clowns and go with OPN instead.

luckman212 2y ago
Can you please cite some recent examples of this clownlike behavior?
- riedel 2y ago
  Out of curiosity I googled 'pfsense clown' and found this thread: https://old.reddit.com/r/opnsense/comments/1ct683k/clown_moment_by_pfsense/ https://old.reddit.com/r/opnsense/comments/1ct683k/clown_mom...
- IntelMiner 2y ago
  They harassed the OPNsense team, registering a domain to besmirch them and then pretended to have nothing to do with it until ICANN got involved Oh, and they knowingly shipped a broken and insecure Wireguard to their customers, and tried to use their FreeBSD commit status to force it upstream
  - SpecialistK 2y ago
    This is the most recent one I'm familiar with. Jason D even had to get involved and there was a lot of bad blood.
- guiambros 2y ago
  Try compiling pfSense. No, here's an even simpler task: try compiling packages for pfSense. The clowns from Netgate made it unbelievably difficult, for no good reason other than being antagonist to the open source community.
  - SpecialistK 2y ago
    Meanwhile, I've never tried building OPN but it looks well documented and can be added to a vanilla FreeBSD install. https://github.com/opnsense/core https://github.com/opnsense/core

cromka 2y ago

I did the same and while I never had any issues with pfSense staff being rude or condescending, I had experience such attitudes on multiple occasions with OPNSense staff, and that included my bug reports with fixes provided. I was scratching my head a lot wondering if “I was me, not them” but no, I saw this with others, too, and then realized there’s something wrong there. I don’t even bother reporting anything anymore because of that. This is all very ironic because that kind of attitude was the main drive for many to move away from pfsense.

justsomehnguy 2y ago

> OPNsense has been rock solid for me, btw Well, it works. But try to add some custom parameters to a daemon, which aren't listed on the page. Or try to run more routers than one. Or diag network states even on 4k monitor. There are a thousands cuts using OPNsense in anything more than a home router. Despite ten years of trying this year I ripped it off where it was installed and replaced back with pfSense.