Skip to content

Commit e62d7c0

Browse files
WeltolkWeltolk
committed
update
1 parent 4cc09a4 commit e62d7c0

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

41 files changed

+1860
-147
lines changed

‎README.ENG.md‎

Lines changed: 147 additions & 147 deletions
Original file line numberDiff line numberDiff line change
@@ -1,147 +1,147 @@
1-
#v2ray-examples
2-
3-
Here are some V2Ray configuration examples for reference, the content keeps pace with the times, automation scripts, etc. Please do not pull the configuration from here.
4-
5-
Thanks to KiriKira, the author of vTemplate, Yuluowusheng and all the developers of Project V.
6-
7-
## Contribution Guidelines
8-
9-
You are welcome to make a template for your own configuration and submit a PR.
10-
11-
Templates should adhere to the following standards:
12-
- use 4 spaces for indentation
13-
- Square (curly) brackets do not wrap
14-
- Unneeded fields should be removed
15-
- `log` section only leaves `loglevel`
16-
- For `outbounds`, client side should have `proxy` and `direct`, server side should have `direct` and `block`
17-
- Unless it is a template for a specific scenario, `geoip:private` should be routed to `direct` outbound (server configuration routes to `block` outbound)
18-
- DNS should not appear in config files unless it is a template for a specific scenario
19-
- `uuid` should be left blank and filled by the user.
20-
- `domainStrategy` in `routing` remains the default, which is `AsIs`.
21-
22-
### Examples
23-
24-
<!-- Here yaml is only used for syntax highlighting, the actual content is json -->
25-
```yaml
26-
{
27-
"log": {
28-
"loglevel": "warning"
29-
},
30-
"routing": {},
31-
"inbounds": [],
32-
"outbounds": []
33-
}
34-
```
35-
36-
### client
37-
38-
<!-- Here yaml is only used for syntax highlighting, the actual content is json -->
39-
```yaml
40-
{
41-
"log": {
42-
"loglevel": "warning"
43-
},
44-
"routing": {
45-
"domainStrategy": "AsIs",
46-
"rules": [
47-
{
48-
"ip": [
49-
"geoip:private"
50-
],
51-
"outboundTag": "direct",
52-
"type": "field"
53-
}
54-
]
55-
},
56-
"inbounds": [
57-
{
58-
"port": 1080,
59-
"protocol": "socks",
60-
"settings": {
61-
"auth": "noauth",
62-
"udp": true
63-
},
64-
"tag": "socks"
65-
}
66-
],
67-
"outbounds": [
68-
{
69-
"protocol": "vmess",
70-
"settings": {
71-
"vnext": [
72-
{
73-
"users": [
74-
{
75-
"id": ""
76-
}
77-
],
78-
"port": 1234,
79-
"address": "Your_IP_Address"
80-
}
81-
]
82-
}
83-
},
84-
{
85-
"protocol": "freedom",
86-
"tag": "direct"
87-
}
88-
]
89-
}
90-
```
91-
92-
### Server
93-
94-
<!-- Here yaml is only used for syntax highlighting, the actual content is json -->
95-
```yaml
96-
{
97-
"log": {
98-
"loglevel": "warning"
99-
},
100-
"routing": {
101-
"domainStrategy": "AsIs",
102-
"rules": [
103-
{
104-
"ip": [
105-
"geoip:private"
106-
],
107-
"outboundTag": "blocked",
108-
"type": "field"
109-
}
110-
]
111-
},
112-
"inbounds": [
113-
{
114-
"port": 1234,
115-
"protocol": "vmess",
116-
"settings": {
117-
"clients": [
118-
{
119-
"id": "",
120-
}
121-
]
122-
}
123-
}
124-
],
125-
"outbounds": [
126-
{
127-
"protocol": "freedom"
128-
},
129-
{
130-
"protocol": "blackhole",
131-
"tag": "blocked"
132-
}
133-
]
134-
}
135-
```
136-
137-
## How to choose the configuration that suits you:
138-
139-
![](how-to-choose/how-to-choose-a-v2ray-plan-ENG.png)
140-
141-
Additional Notes:<br>
142-
Although Websocket+TLS+Web may be regarded as the best solution at this stage, it is definitely not a solution recommended for novices to try as soon as they come up, let alone the only usage of V2Ray. <br>
143-
At the same time, you should understand that the network conditions in each region are different (mainly referring to the QoS level of different protocols), you can try all the configurations to find the most suitable one for you, try to ask as little as possible, and it is best not to ask "why do I V2Ray so slow?" Questions like that.
144-
145-
## at last
146-
147-
have fun!
1+
#v2ray-examples
2+
3+
Here are some V2Ray configuration examples for reference, the content keeps pace with the times, automation scripts, etc. Please do not pull the configuration from here.
4+
5+
Thanks to KiriKira, the author of vTemplate, Yuluowusheng and all the developers of Project V.
6+
7+
## Contribution Guidelines
8+
9+
You are welcome to make a template for your own configuration and submit a PR.
10+
11+
Templates should adhere to the following standards:
12+
- use 4 spaces for indentation
13+
- Square (curly) brackets do not wrap
14+
- Unneeded fields should be removed
15+
- `log` section only leaves `loglevel`
16+
- For `outbounds`, client side should have `proxy` and `direct`, server side should have `direct` and `block`
17+
- Unless it is a template for a specific scenario, `geoip:private` should be routed to `direct` outbound (server configuration routes to `block` outbound)
18+
- DNS should not appear in config files unless it is a template for a specific scenario
19+
- `uuid` should be left blank and filled by the user.
20+
- `domainStrategy` in `routing` remains the default, which is `AsIs`.
21+
22+
### Examples
23+
24+
<!-- Here yaml is only used for syntax highlighting, the actual content is json -->
25+
```yaml
26+
{
27+
"log": {
28+
"loglevel": "warning"
29+
},
30+
"routing": {},
31+
"inbounds": [],
32+
"outbounds": []
33+
}
34+
```
35+
36+
### client
37+
38+
<!-- Here yaml is only used for syntax highlighting, the actual content is json -->
39+
```yaml
40+
{
41+
"log": {
42+
"loglevel": "warning"
43+
},
44+
"routing": {
45+
"domainStrategy": "AsIs",
46+
"rules": [
47+
{
48+
"ip": [
49+
"geoip:private"
50+
],
51+
"outboundTag": "direct",
52+
"type": "field"
53+
}
54+
]
55+
},
56+
"inbounds": [
57+
{
58+
"port": 1080,
59+
"protocol": "socks",
60+
"settings": {
61+
"auth": "noauth",
62+
"udp": true
63+
},
64+
"tag": "socks"
65+
}
66+
],
67+
"outbounds": [
68+
{
69+
"protocol": "vmess",
70+
"settings": {
71+
"vnext": [
72+
{
73+
"users": [
74+
{
75+
"id": ""
76+
}
77+
],
78+
"port": 1234,
79+
"address": "Your_IP_Address"
80+
}
81+
]
82+
}
83+
},
84+
{
85+
"protocol": "freedom",
86+
"tag": "direct"
87+
}
88+
]
89+
}
90+
```
91+
92+
### Server
93+
94+
<!-- Here yaml is only used for syntax highlighting, the actual content is json -->
95+
```yaml
96+
{
97+
"log": {
98+
"loglevel": "warning"
99+
},
100+
"routing": {
101+
"domainStrategy": "AsIs",
102+
"rules": [
103+
{
104+
"ip": [
105+
"geoip:private"
106+
],
107+
"outboundTag": "blocked",
108+
"type": "field"
109+
}
110+
]
111+
},
112+
"inbounds": [
113+
{
114+
"port": 1234,
115+
"protocol": "vmess",
116+
"settings": {
117+
"clients": [
118+
{
119+
"id": "",
120+
}
121+
]
122+
}
123+
}
124+
],
125+
"outbounds": [
126+
{
127+
"protocol": "freedom"
128+
},
129+
{
130+
"protocol": "blackhole",
131+
"tag": "blocked"
132+
}
133+
]
134+
}
135+
```
136+
137+
## How to choose the configuration that suits you:
138+
139+
![](how-to-choose/how-to-choose-a-v2ray-plan-ENG.png)
140+
141+
Additional Notes:<br>
142+
Although Websocket+TLS+Web may be regarded as the best solution at this stage, it is definitely not a solution recommended for novices to try as soon as they come up, let alone the only usage of V2Ray. <br>
143+
At the same time, you should understand that the network conditions in each region are different (mainly referring to the QoS level of different protocols), you can try all the configurations to find the most suitable one for you, try to ask as little as possible, and it is best not to ask "why do I V2Ray so slow?" Questions like that.
144+
145+
## at last
146+
147+
have fun!

