#nf-tables #async #nftables-async

nftables-async

An async version of the helper to run nftables, providing full compatibility with the rest of the nftables crate

5 releases (3 breaking)

new 0.4.0 Apr 16, 2025
0.3.0 Mar 23, 2025
0.2.2 Dec 1, 2024
0.2.1 Nov 29, 2024
0.1.1 Oct 27, 2024

#870 in Network programming

Download history 4/week @ 2025-01-03 11/week @ 2025-01-10 10/week @ 2025-01-17 2/week @ 2025-01-24 4/week @ 2025-01-31 7/week @ 2025-02-07 13/week @ 2025-02-14 14/week @ 2025-02-21 4/week @ 2025-02-28 3/week @ 2025-03-07 7/week @ 2025-03-14 128/week @ 2025-03-21 19/week @ 2025-03-28 8/week @ 2025-04-04 105/week @ 2025-04-11

261 downloads per month
Used in 4 crates (via fcnet)

MIT license

15KB
245 lines

nftables-async

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:

  1. TokioProcess using the Tokio stack, enabled via tokio-process feature
  2. AsyncProcess using the async-process crate (Smol stack), enabled via async-process feature.

Why not the async helpers in nftables >0.6?

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:

  1. The support in 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.
  2. The two features are mutually exclusive, making it impossible to compile an nftables that has both enabled. This breaks the use-case of fcnet, that needs both when enabling multiple runtime features, and is generally inconvenient.

Dependencies

~1–13MB
~168K SLoC