XTLS / XTLS/Xray-core

Experimental MASQUE‑based VPN MVP (Android/Windows/server) — possible related client / reference for CONNECT‑IP

Open
#6,521 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

PR welcome
Dominant language
Go
Stars
41.7k
Forks
5.9k
Avg merge
3d 10h
Merged PRs (30d)
29

Description

Hi,

I’ve published an experimental MASQUE‑based VPN MVP on GitHub: Android client, Windows client and server.

– MASQUE over QUIC + HTTP/3 CONNECT‑IP (RFC 9484)
– mutual TLS between client and server
– Windows client uses a Wintun adapter with full‑route mode and a separate host route for the MASQUE server
– Android client and server code are included for lab/testing setups
– the public tree contains only source code and sanitized example profiles (no production certificates, keys or VPS endpoints).

Repo: https://github.com/Next1971/masque-vpn-mvp

I think this project could be useful as:
– an external MASQUE client in the Xray ecosystem, or
– a reference implementation for future MASQUE / CONNECT‑IP support in Xray.

I’d be happy to:
– adapt the client to better fit Xray’s configuration model, or
– write documentation / example configs showing how to use this MASQUE client with an Xray‑based backend.

Would you be interested in listing this as a related experimental client or considering a more formal integration path? Any feedback on the current design (especially around CONNECT‑IP behavior and routing) is very welcome.

Thanks in advance for taking a look.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the linked masque-vpn-mvp repository and Xray's existing networking and protocol integration points; compare its CONNECT-IP behavior, mutual TLS, and routing model with Xray's capabilities. Done would be a maintainer decision on whether to list it, document it, or pursue a formal integration path, with scope and relevant tests or configurations identified.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, go
Domain
networking, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.