| Crates.io | nftables-async |
| lib.rs | nftables-async |
| version | 0.4.0 |
| created_at | 2024-10-27 05:50:16.018193+00 |
| updated_at | 2025-04-16 17:02:58.724439+00 |
| description | An async version of the helper to run nftables, providing full compatibility with the rest of the nftables crate |
| homepage | |
| repository | https://github.com/kanpov/nftables-async |
| max_upload_size | |
| id | 1424359 |
| size | 35,521 |
An async version of the helper to run nftables in the nftables crate. Simply add both nftables-async and nftables to your crate, then use the nftables_async::apply_ruleset or nftables_async::get_current_ruleset to perform manipulations. Everything is compatible with the sync helper, even the error types, the functions, however, return "true" async futures.
To provide the asynchronous I/O, an implementation of the Process trait in the crate is needed. Two implementations are provided built-in behind feature gates:
TokioProcess using the Tokio stack, enabled via tokio-process featureAsyncProcess using the async-process crate (Smol stack), enabled via async-process feature.nftables 0.6.0 introduced tokio and async-process features that are mostly equivalent to this crate, however, these have some disadvantages that make nftables-async still relevant:
nftables is not implemented via a trait (like nftables_async::Process), meaning third-party extensions for async platforms other than Tokio or the async-* stack are not easily possible.nftables that has both enabled. This breaks the use-case of fcnet, that needs both when enabling multiple runtime features, and is generally inconvenient.