search for: op_lookup

https://bugzilla.netfilter.org/show_bug.cgi?id=888 Summary: Assertion errors attempting a statement which (I believe) is grammatically correct. Product: nftables Version: unspecified Platform: x86_64 OS/Version: Fedora Status: NEW Severity: normal Priority: P5 Component: nft

...me { "vlan1", "vi-vlan1_*" } ip daddr 33.44.5.6/32 ip protocol 6 tcp dport 222 accept ^^^^^^^ It appears when using a wildcard interface string in an inline set. The error is raised in byteorder_conversion() called from expr_evaluate_relational() in evaluate.c. Inside the OP_LOOKUP case, row 1232. The string should in host byte order, but that is not expected for the lookup (due to the prefix_expr_alloc()?) -- You are receiving this mail because: You are watching all bug changes. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lis...

...lidays! -------------- next part -------------- Anatole Denis (7): evaluate: Add set to cache only when well-formed tests: Add regression test for malformed sets Revert "evaluate: check for NULL datatype in rhs in lookup expr" src: Interpret OP_NEQ against a set as OP_LOOKUP tests/py: Unmask negative set lookup rule: Introduce helper function cache_flush evaluate: Update cache on flush ruleset Anders K. Pedersen (4): rt: introduce routing expression Replace tests/files/expr-rt with Python based tests, and replace ether type with meta...