feat(dpi): added additional logging when dpi blocks #1482
Merged
+17
−5
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gsanchietti
reviewed
Jan 20, 2026
gsanchietti
approved these changes
Jan 20, 2026
Co-authored-by: Giacomo Sanchietti <[email protected]>
Collaborator
Author
|
QA: check that you can actively see the blocked applications in the logs |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Following a discussion with @francio87, we identified that support staff face difficulties detecting which applications are being caught by the DPI filter, making troubleshooting more challenging.
Since netifyd v5 now properly supports logging additional output when a block is applied, I've added the log option to the rules. This ensures that logs are saved every 60 seconds in /var/run/netifyd/dpi-actions-*, improving visibility into blocked applications.