OPNsense Forum

English Forums => Intrusion Detection and Prevention => Topic started by: planetf1 on September 09, 2024, 10:43:38 AM

Title: Suricata rule update issues (24.7.3)
Post by: planetf1 on September 09, 2024, 10:43:38 AM
I'm seeing various errors like

2024-09-09T06:00:02   Error   send_heartbeat.py   unexpected result from https://opnsense.emergingthreats.net/api/v1/telemetry (http_code 502)

2024-09-09T00:00:02   Error   rule-updater.py   download failed for https://opnsense.emergingthreats.net/api/v1/ruleset/engine/suricata/5 (http_code: 502)

2024-09-09T00:00:01   Error   rule-updater.py   download failed for https://opnsense.emergingthreats.net/api/v1/ruleset/version (http_code: 502)

These have been happening since 2024-09-04 and occur daily.

No network issues I"m aware of
I have an et_telemetry.token


Title: Re: Suricata rule update issues (24.7.3)
Post by: guenti_r on January 09, 2025, 12:08:57 PM
Same here, see https://forum.opnsense.org/index.php?topic=45112.0 (https://forum.opnsense.org/index.php?topic=45112.0)
Title: Re: Suricata rule update issues (24.7.3)
Post by: corran22 on January 21, 2025, 07:33:16 PM
Greetings.  Disabled sensors should now be re-enabled.  We've modified the token code to increase the size of the window that's examined to determine whether a sensor is still sending us data or not. Apologies for any disruption. We'll get some documentation out clarifying our position on telemetry reception and periodicy soon.--ET Team