Messages

Hi,
i just tested the patch.
Initially it doesn't work.
But after a reboot everything start working.

https://github.com/opnsense/src/issues/235#issuecomment-2629176435

Well now must wait for CrowdSec fix for this issue: https://github.com/opnsense/plugins/issues/4511

My issue is gone by patching 83975b5.
The opnsense team should build a 25.1_1 release with this patch for avoiding others have the issue after the upgrade to 25.1.

https://github.com/opnsense/src/issues/235

# opnsense-patch 83975b5
# /usr/local/etc/rc.filter_configure

Thanks @notspam for your feedback,
as i wrote on GitHub (l0rdg3x), i'll test this this patch tomorrow and report back to Franco.
i'm pretty sure that patch will fix the issue also on my firewall.

Hi,
if someone is interested, i opened a FR for this.

https://github.com/opnsense/core/issues/8274

Solved. On my site it was modified behaviour with MTU size.

Hi,
https://forum.opnsense.org/index.php?topic=45481.msg227423#msg227423
Issue opened: https://github.com/opnsense/core/issues/8270

Crowdsec blocks haven't appeared in my logs since I upgraded to 25.1 from 24.7.12. I also watched the live view for a few minutes and didn't see a block. I am not using Appsec (don't even know what it is).

Yes exactly!

CrowdSec had problems with Appsec enabled since 24.7.12
Can workaround by reverting or removing appsec collections. But I didn't find a solution to fix the root cause.

Hi, in my case, i don't have AppSec collections.

Hi,
today i update from 24.7.12 to 25.1.
2 issues:

1. MTU
I have the primary WAN in DHCP (i have a public IP from ISP via DHCP) with 1492 MTU (if i set 1500 i have some trouble, and device behind firewall can't reach some sites).
On 24.7.12 everything works.
On 25.1 seems that this parameter doesn't work.
I have issue reaching some site like i have with 1500 MTU.
I also tried decrease in some steps until i reach 1460, but nothing works.
Restore to 24.7.12 snapshot and everything works again.

Issue opened: https://github.com/opnsense/core/issues/8270

2. CrowdSec
With 25.1 seems that nothing is blocked.
I have't time for more investigation about this issue.
Without MTU working i'm unable to test other features.

Thanks.

After a reboot the 502 is gone.
I'm able to download the rules.
BUT (see screenshot)
And i can't see send_telemetry.py work.

We're looking at the 502 errors - this is not a sensor disabling issue.  Resource-wise our internal monitoring shows the server healthy and responsive.  Are you still having this problem?

Yes, i still have the problem.

2025-01-25T10:50:52   Error   send_telemetry.py   unexpected result from https://opnsense.emergingthreats.net/api/v1/event (http_code 502)   
2025-01-25T10:49:11   Error   send_telemetry.py   unexpected result from https://opnsense.emergingthreats.net/api/v1/event (http_code 502)   
2025-01-25T10:48:24   Error   send_telemetry.py   unexpected result from https://opnsense.emergingthreats.net/api/v1/event (http_code 502)


I tried a rule updater:

2025-01-25T11:09:49   Error   rule-updater.py   download failed for https://opnsense.emergingthreats.net/api/v1/ruleset/version (http_code: 502)   
2025-01-25T11:09:48   Error   rule-updater.py   download failed for https://opnsense.emergingthreats.net/api/v1/ruleset/version (http_code: 502)   
2025-01-25T11:09:48   Error   rule-updater.py   download failed for https://opnsense.emergingthreats.net/api/v1/ruleset/engine/suricata/5 (http_code: 502)   
2025-01-25T11:09:47   Error   rule-updater.py   download failed for https://opnsense.emergingthreats.net/api/v1/ruleset/version (http_code: 502)   
2025-01-25T11:09:47   Error   rule-updater.py   download failed for https://opnsense.emergingthreats.net/api/v1/ruleset/engine/suricata/5 (http_code: 502)

Hi,
i still have the issue.
https://github.com/opnsense/plugins/issues/4486#issuecomment-2608435385