Expand description
Framework for packet filtering.
Structs§
- Address
Matcher - A matcher for IP addresses.
- Filter
Api - The filtering API.
- Hook
- A particular entry point for packet processing in which filtering routines are installed.
- IpRoutines
- Routines that perform ordinary IP filtering.
- NatRoutines
- Routines that can perform NAT.
- Packet
Matcher - Top-level matcher for IP packets.
- Port
Matcher - A matcher for transport-layer port numbers.
- Proof
OfEgress Check - A witness type to indicate that the egress filtering hook has been run.
- Routine
- A sequence of
Rules. - Routines
- IP version-specific filtering routine state.
- Rule
- A set of criteria (matchers) and a resultant action to take if a given packet matches.
- Transport
Protocol Matcher - A matcher for transport-layer protocol or port numbers.
- Tuple
- A tuple for a flow in a single direction.
- Uninstalled
Routine - A handle to a
Routinethat is not installed in a particular hook, and therefore is only run if jumped to from another routine.
Enums§
- Action
- The action to take on a packet.
- Address
Matcher Type - A matcher for IP addresses.
- Interface
Matcher - A matcher for network interfaces.
- Mark
Action - An action that can be applied to a mark.
- Transparent
Proxy - Transparently intercept the packet and deliver it to a local socket without changing the packet header.
- Validation
Error - Provided filtering state was invalid.
Traits§
- Filter
Bindings Context - Trait aggregating functionality required from bindings.
- Filter
Bindings Types - Trait defining required types for filtering provided by bindings.
- Interface
Properties - Allows filtering code to match on properties of an interface (ID, name, and device class) without Netstack3 Core (or Bindings, in the case of the device class) having to specifically expose that state.