envoyproxy/envoy

"PROXY_PROTO" for L4 QUIC proxying

Open

#20,380 opened on Mar 16, 2022

View on GitHub
 (0 comments) (0 reactions) (0 assignees)C++ (5,373 forks)batch import
area/quicarea/udphelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (Avg merge 8d) (378 merged PRs in 30d)

Description

It's nice to be able to L4 proxy QUIC without losing original client IP. If you can send large packets, one solution is to prepend a proxy-proto style header from "maglev" style Enovy to L7 Envoy.

One way to signal if a packet is munged by setting the version from standard QUIC versions to something synthetic like kPROX. I'd be happy to sanitize some of our munging and unmunging code when/if someone takes a look at this.

Contributor guide

Research direction
Understand existing proxy protocol support for TCP in Envoy, then explore QUIC integration points in the codebase, particularly the L4 proxy filter and QUIC connection handling. Look at how Envoy currently handles QUIC connections and where a proxy proto header could be prepended.
Tech stack
None
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
C++Envoy architectureQUIC protocolProxy Protocol
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20