‎V5-Shadowsocks-TCP/client.json‎

Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
{
2+
"access": {
3+
"type": "Console",
4+
"level": "Warning"
5+
},
6+
"error": {
7+
"type": "Console",
8+
"level": "Warning"
9+
},
10+
"inbounds": [
11+
{
12+
"listen": "127.0.0.1",
13+
"port": "10808",
14+
"protocol": "socks",
15+
"settings": {
16+
"udpEnabled": true,
17+
"address": "127.0.0.1"
18+
}
19+
},
20+
{
21+
"listen": "127.0.0.1",
22+
"port": "10809",
23+
"protocol": "http"
24+
}
25+
],
26+
"outbounds": [
27+
{
28+
"protocol": "shadowsocks",
29+
"settings": {
30+
"address": "{{ host }}",
31+
"port": 1234,
32+
"method": "chacha20-ietf-poly1305",
33+
"password": "{{ password}}"
34+
},
35+
"streamSettings": {
36+
"transport": "tcp"
37+
},
38+
"tag": "proxy"
39+
},
40+
{
41+
"protocol": "freedom",
42+
"tag": "direct"
43+
}
44+
]
45+
}

‎V5-Shadowsocks-TCP/server.json‎

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
{
2+
"access": {
3+
"type": "Console",
4+
"level": "Warning"
5+
},
6+
"error": {
7+
"type": "Console",
8+
"level": "Warning"
9+
},
10+
"inbounds": [
11+
{
12+
"listen": "0.0.0.0",
13+
"port": 1234,
14+
"protocol": "shadowsocks",
15+
"settings": {
16+
"method": "chacha20-ietf-poly1305",
17+
"password": "{{ password }}"
18+
},
19+
"streamSettings": {
20+
"transport": "tcp"
21+
}
22+
}
23+
],
24+
"outbounds": [
25+
{
26+
"protocol": "freedom",
27+
"tag": "direct"
28+
},
29+
{
30+
"protocol": "blackhole",
31+
"tag": "block"
32+
}
33+
]
34+
}

0 commit comments

Comments
 (0)