Messages

Upgraded to the beta.  All is working here so far except for the missing menu button like others reported.  Still testing and will report issues if I find them.

I have this exact card on the latest firmware and I'm able to achieve this link speed with opnsense.   Are you running into issues?

No issues after applying this.  Will run for a few days and report any issues.

Pardon me for asking, when I lookup pfsync, it deals with high availability. Do you have this setup? Reason I ask is that I don't have it setup and I'm trying to determine if I should upgrade and test.  I'd rather wait if it's impacting those without HA too.

Thanks for the info.  I bit the bullet and recreated my groups.  No big deal.

@franco, not sure if you'll see this but I did notice the commit that fixes this issue.  If I upgraded now that it's fixed, would I still encounter this issue?  Just wondering since there won't be a RC2 and I'm itching to try it.

Don't quote me on this but I swear I had the same issue with one of my internal hosts.  I was able to manually clear the block from the CrowdSec console and then identify a solution to the issue for the future.  I used the link below to create a whitelist for my internal LAN ranges.

https://hub.crowdsec.net/author/crowdsecurity/configurations/whitelists

In hindsight it might not have been the best solution as I'd probably want to subject my internal IoT ranges to filtering but still, it's at least might be some sort of starting point for you.

You're blocking all traffic on every port to those IP addresses.  You most likely want to block just 22, 80, and 443 for a destination port.

Thank you for the fixes in 22.1.8 as well as providing an onramp to beta test 13.1-RELEASE.

What does the upgrade cycle look like if we go to 22.7.b for when 22.7 proper is released?  Is that just an opnsense-update jump away to get on the 22.7 series proper once released?

Correct me if I'm wrong but it shouldn't matter as this is just the underlying FreeBSD OS and kernel.  Not the Opnsense extensions.  For the others that are confused, as Franco said previously, you're going to see an update if you check for updates.  If you want to prevent the downgrade to 13.0, you need to lock the base and kernel packages.  Worked great for me.

Thank you Franco and team.  No issues so far.  I was using the pre3 version as well and had zero issues.

Adding the tunable fixed it here as well.  Thank you!

Was going to post something about this eventually since I noticed the same behavior including the error messages in the logs.  I guess I'll just say me too here.

Someone correct me if I'm wrong but I'm think I remember reading that the development version will always offer something to update to.  One question I have though is, is there an easy way to see on GitHub what changes are being offered with the update?

For what it's worth, I have only had the single instance of the issue I had and I'm still running suricata.  Not sure but I think mine was just a hiccup.

I had this problem this morning.  I rebooted because I wasn't sure what was going on as it was just one of my networks on the router that had the issue.  I couldn't ping or reach anything on the network
  This network is on a BCE adapter.  I am running suricata on both networks.  I didn't think anything of it until now because I made some firewall rule changes last night and thought it was that.  I'll troubleshoot more next time.

See here:
https://forum.opnsense.org/index.php?topic=25535.0

Please note that the beta version will always be available for upgrade when
switching to the development version.  At this point no stable packages
are provided and this includes plugins.  These will become available as
the release candidate is released in early January 2022.