| commit | 1e2989802c4ffb2733c7dc34b0edcc87608b34f4 | [log] [tgz] |
|---|---|---|
| author | QUICHE team <quiche-dev@google.com> | Fri Oct 11 16:17:19 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Oct 11 16:18:07 2024 -0700 |
| tree | 209335d6ad0a30c990720eb2a196fcc31c32b64e | |
| parent | 8bc91fefe57daf3bff9a7db5f4108703ce4216c8 [diff] |
Add support for qbone bridging. Changes are primarily two-fold viz. 1. Add an option to start bonnet server with a specified # of qbone bridge ifaces. 2. Start socat relays taking qbone address offset (which enables relaying of packets coming over qbone tunnel either to local device or to any one of the bridged ifaces). PiperOrigin-RevId: 684986925
QUICHE stands for QUIC, Http, Etc. It is Google‘s production-ready implementation of QUIC, HTTP/2, HTTP/3, and related protocols and tools. It powers Google’s servers, Chromium, Envoy, and other projects. It is actively developed and maintained.
There are two public QUICHE repositories. Either one may be used by embedders, as they are automatically kept in sync:
To embed QUICHE in your project, platform APIs need to be implemented and build files need to be created. Note that it is on the QUICHE team's roadmap to include default implementation for all platform APIs and to open-source build files. In the meanwhile, take a look at open source embedders like Chromium and Envoy to get started:
To contribute to QUICHE, follow instructions at CONTRIBUTING.md.
QUICHE is only supported on little-endian platforms.