Dear OPNsense community,
Sensei 1.6.1 is now available; doubling TLS/SSL download speeds and fixing remote Elasticsearch TLS authentication bug.
Full Release Notes:
https://www.sunnyvalley.io/post/sensei-1-6-1-for-opnsense-is-out/
@mb
thanks for the hint and thanks to the developers.
Update to 1.61 went without problems.
Opnsense and Sensei started cleanly after the reboot.
Greetings from Germany
@Mondmann, thanks for the update.
@mb
Thanks for your work and 1.6.1 update.
I'm facing an issue after the 1.6 to 1.6.1 update.
From the UI i can't access the Sensei -> Configuration -> Reporting & Data tab... it never changes.
My dashboard is empty, as reports or other logging feature.
MongoDB service is running with Disk Usage:338 MB
Would you have any hint to receover th ereporting data ? Uninstall / reinstall Sensei ? In that case will it keep the old 1.6 Sensei Data ?
Thanlks for your help,
Regads,
Gallais
I noticed that mine had shutdown itself due to high swap usage (as per message) - considering that nothing else had changed but the new version I was wondering what may have caused this - as it never shutdown itself previously
@Gallais, @r4nd0m,
Support is investigating a similar case now. We'll update the thread about the findings.
@r4nd0m, @Gallais,
can you remove and re-install os-sensei? All should be good now.
Thanks for the info. ;)
Does Sensei check certificats handshake (transparent) or tls inspection (with a cert on device) ? Thanks
Hi @Anael, all welcome.
"Full TLS inspection" will be available for the highest subscription tier. Free/Home/SOHO editions do not have TLS decryption capability.
We make use of clear-text Client / Server HELO messages (during session initialization) to identify the server host names.
That's clear. Thanks mb ! ;)
Do we still need to use tunable? (Re: Call for testing: New netmap enabled kernel (https://forum.opnsense.org/index.php?topic=11477.msg55913#msg55913)):
Quote
This kernel has also support for native netmap support for vmx(4), VMware VMXNET3 Virtual Interface Controller device.
https://svnweb.freebsd.org/base?view=revision&revision=344272
Native netmap support should yield better performance compared to the emulated driver.
Much appreciated if someone with an existing VMware deployment could test & provide feedback.
PS: Please note that you'll need to set vmxnet3.netmap_native tunable to 1 (from System: Settings: Tunables) to enable native netmap mode.