IETF CONNECT-IP Hackathon: TUN device for masque_client

This change makes it possible for masque_client to bring up a TUN
device, rather than sending a single encapsulated request, if
--bring_up_tun is passed.

For now, the MTU is hard-coded to 1280, but with this, a connection to
testvm.masque.uno is able to bring up a tun0 that can hit https://www.google.com!

```
blaze build third_party/quic/masque/... && cp -f blaze-bin/third_party/quic/masque/masque_client /tmp && sudo /tmp/masque_client --disable_certificate_verification --masque_mode=connect-ip testvm.masque.uno:9661 --bring_up_tun --uid= --alsologtostderr
curl -D /dev/stdout -4 --interface tun0 "https://www.google.com"
```

PiperOrigin-RevId: 486375988
4 files changed
tree: 8b366dada8f90a85a2423cbf3681d9e9db485a54
  1. build/
  2. depstool/
  3. quiche/
  4. .bazelrc
  5. BUILD.bazel
  6. CONTRIBUTING.md
  7. LICENSE
  8. README.md
  9. WHITESPACE
  10. WORKSPACE.bazel
README.md

QUICHE

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.