mirror of
https://github.com/XTLS/Xray-docs-next.git
synced 2025-04-05 14:23:34 +03:00
Translate into English
This commit is contained in:
Kevin Amiri
GitHub
parent
eb7b342dab
commit
dcf88e3c57
1 changed files with 36 additions and 36 deletions
|
|
@ -1,12 +1,12 @@
|
|||
# VLESS
|
||||
|
||||
::: danger
|
||||
目前 VLESS 没有自带加密，请用于可靠信道，如 TLS。
|
||||
Currently, VLESS does not have built-in encryption, please use it on a reliable channel, such as TLS.
|
||||
:::
|
||||
|
||||
VLESS 是一个无状态的轻量传输协议，它分为入站和出站两部分，可以作为 Xray 客户端和服务器之间的桥梁。
|
||||
VLESS is a stateless lightweight transport protocol, which is divided into inbound and outbound parts, and can be used as a bridge between Xray clients and servers.
|
||||
|
||||
与 [VMess](./vmess.md) 不同，VLESS 不依赖于系统时间，认证方式同样为 UUID，但不需要 alterId。
|
||||
Unlike [VMess](./vmess.md), VLESS does not rely on system time, and the authentication method is also UUID, but it does not require alterId.
|
||||
|
||||
## OutboundConfigurationObject
|
||||
|
||||
|
|
@ -31,7 +31,7 @@ VLESS 是一个无状态的轻量传输协议，它分为入站和出站两部
|
|||
|
||||
> `vnext`: \[ [ServerObject](#serverobject) \]
|
||||
|
||||
一个数组, 表示 VLESS 服务器列表，包含一组指向服务端的配置, 其中每一项是一个服务器配置。
|
||||
An array, representing the VLESS server list, containing a set of configurations pointing to the server, each of which is a server configuration.
|
||||
|
||||
### ServerObject
|
||||
|
||||
|
|
@ -52,15 +52,15 @@ VLESS 是一个无状态的轻量传输协议，它分为入站和出站两部
|
|||
|
||||
> `address`: address
|
||||
|
||||
服务端地址，指向服务端，支持域名、IPv4、IPv6。
|
||||
Server address, pointing to the server, supporting domain names, IPv4, and IPv6.
|
||||
|
||||
> `port`: number
|
||||
|
||||
服务端端口，通常与服务端监听的端口相同。
|
||||
Server port, usually the same as the port listened by the server.
|
||||
|
||||
> `users`: \[ [UserObject](#userobject) \]
|
||||
|
||||
数组, 一组服务端认可的用户列表, 其中每一项是一个用户配置
|
||||
Array, a list of users recognized by the server, each of which is a user configuration.
|
||||
|
||||
### UserObject
|
||||
|
||||
|
|
@ -75,61 +75,61 @@ VLESS 是一个无状态的轻量传输协议，它分为入站和出站两部
|
|||
|
||||
> `id`: string
|
||||
|
||||
VLESS 的用户 ID，可以是任意小于 30 字节的字符串, 也可以是一个合法的 UUID.
|
||||
自定义字符串和其映射的 UUID 是等价的, 这意味着你将可以这样在配置文件中写 id 来标识同一用户,即
|
||||
The user ID of VLESS, which can be any string less than 30 bytes, or a valid UUID.
|
||||
Custom strings and their mapped UUIDs are equivalent, which means you can write an id in the configuration file to identify the same user, i.e.
|
||||
|
||||
- 写 `"id": "我爱🍉老师1314"`,
|
||||
- 或写 `"id": "5783a3e7-e373-51cd-8642-c83782b807c5"` (此 UUID 是 `我爱🍉老师1314` 的 UUID 映射)
|
||||
- Write `"id": "I love 🍉 teacher 1314"`,
|
||||
- Or write `"id": "5783a3e7-e373-51cd-8642-c83782b807c5"` (this UUID is the UUID mapping of `I love 🍉 teacher 1314`)
|
||||
|
||||
其映射标准在 [VLESS UUID 映射标准：将自定义字符串映射为一个 UUIDv5](https://github.com/XTLS/Xray-core/issues/158)
|
||||
The mapping standard is in [VLESS UUID mapping standard: mapping custom strings to a UUIDv5](https://github.com/XTLS/Xray-core/issues/158)
|
||||
|
||||
你可以使用命令 `xray uuid -i "自定义字符串"` 生成自定义字符串所映射的的 UUID，也可以使用命令 `xray uuid` 生成随机的 UUID。
|
||||
You can use the command `xray uuid -i "custom string"` to generate the UUID mapped by the custom string, or use the command `xray uuid` to generate a random UUID.
|
||||
|
||||
> `encryption`: "none"
|
||||
|
||||
需要填 `"none"`，不能留空。
|
||||
Need to fill in `"none"`, cannot be left empty.
|
||||
|
||||
该要求是为了提醒使用者没有加密，也为了以后出加密方式时，防止使用者填错属性名或填错位置导致裸奔。
|
||||
This requirement is to remind users that there is no encryption and to prevent users from filling in the wrong attribute name or location, causing exposure when encryption methods come out in the future.
|
||||
|
||||
若未正确设置 encryption 的值，使用 Xray 或 -test 时会收到错误信息。
|
||||
If the value of encryption is not set correctly, an error message will be received when using Xray or -test.
|
||||
|
||||
> `flow`: string
|
||||
|
||||
流控模式，用于选择 XTLS 的算法。
|
||||
Flow control mode, used to select the XTLS algorithm.
|
||||
|
||||
目前出站协议中有以下流控模式可选：
|
||||
Currently, there are the following flow control modes available in the outbound protocol:
|
||||
|
||||
- 无 `flow`，空字符或者 `none`：使用普通 TLS 代理
|
||||
- `xtls-rprx-vision`：使用新 XTLS 模式 包含内层握手随机填充 支持 uTLS 模拟客户端指纹
|
||||
- `xtls-rprx-vision-udp443`：同 `xtls-rprx-vision`, 但是放行了目标为 443 端口的 UDP 流量
|
||||
- No `flow`, empty character or `none`: using regular TLS proxy
|
||||
- `xtls-rprx-vision`: using the new XTLS mode includes inner handshake random padding supports uTLS client fingerprint simulation
|
||||
- `xtls-rprx-vision-udp443`: same as `xtls-rprx-vision`, but allows UDP traffic with a destination of port 443
|
||||
|
||||
此外，目前 XTLS 仅支持 TCP、mKCP、DomainSocket 这三种传输方式。
|
||||
In addition, currently, XTLS only supports TCP, mKCP, and DomainSocket transport modes.
|
||||
|
||||
<!-- prettier-ignore -->
|
||||
::: tip 关于 xtls-rprx-*-udp443 流控模式
|
||||
::: tip About xtls-rprx-*-udp443 flow control mode
|
||||
|
||||
启用了 Xray-core 的 XTLS 时，通往 UDP 443 端口的流量默认会被拦截（一般情况下为 QUIC），这样应用就不会使用 QUIC 而会使用 TLS，XTLS 才会真正生效。实际上，QUIC 本身也不适合被代理，因为 QUIC 自带了 TCP 的功能，它作为 UDP 流量在通过 VLESS 协议传输时，底层协议为 TCP，就相当于两层 TCP 了。
|
||||
When using Xray-core's XTLS, traffic to UDP port 443 is blocked by default (generally for QUIC), so the application will use TLS instead of QUIC, and XTLS will take effect. In fact, QUIC itself is not suitable for proxying because it has its own TCP functionality. When it is transmitted as UDP traffic through the VLESS protocol, the underlying protocol is TCP, which is equivalent to two layers of TCP.
|
||||
|
||||
若不需要拦截，请在客户端填写 `xtls-rprx-*-udp443`，服务端不变。
|
||||
If you do not need to block it, please fill in `xtls-rprx-*-udp443` on the client side and do not change the server side.
|
||||
:::
|
||||
|
||||
::: tip 关于 Splice 模式
|
||||
Splice 是 Linux Kernel 提供的函数，系统内核直接转发 TCP，不再经过 Xray 的内存，大大减少了数据拷贝、CPU 上下文切换的次数。
|
||||
::: tip About Splice mode
|
||||
Splice is a function provided by the Linux Kernel. The system kernel directly forwards TCP without going through Xray's memory, greatly reducing the number of data copies and CPU context switches.
|
||||
|
||||
Splice 模式的的使用限制：
|
||||
The usage restrictions of Splice mode are:
|
||||
|
||||
- Linux 环境
|
||||
- 入站协议为 `Dokodemo door`、`Socks`、`HTTP` 等纯净的 TCP 连接, 或其它使用了 XTLS 的入站协议
|
||||
- 出站协议为 VLESS + XTLS
|
||||
- 需要注意的是，使用 mKCP 协议时不会使用 Splice（是的，虽然没有报错，但实际上根本没用到）
|
||||
- Linux environment
|
||||
- Inbound protocols are `Dokodemo door`, `Socks`, `HTTP`, etc., pure TCP connections, or other inbound protocols that use XTLS
|
||||
- Outbound protocol is VLESS + XTLS
|
||||
- It is worth noting that when using the mKCP protocol, Splice will not be used (yes, although there is no error, it is not used at all)
|
||||
|
||||
此外，使用 Splice 时网速显示会滞后，这是特性，不是 bug。
|
||||
In addition, when using Splice, the speed display will lag behind, which is a feature, not a bug.
|
||||
|
||||
使用 Vision 模式 如果满足上述条件 会自动启用 Splice
|
||||
Using Vision mode will automatically enable Splice if the above conditions are met.
|
||||
:::
|
||||
|
||||
> `level`: number
|
||||
|
||||
用户等级，连接会使用这个用户等级对应的 [本地策略](../policy.md#levelpolicyobject)。
|
||||
User level, the connection will use the [local policy](../policy.md#levelpolicyobject) corresponding to this user level.
|
||||
|
||||
level 的值, 对应 [policy](../policy.md#policyobject) 中 `level` 的值。 如不指定, 默认为 0。
|
||||
The value of level corresponds to the value of `level` in [policy](../policy.md#policyobject). If not specified, the default is 0.
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue