delete from smf_members where posts=0 and website_url <> ''
been using pfsense for the past 3-4 years for our various offices and i loved the fact i could always build it myself unless that is you all know what happened
Congrats on the thousands of spam bots. Or maybe you have thousands of lurking users with 0 posts who are big fans of SEO, weight loss, pornography, and all the other things typical to back link spam.
Well i know its not the right place but i'd like to say hello at first
1. i hope you guys never take away your tools
2. can someone please summarize what the differences are so far from pfsense apart from the license difference? i'll be regular from here on but a summary of teh differences so far will be a great help
3. tools! what differences are there in build system from pfsense? and has there been a guide set up for using tools? i will be setting up a test firewall (opnsense ofcourse ) tomorrow but from then on i like to build my firewall on my own so a guide will be really helpful
Though you're wasting your time building yourself IMO, whether pfSense or OPNsense.
It's barely any work now, except the initial rewrite we did to bring it back. Eventually, it'll be even less work when we can get rid of the last customisation patches in the FreeBSD ecosystem so we can cut down the code and overrides of FreeBSD. It stays.
The list keeps getting longer and I tend to forget cool things along the way as they become the new normal, but maybe this will suffice:o Redesigned firmware upgrades to allow faster update cycles to ship security patches, but fixes and features in a timely fashion (right now about once a week). People love the seamless upgrade workflow. They get itchy when they don't have new updates for two weeks. o The bootstrap GUI point is almost moot, but for the sake of the argument we're reworking all GUI things that we don't like for usability and user experience as well as making the layout fancy. See e.g. https://opnsense.org/system-health-whats-next/ or the way we redesigned the VPN section and are going to redesign the firewall section (almost ready).o We're aiming to keep an open platform to allow easy builds and extensibility without the need for overrides and too many custom hooks, so people are free to: build their own OPNsense, implement their own plugins, add their own ports and packages, build their own projects or appliances with the framework. We can even do "side-grades" like we do with LibreSSL/OpenSSL or our release and development version. All of those options without having to reboot.o I know plugins are a weak point, but 10 years of an active community account for a lot larger ecosystem. We've decided the old packages system wasn't something we ought to keep (it was over 5000 lines strong), so we are currently rewriting it for 16.1, albeit making it easier to conjure plugins in the first place. To bridge the gap we've included squid (proxy server) and suricata (intrusion detection) into the base installation. We've also added the OpenVPN client exporter. Some people work on routing extensions now (quagga), captive portal voucher plugins, etc.That's my favourite points on top of everything is supposed to work as is nowadays. For more what we believed to be unique works when we did them consult the following URLs.For 15.1: https://forum.opnsense.org/index.php?topic=817.0For 15.7: https://forum.opnsense.org/index.php?topic=837.0
