Skip to content

Commit d35c6f5

Browse files
yuhan6665lk29
yuhan6665
and
lk29
committed
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 <[email protected]>
1 parent 28052d7 commit d35c6f5

File tree

18 files changed

+482
-4
lines changed

18 files changed

+482
-4
lines changed

‎ReverseProxy/README.ENG.md

+21
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
# reverse proxy
2+
# principle
3+
Xray Client <--- VMESS/SS ---> Xray Portal (requires public IP) <--- VMESS/SS ---> Xray Bridge
4+
# illustrate
5+
In the configuration, the internal network device uses `bridge.json`, the device with public network ip uses `portal.json`, and the device connected to the intranet through `portal` uses `client.json`.
6+
7+
In practical applications, `VMESS-TCP, Shadowsocks-2022`, etc. can be used as the transmission protocols from Xray Client to Xray Portal, and from Xray Bridge to Xray Portal.
8+
9+
## psk
10+
11+
Shadowsocks 2022 uses a pre-shared key similar to WireGuard for the password.
12+
13+
Use `openssl rand -base64 <length>` to generate a shadowsocks-rust compatible key, the length depends on the encryption method used.
14+
15+
| encryption method | key length |
16+
|--------------------------------|-----:|
17+
| 2022-blake3-aes-128-gcm | 16 |
18+
| 2022-blake3-aes-256-gcm | 32 |
19+
| 2022-blake3-chacha20-poly1305 | 32 |
20+
21+
In the Go implementation, 32-bit keys always work.

‎ReverseProxy/README.md

+4-1
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,8 @@
1+
[ENGLISH](README.ENG.md)
2+
13
# 反向代理
24
# 原理
5+
36
Xray Client <--- VMESS/SS ---> Xray Portal(需要公网 IP) <--- VMESS/SS ---> Xray Bridge
47
# 说明
58
配置中，内网设备使用的配置为 `bridge.json`，有公网 ip 的设备使用 `portal.json`，通过`portal`连接到内网的设备使用`client.json`。
@@ -18,4 +21,4 @@ Shadowsocks 2022 使用与 WireGuard 类似的预共享密钥作为密码。
1821
| 2022-blake3-aes-256-gcm | 32 |
1922
| 2022-blake3-chacha20-poly1305 | 32 |
2023

21-
在 Go 实现中，32 位密钥始终工作。
24+
在 Go 实现中，32 位密钥始终工作。

‎ReverseProxy/VLESS-TCP-XTLS-WS/README.ENG.md

