Messages

So, can I infer from your statement that Windows 2016 Active Directory is not supported?

Secondly, thanks for that info and I might look in that direction of using Radius.

I looked through the forums and did not see any specific topics around this question, but in the event I missed something please feel free to just send a link and say "check this out."

I have an AD Server running on Windows 2016 and was having issues getting it to be registered with OPNsense, so before I dig in here I wanted to see if Windows 2016 AD was even supported with OPNsense for LDAP and or LDAP +OTP?

Of not, not a problem but curious if there were plans to support it, or maybe recommend some workarounds.

Thanks

Not sure if this is just my setup but after upgrading to OPNsense 18.7.8 I get stuck in a loop that won't complete.  Because it reset my configuration of Sensei* after the OPNsense 18.7.8 upgrade, I have to go through the config wizard again and when I click finish, it attempts to configure everything but kicks out the attached error.  Essentially it tells me, "error indices could not be created," and I am stuck in that loop as it returns me to the beginning of the config wizard.

So, #1, is it just me?
and #2, assuming it is not me and before I simply try to uninstall/reinstall, any ideas?

Thanks

*Is it normal for an OPNsense upgrade to reset my Sensei configuration?  If the answer is yes, that is fine but also if there is a way to backup a config and restore it that would help me retain settings.  Either way, love the solution and reconfiguration is actually a minor thing in the grand scheme of things so if the answer is no here then that is fine as I still find huge value in the software.

Thanks

When running a security audit via the audit now capability in OPNsense I get the reference to a vulnerability in lightttpd (see attached).

Is this already address via some mitigating controls or is this yet to be address in an upcomgin release of OPNsense?

Thanks

Not sure if this is the right place to post this, so if I am wrong please redirect me.

I have noticed with Sensei (BTW, it is working fine) that when I run a health audit in OPNsense I get the following (see attached screenshot) checksum mismatch for the nodes.csv file and was curious if this is normal or something is wrong.  Things appear to work fine and no matter what Cloud Threat Intel selections I make (not sure that is related but it might be) I get the mismatch and the Cloud Threat Intel is working fine regardless, or at least shows up and running.

And, on another note, in terms of processing when do the Sensei components process information in terms of order?  For example, I use the web proxy (squid) in OPNsense and was curious if Sensei process the packets before the proxy or after or somehow during, or frankly something completely different if I am misunderstanding the order of operations.

Thanks in advance.