[conntrack] Self-correcting mechanism for existing TCP connections' direction
Open
area/ebpf
area/flows
scope/M
type/fix
- Dominant language
- Go
- Stars
- 3.2k
- Forks
- 304
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 78
Description
Currently, for TCP connections that existed before Retina was deployed, conntrack uses a best-effort approach, relying on the ACK packet to determine the direction of these connections. However, this method can be inaccurate. Implementing a self-correcting mechanism, such as examining the packet sequence numbers, could resolve this issue. We also need to figure out a self-correcting mechanism for UDP connections as well.
Contributor guide
Assessment
This issue has not been assessed yet.