Its a real company with real people just backporting opnsense commits to its own fork, telling the government its a french Firewall
One thing of note here is that Greg was active in the forum in the early days. I think you can find the discussion about him wanting a firewall API (or complaining about lack of it), but unwilling to fund it directly but rather through workforce hired by him. This was (and still is) problematic for simple code review and audit reasons since the changes are possibly huge and a design document was also not being proposed at that time.About the fork, if you can call a periodic full update of an older version discontinued by us that, what struck us as odd was the bold behaviour to base their releases on our business release branches that we open-sourced in order for people to look at the contents, but we have since decided to discontinued these branches for that single fact alone.If you look at the commits you see that plugins were thrown into the core and the plugin repository itself scrapped creating a full UTM type software that is "easier to maintain". And if you take another look at the commits you see that operational issues and fixes are not being worked on as a steady stream of updates that make up most of your stable updates. For some reason it's enough to do a new version once or twice in a year and all users are happy.Disclaimer: I'm not complaining. It is what it is. Cheers,Franco
[...] and to a certain extent until now, there is no On Premise Central Management solution beside our own DynFi Manager.
Turns out we were right because few months after we have started our own fork, OPNsense shifted back to the FreeBSD kernel.
Unfortunately we didn't had the chance to have GonzoPancho screaming on the whole internet so social marketing for our distro is still discrete at this stage…
but there clearly will have some very interesting stuff offered that will move us on our own trajectory…
