We are currently experiencing a DDoS across multiple of our public services. This is causing service degradation and partial outages across these services. Mitigations in progress...
I updated my @pfsense firewall last night and it corrupted the OS completely, I spent most of my day re-building the OS, thank god I set up @UnimusNet in my home network.
Remeber kids always back up, (and have a off site back up), I might request that as a feature for Unimus.
We will be performing maintenance and updates on our Portal and Licensing Server starting now (at 10:00 / noon UTC, 12:00 CET, 6:00 AM Eastern / EDT / EST, 20:00 AEST). Expected downtime is 60 minutes to 2 hours maximum.
We'll be exhibiting at @NCSS_Cyber 2026 in Birmingham.
Network automation meets cyber security. Come talk NIS2, network compliance & infrastructure visibility with us.
Unimus 2.8.0 has just been released! This is a major release, bringing our Compliance feature into public availability. Along with Compliance, there are also UI / UX improvements, and drivers for 9 new device types.
Compliance a massive feature and has a bit of a learning curve.
We tried to make it as easy and as friendly to work with as possible. Let me know any feedback and especially UI / UX improvement suggestions.
Unimus 2.8.0 is heading for a Stable release very soon! The biggest new feature of 2.8 is Config Compliance. Check out how Compliance works here: blog.unimus.net/config-compl…
Unimus 2.7.1 was just released! This is a minor feature and bugfix release, containing quality of life enhancements, 15 bug fixes, and drivers for 10 new device types.
For more info and the full Changelog, see the 2.7.1 release thread: forum.unimus.net/viewtopic.p…
Release summary and highlights:
- Added a new "Temporary Tag" feature
- Added new "Actions" on Config Search results
- 7 other minor features and improvements
- Support for 10 new device types
- 15 bugs and issues fixed
We will be performing maintenance and updates on our Portal, Licensing Server and Wiki at 12:00 / noon UTC (14:00 CET, 8:00 AM Eastern / EDT / EST, 22:00 AEST). Expected downtime is 30 minutes to 1 hour maximum.