update tutorials

go-gost · Dec 23, 2024 · b29802b · b29802b
1 parent ad43ced
commit b29802b
Show file tree

Hide file tree

Showing 4 changed files with 12 additions and 4 deletions.
diff --git a/docs/concepts/bypass.md b/docs/concepts/bypass.md
@@ -20,7 +20,7 @@ comments: true
     gost -L http://:8080?bypass=10.0.0.0/8 -F http://192.168.1.1:8080?bypass=172.10.0.0/16,127.0.0.1,localhost,*.example.com,.example.org
     ```
 
-    通过`bypass`参数来指定请求的目标地址匹配规则列表，规则是以逗号分割的IP，CIDR，域名或域名通配符。
+    通过`bypass`参数来指定请求的目标地址匹配规则列表，规则是以逗号分割的IP，IP范围，CIDR，域名或域名通配符。
 
 === "配置文件"
 
@@ -56,8 +56,9 @@ comments: true
       - 10.0.0.0/8
     - name: bypass-1
       matchers:
-      - 172.10.0.0/16
       - 127.0.0.1
+      - 172.20.0.1-172.30.0.255
+      - 172.10.0.0/16
       - localhost
       - '*.example.com'
       - .example.org

diff --git a/docs/tutorials/reverse-proxy-tunnel.md b/docs/tutorials/reverse-proxy-tunnel.md
@@ -99,6 +99,9 @@ comments: true
 
 当主机名为`example.com`时，根据Ingress中的规则匹配到ID为4d21094e-b74c-4916-86c1-d9fa36ea677b的隧道。当流量到达客户端后再由rtcp服务转发给192.168.1.1:80服务。
 
+!!! note "流量类型限制"
+    公共入口点仅支持接收HTTP和带有SNI信息的TLS流量。
+
 !!! tip "高可用性"
     为了提高单个隧道的可用性，可以运行多个客户端，这些客户端使用相同的隧道ID。当需要从隧道获取连接时，将采用加权随机方式选择一个客户端连接，最多3次失败重试。
 

diff --git a/en/docs/concepts/bypass.md b/en/docs/concepts/bypass.md
@@ -17,7 +17,7 @@ Bypass can be set on the service, the hop and the nodes of the forwarding chain
     gost -L http://:8080?bypass=10.0.0.0/8 -F http://192.168.1.1:8080?bypass=172.10.0.0/16,127.0.0.1,localhost,*.example.com,.example.org
     ```
 
-    Use the `bypass` parameter to specify the requested target address matching rule list. The rules are IP, CIDR, domain name or domain name wildcard separated by commas.
+    Use the `bypass` parameter to specify the requested target address matching rule list. The rules are IP, IP range, CIDR, domain name or domain name wildcard separated by commas.
 
 === "File (YAML)"
 
@@ -52,8 +52,9 @@ Bypass can be set on the service, the hop and the nodes of the forwarding chain
       - 10.0.0.0/8
     - name: bypass-1
       matchers:
-      - 172.10.0.0/16
       - 127.0.0.1
+      - 172.20.0.1-172.30.0.255
+      - 172.10.0.0/16
       - localhost
       - '*.example.com'
       - .example.org

diff --git a/en/docs/tutorials/reverse-proxy-tunnel.md b/en/docs/tutorials/reverse-proxy-tunnel.md
@@ -99,6 +99,9 @@ In this example, when the traffic enters the entry point (port 80 of the server)
 
 When the hostname is `example.com`, the tunnel with the ID 4d21094e-b74c-4916-86c1-d9fa36ea677b is matched according to the rules in the Ingress. When the traffic reaches the client, it is forwarded by the rtcp service to the 192.168.1.1:80 service.
 
+!!! note "Traffic Limit"
+    Public entrypoint only supports receiving HTTP and TLS traffic with SNI information.
+
 !!! tip "High Availability"
     In order to improve the availability of a single tunnel, multiple clients can be run, and these clients use the same tunnel ID. When obtaining a connection from the tunnel, a weighted random mechanism will be used, with up to 3 failed retries.