Skip to content

client: add optional quic.version (v1 or v2) - #1673

Open
ranthe21 wants to merge 1 commit into
HyNetworks:masterfrom
ranthe21:feat/client-quic-versions
Open

ranthe21 wants to merge 1 commit into
HyNetworks:masterfrom
ranthe21:feat/client-quic-versions

Conversation

@ranthe21

@ranthe21 ranthe21 commented Sep 2, 2026 •

Copy link
Copy Markdown

This adds a client-only quic.version option to allow dialing QUIC v2.

  • Setting this to v1 (or leaving it unset) keeps the current behavior and dials v1 with the Chrome fingerprint intact.
  • Setting this to v2 dials QUIC v2 instead. Since Chrome does not use v2, this automatically disables the Chrome parrot in core and logs a warning.

Other clients like sing-box, Xray, and TUIC only support v1 right now, but the Hysteria server already accepts v2. Adding this gives us a good foundation for supporting v2 going forward. (Some firewalls around the world only block v1...)

The option only changes the QUIC handshake itself. Lower-level transport features like obfs and port hopping run beneath QUIC, so they work with v2 without any issues. No server-side code was touched.

I tested this locally, including with obfs and port hopping enabled under v2, and everything works as expected. I am happy to update the docs on hysteria.network if this gets merged.

@ranthe21
ranthe21 force-pushed the feat/client-quic-versions branch from 9c72e36 to c15d6d8 Compare October 3, 2026 09:54
Lets the client pick the QUIC version to dial: v1 or v2. Unset keeps the
current behavior (v1). v2 turns off the Chrome parrot since Chrome
doesn't do v2.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant