Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

The fate of forbidden packets should be configurable #2

Closed
LionelCons opened this issue Nov 10, 2020 · 2 comments · Fixed by #7
Closed

The fate of forbidden packets should be configurable #2

LionelCons opened this issue Nov 10, 2020 · 2 comments · Fixed by #7

Comments

@LionelCons
Copy link

A forbidden packet is currently logged and denied. This is hard-coded in the 'INPUT-log_rejected' fragment and it is not configurable.

The fate of forbidden packets should be configurable.

This is especially important for the log prefix and the associated action (some may want to drop rather than reject).
@duritong
Copy link
Collaborator

Sounds reasonable, happy to merge a MR

This was referenced Nov 15, 2020
Merged
Merged
@LionelCons
Copy link
Author

FWIW, I have tested Nacho's log_prefix and reject_with and they work fine in my environment. So these 2 MRs do fix this issue.

@keachi keachi closed this as completed in #7 Nov 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add a parameter to control the fate of discarded traffic nbarrientos/puppet-nftables
2 participants
@duritong @LionelCons