-
Notifications
You must be signed in to change notification settings - Fork 124
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
bug: GetRule and log prefix rule is not being parsed #115
Comments
@stapelberg , sure, will do it next week! |
@stapelberg , did not forget about this. got super busy with something else. Will come back to this soon. |
turekt
added a commit
to turekt/nftables
that referenced
this issue
Feb 15, 2022
Fixes google#115 | Added expr.Log to EXPR_DATA switch | Enriched existing GetRule test with expr.Log check
turekt
added a commit
to turekt/nftables
that referenced
this issue
Feb 15, 2022
Fixes google#115 | Added expr.Log to EXPR_DATA switch | Enriched existing GetRule test with expr.Log check
turekt
added a commit
to turekt/nftables
that referenced
this issue
Feb 17, 2022
Fixes google#115 | Added expr.Log to EXPR_DATA switch | Added test for expr.Log parsing
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It appears that
log prefix
rules are not bring parsed byGetRule()
The following output represents the dump of the above rules.
Issue: Notice the
Exprs: ([]expr.Any) <nil>
as it relates tolog prefix
rule.is:
Next:
is:
Next:
is:
The text was updated successfully, but these errors were encountered: