packets go in, packets go out, you can't explain that

56 stars 9 forks 56 watchers Rust Mozilla Public License 2.0
3 Open Issues Need Help Last updated: Sep 11, 2025

Open Issues Need Help

View All on GitHub
good first issue feature

packets go in, packets go out, you can't explain that

Rust

AI Summary: The task requires fixing a bug in the Oxide Packet Transformation Engine (OPTE) where only outbound hit times are considered for LFT (likely Lease Time) expiry. The solution involves either using both inbound and outbound hit times for expiry calculations or storing both in a shared atomic `Moment` data structure. This will ensure accurate LFT expiry for both inbound and outbound network flows.

Complexity: 4/5
good first issue

packets go in, packets go out, you can't explain that

Rust

AI Summary: The task involves adding `Send + Sync` bounds to the `Port<N>` type and related structs/traits within the Oxide Packet Transformation Engine (OPTE) project to resolve a Clippy warning about an `Arc` that is not `Send` and `Sync`. This requires identifying all affected structs and traits and adding the necessary bounds, potentially involving the creation of sentinel machinery to enforce the bounds at compile time.

Complexity: 4/5
good first issue cleanup

packets go in, packets go out, you can't explain that

Rust