+20
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
# VLESS over TCP with XTLS + fallback & split
2+
3+
Cooperate with fallback, use port 443 + XTLS + WS and route diversion to realize reverse proxy and enhance concealment.
4+
5+
There are two client connection methods: VLESS over WS with TLS / VLESS over TCP with XTLS
6+
7+
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](https://github.com/XTLS/Xray-examples/blob/main/VLESS-TCP-XTLS-WHATEVER/README.md)
8+
9+
# additional configuration
10+
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.
11+
12+
## Routing split
13+
According to the prompt in the configuration, in the `Portal` configuration, uncomment the first route:
14+
```
15+
// "ip": [
16+
// "geoip:private"
17+
// ],
18+
```
19+
20+
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.

‎ReverseProxy/VLESS-TCP-XTLS-WS/README.md

+2
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,7 @@
11
# VLESS over TCP with XTLS + 回落 & 分流
22

3+
[ENGLISH](README.ENG.md)
4+
35
配合回落，使用 443 端口 + XTLS + WS 和路由分流，实现反向代理，增强隐蔽性。
46

57
客户端连接方式有 VLESS over WS with TLS / VLESS over TCP with XTLS 两种

‎Shadowsocks-2022/README.ENG.md

+239
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,239 @@
1+
#Shadowsocks2022
2+
3+
Server-side JSON
4+
5+
```json
6+
{
7+
"inbounds": [
8+
{
9+
"port": 1234,
10+
"protocol": "shadowsocks",
11+
"settings": {
12+
"method": "2022-blake3-aes-128-gcm",
13+
"password": "{{ psk }}",
14+
"network": "tcp,udp"
15+
}
16+
}
17+
],
18+
"outbounds": [
19+
{
20+
"protocol": "freedom"
21+
}
22+
]
23+
}
24+
```
25+
26+
Server-side JSON (multi-user)
27+
28+
```json
29+
{
30+
"inbounds": [
31+
{
32+
"port": 1234,
33+
"protocol": "shadowsocks",
34+
"settings": {
35+
"method": "2022-blake3-aes-128-gcm",
36+
"password": "{{ server psk }}",
37+
"clients": [
38+
{
39+
"password": "{{ user psk }}",
40+
"email": "my user"
41+
}
42+
],
43+
"network": "tcp,udp"
44+
}
45+
}
46+
],
47+
"outbounds": [
48+
{
49+
"protocol": "freedom"
50+
}
51+
]
52+
}
53+
```
54+
55+
Server-side JSON (transit)
56+
57+
```json
58+
{
59+
"inbounds": [
60+
{
61+
"port": 1234,
62+
"protocol": "shadowsocks",
63+
"settings": {
64+
"method": "2022-blake3-aes-128-gcm",
65+
"password": "{{ relay psk }}",
66+
"clients": [
67+
{
68+
"address": "server",
69+
"port": 1234,
70+
"password": "{{ server/user psk }}",
71+
"email": "my server"
72+
}
73+
],
74+
"network": "tcp,udp"
75+
}
76+
}
77+
],
78+
"outbounds": [
79+
{
80+
"protocol": "freedom"
81+
}
82+
]
83+
}
84+
```
85+
86+
Client JSON
87+
88+
```json
89+
{
90+
"inbounds": [
91+
{
92+
"port": 10801,
93+
"protocol": "socks",
94+
"settings": {
95+
"udp": true
96+
}
97+
},
98+
{
99+
"port": 10802,
100+
"protocol": "http"
101+
}
102+
],
103+
"outbounds": [
104+
{
105+
"protocol": "shadowsocks",
106+
"settings": {
107+
"servers": [
108+
{
109+
"address": "{{ host }}",
110+
"port": 1234,
111+
"method": "2022-blake3-aes-128-gcm",
112+
"password": "{{ psk }}"
113+
}
114+
]
115+
}
116+
}
117+
]
118+
}
119+
```
120+
121+
Client JSON (UDP over TCP)
122+
123+
```json
124+
{
125+
"inbounds": [
126+
{
127+
"port": 10801,
128+
"protocol": "socks",
129+
"settings": {
130+
"udp": true
131+
}
132+
},
133+
{
134+
"port": 10802,
135+
"protocol": "http"
136+
}
137+
],
138+
"outbounds": [
139+
{
140+
"protocol": "shadowsocks",
141+
"settings": {
142+
"servers": [
143+
{
144+
"address": "{{ host }}",
145+
"port": 1234,
146+
"method": "2022-blake3-aes-128-gcm",
147+
"password": "{{ psk }}",
148+
"uot": true
149+
}
150+
]
151+
}
152+
}
153+
]
154+
}
155+
```
156+
157+
Client JSON (multi-user)
158+
159+
```json
160+
{
161+
"inbounds": [
162+
{
163+
"port": 10801,
164+
"protocol": "socks",
165+
"settings": {
166+
"udp": true
167+
}
168+
},
169+
{
170+
"port": 10802,
171+
"protocol": "http"
172+
}
173+
],
174+
"outbounds": [
175+
{
176+
"protocol": "shadowsocks",
177+
"settings": {
178+
"servers": [
179+
{
180+
"address": "{{ host }}",
181+
"port": 1234,
182+
"method": "2022-blake3-aes-128-gcm",
183+
"password": "{{ server psk }}:{{ user psk }}"
184+
}
185+
]
186+
}
187+
}
188+
]
189+
}
190+
```
191+
192+
Client JSON (transit)
193+
194+
```json
195+
{
196+
"inbounds": [
197+
{
198+
"port": 10801,
199+
"protocol": "socks",
200+
"settings": {
201+
"udp": true
202+
}
203+
},
204+
{
205+
"port": 10802,
206+
"protocol": "http"
207+
}
208+
],
209+
"outbounds": [
210+
{
211+
"protocol": "shadowsocks",
212+
"settings": {
213+
"servers": [
214+
{
215+
"address": "{{ host }}",
216+
"port": 1234,
217+
"method": "2022-blake3-aes-128-gcm",
218+
"password": "{{ relay psk }}:{{ user psk }}"
219+
}
220+
]
221+
}
222+
}
223+
]
224+
}
225+
```
226+
227+
## Password
228+
229+
Shadowsocks 2022 uses a pre-shared key similar to WireGuard for the password.
230+
231+
Use `openssl rand -base64 <length>` to generate a shadowsocks-rust compatible key, the length depends on the encryption method used.
232+
233+
| encryption method | key length |
234+
|--------------------------------|-----:|
235+
| 2022-blake3-aes-128-gcm | 16 |
236+
| 2022-blake3-aes-256-gcm | 32 |
237+
| 2022-blake3-chacha20-poly1305 | 32 |
238+
239+
In the Go implementation, 32-bit keys always work.

‎Shadowsocks-2022/README.md

+3-1
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,7 @@
11
# Shadowsocks 2022
22

3+
[ENGLISH](README.ENG.md)
4+
35
服务端 JSON
46

57
```json
@@ -236,4 +238,4 @@ Shadowsocks 2022 使用与 WireGuard 类似的预共享密钥作为密码。
236238
| 2022-blake3-aes-256-gcm | 32 |
237239
| 2022-blake3-chacha20-poly1305 | 32 |
238240

239-
在 Go 实现中，32 位密钥始终工作。
241+
在 Go 实现中，32 位密钥始终工作。

0 commit comments

Comments
 (0)