Issues I encountered after installing Sensei included web interface locking up, and unable to access opnsesne via ssh. Memory usage never exceeded 35% with sensei running and cpu usage was minimal. The hardware is a Dell Optiplex 8gb ram Intel(R) Core(TM) i5-3475S CPU 2.90GHz. I am running it at home, my internet speed is 300/80. First i need to say that I have had zero issues with opnsense in the year that i have been running it, rock solid. In that time I observed some unexpected behavior.
#DISK SENSEI 1.2 PATCH#
A patch has been applied to fix this problem.
User interface now shows a Warning popup recommending a workaround to assign WAN interface to Suricata and Sensei to LAN interface.
A check added to Interface Configuration menu, preventing Sensei from being assigned to an interface which is in use by Suricata.This is a minor reliability release fixing a few issued reported for 0.6 release.
#DISK SENSEI 1.2 SOFTWARE#
Since we see that more and more people want to see Sensei deployed in more large scale environments, with thousands of users.įor the time being, our focus is to have the software make super stable & make it cover the essential network security requirements of SOHO / SME users. Looking forward, it looks like we'll offer this option. Use case is firewalling + application control + web security. HW: Dual-Core i5-2400 GHz (4 threads) with 10GB RAM - OPNsense + Sensei. They were already using modern CPUs, so CPU was not a problem.įor a reference, with the current architecture, the largest deployment that we are reported is 700+ concurrent users and 500 Mbps/50 Mbps max, 300 Mbps sustained WAN throughput. So instead of starting with a distributed design, we started with this one, suggesting early users to increase the amount of memory they had. Because the deployments were typical of a SOHO, SME, and they were not able to operate a separate deployment just for reporting. All of the first users' feedback was to have it coupled with the firewall. This was an important decision to make when we first started working on the plugin. I've seen that it only can handle 300 and 400 times its capacity if refer to online information (like.
#DISK SENSEI 1.2 PRO#
Where my mackbook pro from 2017 which undergo the same intensity of work has only 136TB for 8%.ĭoes it mean that it my m1 SSD is at the end of its life? How is it possible that it can be such short (not even a year) ?
After 292 days of work, it looks like it already has 134,28 TB of Data units written and it is already at 5% of prefailed reallocation (data from disk sensei). Hello, I start to worry about the SSD of my mac mini m1 16/512.
0 kommentar(er)
