black-internet-days-ahead/Xray-examples
1
0
Fork 0
mirror of https://github.com/XTLS/Xray-examples.git synced 2024-09-19 18:17:49 +00:00
Code Issues Packages Projects Releases Wiki Activity
Xray-examples/ReverseProxy/VLESS-TCP-XTLS-WS/README.ENG.md
yuhan6665 d35c6f5aaa Update README.ENG.md url fix 
Update vmess_ws_tls.json comment translate

Update vmess_tcp_tls.json comment translate

Update vless_ws_tls.json comment trnslate

Update vless_tcp_xtls.json comment translate

Update vless_tcp_tls.json comment translate

Update trojan_tcp_tls.json comment translate

Create README.ENG.md

Update README.md add link README.ENG.md

Update README.md add link README.ENG.md

Create README.ENG.md

Update README.md add link README.ENG.md

Create README.ENG.md

Update client.json comment transalate

Update server.json comment translate

Update README.md add english translate

Update README.md add english link

Create README.ENG.md

Update Caddyfile comment translate

Update client.json comment translate

Update server.json comment translate

Update README.md add link README.ENG.md

Create RREADME.ENG.md

Update config_client_tcp_tls.json translate comment

Update config_client_ws_tls.json translate comment

Update config_server.json comment translate

Update README.md add link README.ENG.md

Create README.ENG.md

Update config_client.json comment translate

Update config_server.json comment translate

Update client.json translate comment

Update server.json translate comment

Update README.md add link README.ENG.md

Create README.ENG.md

Update server.json translate comment

Update README.md add link README.ENG.md

Update README.md

Create README.ENG.md

Co-authored-by: lk29 <12291632+lk29@users.noreply.github.com>
2023-04-05 21:08:31 -04:00

1 KiB
Raw Blame History

VLESS over TCP with XTLS + fallback & split

Cooperate with fallback, use port 443 + XTLS + WS and route diversion to realize reverse proxy and enhance concealment.

There are two client connection methods: VLESS over WS with TLS / VLESS over TCP with XTLS

The portal setting defaults to the web server on port 80 (it can also be replaced with a database, FTP, etc.), refer to VLESS-TCP-XTLS-WHATEVER

additional configuration

If your portal is outside the country, you can use routing splitting to achieve scientific Internet access + access to intranet devices at the same time.

Routing split

According to the prompt in the configuration, in the Portal configuration, uncomment the first route:

// "ip": [
// "geoip:private"
// ],

At this time, when the traffic matches the "external" or "externalws" label, and the target ip of the access is a private ip address, the traffic will be forwarded to the bridge, and the rest of the traffic will go direct.