wirefilter
wirefilter copied to clipboard
cloudflare
An execution engine for Wireshark-like filters
Type should be used from wirefilter:: instead of current crate
The `Scheme!` macro references `crate`, but since it is a macro this will evaluate at compile time to be the crate that is attempting to use wirefilter. We must use...
There is no reason these need the same lifetime, and requiring the same lifetime makes some things impossible like having a Filter with a 'static lifetime and trying to execute...
Would it be possible to have examples of using wirefilter in Go? It's mentioned in the Cloudflare Blog post regarding wirefilter that Cloudflare has embedded the engine into your Go...
Hello! It is not issue itself, but more like feature request for future: it would be great to perform recursive check of nested parameters. For example, you have JSON as...
Currently many errors return spans that last to the end of the input when they could be refined to a narrower region. Not providing specific examples, but it would be...
I’m trying to run the tests for this crate, but it doesn’t compile on a current Rust version. ``` $ cargo test --workspace (other output...) error: expected `;` --> wirefilter-parser/src/lib.rs:55:18...
Hello, I'm now writing a package filter demo using wirefilter master branch, with almost 10rules using regex. I'm curious is there any method to accelerate the match process by combinng...
wirefilter does not support CIDR format: ip.addr == 192.168.0.1/24 --- not supported ip.addr >= 192.168.0.1 and ip.addr
Metadata
Owner
Metadata
An execution engine for Wireshark-like filters