github/easytier.github.io
4
0
Fork 0
mirror of https://github.com/EasyTier/easytier.github.io.git synced 2025-05-19 10:27:06 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

update

Browse Source
This commit is contained in:
sijie.sun
2025-02-25 14:05:22 +08:00
parent a00ff95b38
commit eeb6724ec1
6 changed files with 86 additions and 81 deletions
Download Patch File Download Diff File Expand all files Collapse all files
en/guide/network/config-file.md
+1 -1
View File
@@ -16,4 +16,4 @@ Running `easytier-core` directly without parameters will generate the minimal co
## Configuration File Generator
The official website provides a configuration file generator, which you can access via <a href="https://easytier.cn/web/index.html#config_generator">Configuration File Generator</a> to generate configuration files.
The official website provides a configuration file generator, which you can access via <a target="_blank" href="https://easytier.cn/web/index.html#config_generator">Configuration File Generator</a> to generate configuration files.
en/guide/network/kcp-proxy.md
+4 -2
View File
@@ -1,7 +1,5 @@
# KCP Proxy
EasyTier is a remote networking software that uses a TUN device to create a virtual network and transmits data between nodes via the UDP protocol.
EasyTier typically uses the UDP protocol to transmit IP packets within the virtual network. However, some ISPs restrict UDP, which can lead to high packet loss and affect TCP performance within the virtual network.
To address this issue, EasyTier provides a KCP proxy feature that can proxy TCP connections in the virtual network and convert them to KCP for transmission. Thanks to KCP's more aggressive retransmission mechanism, it effectively reduces packet loss and improves TCP transmission speeds within the virtual network.
@@ -40,6 +38,10 @@ If you do not want traffic destined for a specific node to use the KCP protocol,
For example, if you do not want Node B to receive KCP traffic, start EasyTier on Node B with the `--disable-kcp-input` parameter. In this case, even if Node A has enabled the KCP proxy, the traffic from Node A to Node B will continue to use the TCP protocol.
## Subnet-to-Subnet KCP Support
If Node A is a router, and the subnet under A needs to access other EasyTier nodes or other proxied subnets, it can also use the KCP proxy. However, Node A must use the user-space network stack by specifying the `--use-smoltcp` parameter. Otherwise, the TCP protocol will still be used.
## Checking KCP Proxy Status
You can check the status of KCP proxy connections using the EasyTier CLI tool.