Thomas Eizinger e58ec73bbc refactor(eBPF): imply XDP_TX from Ok(()) (#8604) ...

Currently, the eBPF code isn't consistent in how it handles XDP actions.
For some cases, we return errors and then map them to `XDP_PASS` or
`XDP_DROP`. For others, we return `Ok(XDP_PASS)`. This is unnecessarily
hard to understand.

We refactor the eBPF kernel to ALWAYS use `Error`s for all code-paths
that don't end in `XDP_TX`, i.e. when we successfully modified the
packet and want to send it back out.

In addition, we also change the way we log these errors. Not all errors
are equal and most `XDP_PASS` actions don't need to be logged. Those
packets are simply passing through.

Finally, we also introduce new checks in case any calls to the eBPF
helper functions fail.

Related: #7518

2025-04-01 13:42:00 +00:00

..

ebpf-shared

feat(relay): record metrics about bytes relayed via eBPF (#8556)

2025-03-31 21:57:31 +00:00

ebpf-turn-router

refactor(eBPF): imply XDP_TX from Ok(()) (#8604)

2025-04-01 13:42:00 +00:00

server

feat(relay): make interface for eBPF program configurable (#8592)

2025-04-01 08:20:27 +00:00