Skip to content

Fw updates/v18#15300

Closed
victorjulien wants to merge 23 commits intoOISF:mainfrom
victorjulien:fw-updates/v18
Closed

Fw updates/v18#15300
victorjulien wants to merge 23 commits intoOISF:mainfrom
victorjulien:fw-updates/v18

Conversation

jufajardini and others added 23 commits May 1, 2026 11:10
- tls.cert_chain_len
- datarep
- dataset
- dns.opcode

Part of
Ticket OISF#8387
The firewall enabling flag for tcp.flags was being overwritten by
another line of code.

Related to
Ticket OISF#8387
Clean up host mode tracking, which is used by reject to control how
rejects are sent. Before this patch there were 2 modes: sniffer only
and router. This patch introduces a bridge mode that is automatically
set by the bridge modes. In bridge mode the `Packet::livedev` is used.

Ticket: OISF#8390.
So a value of 0 means no device.
Most code uses an opague type for LiveDevice, so add an id getter.
In prep for storing both directions for IPS.
Update ctx caching to take direction into account.
Use an enum for the firewall related flow control, to improve
readability of the firewall inspection logic.
If a ruleset would use `dns:request_complete` but not have a rule for
`dns:request_started`, the `request_started` hook default policy would
not get invoked.

Add a check to make sure it is invoked.

Ticket: OISF#8495.
For non-UDP (so TCP), don't allow `accept:packet` or `drop:packet` as
this makes the evaluation of other rule hooks unpredictable.

Ticket: OISF#8497.
When there are no rules after prefilter the default policy needs to be invoked.
Fixes: 232276a ("detect: ethernet/arp matching")
For firewall rules, allow multiple actions to be specified in a list

        accept:flow,pass:flow,alert
        accept:flow,alert
        accept:flow,pass:flow

It is mandatory to make the first action the primary firewall policy
action: accept, drop, reject.

Ticket: OISF#8480.
Previously a `accept:flow` action would act as both a firewall "accept" and
a threat detection "pass" for the rest of the flow.

This patch changes that. The `accept:flow` action now only accepts the
rest of the packets for the firewall ruleset, but does still continue
threat detection rule evaluation.

Ticket: OISF#8444.
@victorjulien victorjulien requested review from a team and jasonish as code owners May 1, 2026 09:34
@victorjulien victorjulien mentioned this pull request May 1, 2026
@codecov
Copy link
Copy Markdown

codecov Bot commented May 1, 2026

Codecov Report

❌ Patch coverage is 71.38158% with 87 lines in your changes missing coverage. Please review.
✅ Project coverage is 82.63%. Comparing base (18f742f) to head (d3ea235).

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #15300      +/-   ##
==========================================
- Coverage   82.65%   82.63%   -0.02%     
==========================================
  Files         993      993              
  Lines      270997   271136     +139     
==========================================
+ Hits       223985   224057      +72     
- Misses      47012    47079      +67     
Flag Coverage Δ
fuzzcorpus 61.01% <26.80%> (-0.04%) ⬇️
livemode 18.38% <23.72%> (-0.01%) ⬇️
netns 22.61% <49.83%> (-0.02%) ⬇️
pcap 45.23% <23.79%> (-0.04%) ⬇️
suricata-verify 66.37% <64.48%> (-0.02%) ⬇️
unittests 58.56% <20.40%> (-0.03%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@suricata-qa
Copy link
Copy Markdown

WARNING:

field baseline test %
SURI_TLPR1_stats_chk
.uptime 667 696 104.35%

Pipeline = 31147

@victorjulien victorjulien mentioned this pull request May 1, 2026
@victorjulien
Copy link
Copy Markdown
Member Author

CI issues addressed in #15306

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants