-
Notifications
You must be signed in to change notification settings - Fork 458
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.
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
Allow --reject-with tcp-reset for TCP rules #1184
Labels
Comments
chrisongthb
added a commit
to chrisongthb/chrisongthb-puppetlabs-firewall
that referenced
this issue
Jan 5, 2024
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the Bug
When defining a TCP rule, one may want to use
--reject-with tcp-reset
. This is not possible in the current Version of this module v7.0.2.Expected Behavior
The module should per-se accept 'tcp-reset' next to 'icmp(6)-net-unreachable', 'icmp(6)-host-unreachable', 'adm-prohibited' and the others. Further more the module should contain a parameter validation: 'tcp-reset' makes only sense, if proto is set to 'tcp'. If that does not match, a helpful error message should be printed on the agent side.
Steps to Reproduce
Environment
The text was updated successfully, but these errors were encountered: