A patch has been applied to fix this problem. Web Filtering: Undecided sites - sites which Sensei categorization database did not have the final decision for - were not filtered.Web Filtering: Unknown sites - sites which Sensei categorization database did not have any information for - were not filtered. This check is to prevent an underlying problem with netmap-virtio which results in traffic forwarding to stop. In Proxmox/QEMU/KVM deployments, Sensei UI Configurator filters out virtio based ethernet interfaces.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. 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.
0 kommentar(er)
