From 68a23a9717947ec3fb8fe12fc0d76d2e2104a999 Mon Sep 17 00:00:00 2001 From: arraykeys Date: Wed, 24 Nov 2021 10:25:30 +0800 Subject: [PATCH] update --- README.md | 87 ++++++++++++++++++++++++++++++++++++++++ docs/manual/manual.md | 87 ++++++++++++++++++++++++++++++++++++++++ docs/sitemap.xml | 12 +++--- docs/tags/cdn/index.html | 4 +- docs/tags/cdn/index.xml | 4 +- docs/tags/index.xml | 2 +- 6 files changed, 185 insertions(+), 11 deletions(-) diff --git a/README.md b/README.md index 7753412..136a80d 100644 --- a/README.md +++ b/README.md @@ -708,6 +708,27 @@ The `--bind-listen` parameter can be used to open the client connection with the `proxy http -t tcp -p 2.2.2.2:33080 --bind-listen` +#### Flexible Outgoing IP + +Although the above `--bind-listen` parameter can specify the outgoing IP, the `entry IP` and the `outgoing IP` cannot be referenced artificially. If you want the ingress IP and the egress IP to be different, you can use the `--bind-ip` parameter, format: `IP:port`, for example: `1.1.1.1:8080`, `[2000:0:0:0:0 :0:0:1]:8080`. For multiple binding requirements, the `--bind-ip` parameter can be repeated. + +For example, this machine has IP `5.5.5.5`, `6.6.6.6`, and monitors two ports `8888` and `7777`, the command is as follows: + +`Proxy tcp -t tcp -p :8888,:7777 --bind-ip 5.5.5.5:7777 --bind-ip 6.6.6.6:8888 -T tcp -P 2.2.2.2:3322` + +Then the client access port `7777`, the outgoing IP is `5.5.5.5`, access port `8888`, the outgoing IP is `6.6.6.6`, if both `--bind-ip` and `--bind- are set at the same time listen`,`--bind-ip` has higher priority. + +In addition, the `IP` part of the `--bind-ip` parameter supports specifying the `network card name`, `wildcards`, and more than one can be specified. The detailed description is as follows: + +- Specify the network card name, such as: `--bind-ip eth0:7777`, and then the client accesses the `7777` port, and the egress IP is the IP of the eth0 network card. +- The network card name supports wildcards, such as: `--bind-ip eth0.*:7777`, then the client accesses the port `7777`, and the egress IP is randomly selected from the IP of the network card starting with `eth0.`. +- IP supports wildcards, such as: `--bind-ip 192.168.?.*:777`, then the client accesses the `7777` port, the outgoing IP is all the IPs of the machine, and matches the IP of `192.168.?.*` A randomly selected one. +- It can also be several combinations of network card name and IP, and several selective divisions using half-width, such as: `-bind-ip pppoe??,192.168.?.*:7777`, and then the client accesses the `7777` port , The outgoing IP is the machine's network card name matching `pppoe??` + It is randomly selected from the IP matching `192.168.?.*` in the machine IP. +- The wildcard character `*` represents 0 to any character, `? `Represents 1 character. +- If the IP of the network card changes, it will take effect in real time. +- You can use the `--bind-refresh` parameter to specify the interval to refresh the local network card information, the default is `5`, the unit is second. + ### 1.17 Certificate parameters use base64 data By default, the -C, -K parameter is the path to the crt certificate and the key file. @@ -816,6 +837,28 @@ When the TCP proxy is a superior type (parameter: -T) is tcp, it supports the sp `proxy tcp -p ":33080" -T tcp -P" 192.168.22.33:22" -B` +#### Flexible Outgoing IP + +Although the above `--bind-listen` parameter can specify the outgoing IP, the `entry IP` and the ` outgoing IP` cannot be referenced artificially. If you want the ingress IP to be different from the egress IP, you can use the `--bind-ip` parameter, format: `IP:port`, for example: `1.1.1.1:8080` +, `[2000:0:0:0:0:0:0:1]:8080`. For multiple binding requirements, you can repeat the `--bind-ip` parameter identification. + +For example, this machine has IP `5.5.5.5`, `6.6.6.6`, and monitors two ports `8888` and `7777`, the command is as follows: + +`Proxy tcp -t tcp -p :8888,:7777 --bind-ip 5.5.5.5:7777 --bind-ip 6.6.6.6:8888 -T tcp -P 2.2.2.2:3322` + +Then the client access port `7777`, the outgoing IP is `5.5.5.5`, access port `8888`, the outgoing IP is `6.6.6.6`, if both `--bind-ip` and `--bind- are set at the same time listen`,`--bind-ip` has higher priority. + +In addition, the `IP` part of the `--bind-ip` parameter supports specifying the `network card name`, `wildcards`, and more than one can be specified. The detailed description is as follows: + +- Specify the network card name, such as: `--bind-ip eth0:7777`, then the client accesses the `7777` port, and the egress IP is the IP of the eth0 network card. +- The network card name supports wildcards, for example: `--bind-ip eth0.*:7777`, then the client accesses the `7777` port, and the egress IP is a randomly selected one of the network card IPs starting with `eth0.`. +- IP supports wildcards, such as: `--bind-ip 192.168.?.*:7777`, then the client accesses the `7777` port, and the exit IP is all the IPs of the machine, matching the IP of `192.168.?.*` A randomly selected one. +- It can also be multiple combinations of network card name and IP, separated by half-width commas, such as: `--bind-ip pppoe??,192.168.?.*:7777`, then the client accesses the port `7777`, The outgoing IP is the machine's network card name matching `pppoe??` + It is a randomly selected one among all IPs of the machine that matches `192.168.?.*`. +- The wildcard character `*` represents 0 to any number of characters, and `?` represents 1 character. +- If the IP of the network card changes, it will take effect in real time. +- You can use the `--bind-refresh` parameter to specify the interval to refresh the local network card information, the default is `5`, the unit is second. + ### 2.8 Speed limit, connections limit The parameter `--max-conns` can limit the maximum number of connections per port. @@ -1318,6 +1361,28 @@ The `--bind-listen` parameter can be used to open the client connection with the `proxy socks -t tcp -p 2.2.2.2:33080 --bind-listen` +#### Flexible Outgoing IP + +Although the above `--bind-listen` parameter can specify the outgoing IP, the `entry IP` and ` outgoing IP` cannot be interfered by humans. If you want the ingress IP to be different from the egress IP, you can use the `--bind-ip` parameter, format: `IP:port`, for example: `1.1.1.1:8080` +, `[2000:0:0:0:0:0:0:1]:8080`. For multiple binding requirements, you can repeat the `--bind-ip` parameter. + +For example, the machine has IP `5.5.5.5`, `6.6.6.6`, and monitors two ports `8888` and `7777`, the command is as follows: + +`proxy socks -t tcp -p :8888,:7777 --bind-ip 5.5.5.5:7777 --bind-ip 6.6.6.6:8888` + +Then the client access port `7777`, the outgoing IP is `5.5.5.5`, access port `8888`, the outgoing IP is `6.6.6.6`, if both `--bind-ip` and `--bind- are set at the same time listen`,`--bind-ip` has higher priority. + +In addition, the `IP` part of the `--bind-ip` parameter supports specifying the `network card name`, `wildcards`, and more than one. The details are as follows: + +- Specify the network card name, such as: `--bind-ip eth0:7777`, then the client accesses the `7777` port, and the egress IP is the IP of the eth0 network card. +- The network card name supports wildcards, for example: `--bind-ip eth0.*:7777`, then the client accesses the `7777` port, and the egress IP is a randomly selected one of the network card IPs starting with `eth0.`. +- IP supports wildcards, such as: `--bind-ip 192.168.?.*:7777`, then the client accesses the `7777` port, and the exit IP is all the IPs of the machine, matching the IP of `192.168.?.*` A randomly selected one. +- It can also be multiple combinations of network card name and IP, separated by half-width commas, such as: `--bind-ip pppoe??,192.168.?.*:7777`, then the client accesses the port `7777`, The outgoing IP is the machine's network card name matching `pppoe??` + It is a randomly selected one among all IPs of the machine that matches `192.168.?.*`. +- The wildcard character `*` represents 0 to any number of characters, and `?` represents 1 character. +- If the IP of the network card changes, it will take effect in real time. +- You can use the `--bind-refresh` parameter to specify the interval to refresh the local network card information, the default is `5`, the unit is second. + ### 5.15 Cascade Certification SOCKS5 supports cascading authentication, and -A can set upstream authentication information. @@ -1581,6 +1646,28 @@ The `--bind-listen` parameter can be used to open the client connection with the `proxy sps -S socks -P 2.2.2.2:33080 -T tcp -Z password -l 100K -t tcp --bind-listen -p :33080` +#### Flexible Outgoing IP + +Although the above `--bind-listen` parameter can specify the outgoing IP, the `entry IP` and ` outgoing IP` cannot be interfered by humans. If you want the ingress IP to be different from the egress IP, you can use the `--bind-ip` parameter, format: `IP:port`, for example: `1.1.1.1:8080` +, `[2000:0:0:0:0:0:0:1]:8080`. For multiple binding requirements, you can repeat the `--bind-ip` parameter. + +For example, the machine has IP `5.5.5.5`, `6.6.6.6`, and monitors two ports `8888` and `7777`, the command is as follows: + +`proxy sps -t tcp -p :8888,:7777 --bind-ip 5.5.5.5:7777 --bind-ip 6.6.6.6:8888` + +Then the client access port `7777`, the outgoing IP is `5.5.5.5`, access port `8888`, the outgoing IP is `6.6.6.6`, if both `--bind-ip` and `--bind- are set at the same time listen`,`--bind-ip` has higher priority. + +In addition, the `IP` part of the `--bind-ip` parameter supports specifying the `network card name`, `wildcards`, and more than one. The details are as follows: + +- Specify the network card name, such as: `--bind-ip eth0:7777`, then the client accesses the `7777` port, and the egress IP is the IP of the eth0 network card. +- The network card name supports wildcards, for example: `--bind-ip eth0.*:7777`, then the client accesses the `7777` port, and the egress IP is a randomly selected one of the network card IPs starting with `eth0.`. +- IP supports wildcards, such as: `--bind-ip 192.168.?.*:7777`, then the client accesses the `7777` port, and the exit IP is all the IPs of the machine, matching the IP of `192.168.?.*` A randomly selected one. +- It can also be multiple combinations of network card name and IP, separated by half-width commas, such as: `--bind-ip pppoe??,192.168.?.*:7777`, then the client accesses the port `7777`, The outgoing IP is the machine's network card name matching `pppoe??` + It is a randomly selected one among all IPs of the machine that matches `192.168.?.*`. +- The wildcard character `*` represents 0 to any number of characters, and `?` represents 1 character. +- If the IP of the network card changes, it will take effect in real time. +- You can use the `--bind-refresh` parameter to specify the interval to refresh the local network card information, the default is `5`, the unit is second. + ### 6.13 Certificate parameters use base64 data By default, the -C, -K parameter is the path to the crt certificate and the key file. diff --git a/docs/manual/manual.md b/docs/manual/manual.md index 862c203..6aa9efe 100644 --- a/docs/manual/manual.md +++ b/docs/manual/manual.md @@ -502,6 +502,27 @@ The `--bind-listen` parameter can be used to open the client connection with the `proxy http -t tcp -p 2.2.2.2:33080 --bind-listen` +#### Flexible Outgoing IP + +Although the above `--bind-listen` parameter can specify the outgoing IP, the `entry IP` and the `outgoing IP` cannot be referenced artificially. If you want the ingress IP and the egress IP to be different, you can use the `--bind-ip` parameter, format: `IP:port`, for example: `1.1.1.1:8080`, `[2000:0:0:0:0 :0:0:1]:8080`. For multiple binding requirements, the `--bind-ip` parameter can be repeated. + +For example, this machine has IP `5.5.5.5`, `6.6.6.6`, and monitors two ports `8888` and `7777`, the command is as follows: + +`Proxy tcp -t tcp -p :8888,:7777 --bind-ip 5.5.5.5:7777 --bind-ip 6.6.6.6:8888 -T tcp -P 2.2.2.2:3322` + +Then the client access port `7777`, the outgoing IP is `5.5.5.5`, access port `8888`, the outgoing IP is `6.6.6.6`, if both `--bind-ip` and `--bind- are set at the same time listen`,`--bind-ip` has higher priority. + +In addition, the `IP` part of the `--bind-ip` parameter supports specifying the `network card name`, `wildcards`, and more than one can be specified. The detailed description is as follows: + +- Specify the network card name, such as: `--bind-ip eth0:7777`, and then the client accesses the `7777` port, and the egress IP is the IP of the eth0 network card. +- The network card name supports wildcards, such as: `--bind-ip eth0.*:7777`, then the client accesses the port `7777`, and the egress IP is randomly selected from the IP of the network card starting with `eth0.`. +- IP supports wildcards, such as: `--bind-ip 192.168.?.*:777`, then the client accesses the `7777` port, the outgoing IP is all the IPs of the machine, and matches the IP of `192.168.?.*` A randomly selected one. +- It can also be several combinations of network card name and IP, and several selective divisions using half-width, such as: `-bind-ip pppoe??,192.168.?.*:7777`, and then the client accesses the `7777` port , The outgoing IP is the machine's network card name matching `pppoe??` + It is randomly selected from the IP matching `192.168.?.*` in the machine IP. +- The wildcard character `*` represents 0 to any character, `? `Represents 1 character. +- If the IP of the network card changes, it will take effect in real time. +- You can use the `--bind-refresh` parameter to specify the interval to refresh the local network card information, the default is `5`, the unit is second. + ### 1.17 Certificate parameters use base64 data By default, the -C, -K parameter is the path to the crt certificate and the key file. @@ -610,6 +631,28 @@ When the TCP proxy is a superior type (parameter: -T) is tcp, it supports the sp `proxy tcp -p ":33080" -T tcp -P" 192.168.22.33:22" -B` +#### Flexible Outgoing IP + +Although the above `--bind-listen` parameter can specify the outgoing IP, the `entry IP` and the ` outgoing IP` cannot be referenced artificially. If you want the ingress IP to be different from the egress IP, you can use the `--bind-ip` parameter, format: `IP:port`, for example: `1.1.1.1:8080` +, `[2000:0:0:0:0:0:0:1]:8080`. For multiple binding requirements, you can repeat the `--bind-ip` parameter identification. + +For example, this machine has IP `5.5.5.5`, `6.6.6.6`, and monitors two ports `8888` and `7777`, the command is as follows: + +`Proxy tcp -t tcp -p :8888,:7777 --bind-ip 5.5.5.5:7777 --bind-ip 6.6.6.6:8888 -T tcp -P 2.2.2.2:3322` + +Then the client access port `7777`, the outgoing IP is `5.5.5.5`, access port `8888`, the outgoing IP is `6.6.6.6`, if both `--bind-ip` and `--bind- are set at the same time listen`,`--bind-ip` has higher priority. + +In addition, the `IP` part of the `--bind-ip` parameter supports specifying the `network card name`, `wildcards`, and more than one can be specified. The detailed description is as follows: + +- Specify the network card name, such as: `--bind-ip eth0:7777`, then the client accesses the `7777` port, and the egress IP is the IP of the eth0 network card. +- The network card name supports wildcards, for example: `--bind-ip eth0.*:7777`, then the client accesses the `7777` port, and the egress IP is a randomly selected one of the network card IPs starting with `eth0.`. +- IP supports wildcards, such as: `--bind-ip 192.168.?.*:7777`, then the client accesses the `7777` port, and the exit IP is all the IPs of the machine, matching the IP of `192.168.?.*` A randomly selected one. +- It can also be multiple combinations of network card name and IP, separated by half-width commas, such as: `--bind-ip pppoe??,192.168.?.*:7777`, then the client accesses the port `7777`, The outgoing IP is the machine's network card name matching `pppoe??` + It is a randomly selected one among all IPs of the machine that matches `192.168.?.*`. +- The wildcard character `*` represents 0 to any number of characters, and `?` represents 1 character. +- If the IP of the network card changes, it will take effect in real time. +- You can use the `--bind-refresh` parameter to specify the interval to refresh the local network card information, the default is `5`, the unit is second. + ### 2.8 Speed limit, connections limit The parameter `--max-conns` can limit the maximum number of connections per port. @@ -1112,6 +1155,28 @@ The `--bind-listen` parameter can be used to open the client connection with the `proxy socks -t tcp -p 2.2.2.2:33080 --bind-listen` +#### Flexible Outgoing IP + +Although the above `--bind-listen` parameter can specify the outgoing IP, the `entry IP` and ` outgoing IP` cannot be interfered by humans. If you want the ingress IP to be different from the egress IP, you can use the `--bind-ip` parameter, format: `IP:port`, for example: `1.1.1.1:8080` +, `[2000:0:0:0:0:0:0:1]:8080`. For multiple binding requirements, you can repeat the `--bind-ip` parameter. + +For example, the machine has IP `5.5.5.5`, `6.6.6.6`, and monitors two ports `8888` and `7777`, the command is as follows: + +`proxy socks -t tcp -p :8888,:7777 --bind-ip 5.5.5.5:7777 --bind-ip 6.6.6.6:8888` + +Then the client access port `7777`, the outgoing IP is `5.5.5.5`, access port `8888`, the outgoing IP is `6.6.6.6`, if both `--bind-ip` and `--bind- are set at the same time listen`,`--bind-ip` has higher priority. + +In addition, the `IP` part of the `--bind-ip` parameter supports specifying the `network card name`, `wildcards`, and more than one. The details are as follows: + +- Specify the network card name, such as: `--bind-ip eth0:7777`, then the client accesses the `7777` port, and the egress IP is the IP of the eth0 network card. +- The network card name supports wildcards, for example: `--bind-ip eth0.*:7777`, then the client accesses the `7777` port, and the egress IP is a randomly selected one of the network card IPs starting with `eth0.`. +- IP supports wildcards, such as: `--bind-ip 192.168.?.*:7777`, then the client accesses the `7777` port, and the exit IP is all the IPs of the machine, matching the IP of `192.168.?.*` A randomly selected one. +- It can also be multiple combinations of network card name and IP, separated by half-width commas, such as: `--bind-ip pppoe??,192.168.?.*:7777`, then the client accesses the port `7777`, The outgoing IP is the machine's network card name matching `pppoe??` + It is a randomly selected one among all IPs of the machine that matches `192.168.?.*`. +- The wildcard character `*` represents 0 to any number of characters, and `?` represents 1 character. +- If the IP of the network card changes, it will take effect in real time. +- You can use the `--bind-refresh` parameter to specify the interval to refresh the local network card information, the default is `5`, the unit is second. + ### 5.15 Cascade Certification SOCKS5 supports cascading authentication, and -A can set upstream authentication information. @@ -1375,6 +1440,28 @@ The `--bind-listen` parameter can be used to open the client connection with the `proxy sps -S socks -P 2.2.2.2:33080 -T tcp -Z password -l 100K -t tcp --bind-listen -p :33080` +#### Flexible Outgoing IP + +Although the above `--bind-listen` parameter can specify the outgoing IP, the `entry IP` and ` outgoing IP` cannot be interfered by humans. If you want the ingress IP to be different from the egress IP, you can use the `--bind-ip` parameter, format: `IP:port`, for example: `1.1.1.1:8080` +, `[2000:0:0:0:0:0:0:1]:8080`. For multiple binding requirements, you can repeat the `--bind-ip` parameter. + +For example, the machine has IP `5.5.5.5`, `6.6.6.6`, and monitors two ports `8888` and `7777`, the command is as follows: + +`proxy sps -t tcp -p :8888,:7777 --bind-ip 5.5.5.5:7777 --bind-ip 6.6.6.6:8888` + +Then the client access port `7777`, the outgoing IP is `5.5.5.5`, access port `8888`, the outgoing IP is `6.6.6.6`, if both `--bind-ip` and `--bind- are set at the same time listen`,`--bind-ip` has higher priority. + +In addition, the `IP` part of the `--bind-ip` parameter supports specifying the `network card name`, `wildcards`, and more than one. The details are as follows: + +- Specify the network card name, such as: `--bind-ip eth0:7777`, then the client accesses the `7777` port, and the egress IP is the IP of the eth0 network card. +- The network card name supports wildcards, for example: `--bind-ip eth0.*:7777`, then the client accesses the `7777` port, and the egress IP is a randomly selected one of the network card IPs starting with `eth0.`. +- IP supports wildcards, such as: `--bind-ip 192.168.?.*:7777`, then the client accesses the `7777` port, and the exit IP is all the IPs of the machine, matching the IP of `192.168.?.*` A randomly selected one. +- It can also be multiple combinations of network card name and IP, separated by half-width commas, such as: `--bind-ip pppoe??,192.168.?.*:7777`, then the client accesses the port `7777`, The outgoing IP is the machine's network card name matching `pppoe??` + It is a randomly selected one among all IPs of the machine that matches `192.168.?.*`. +- The wildcard character `*` represents 0 to any number of characters, and `?` represents 1 character. +- If the IP of the network card changes, it will take effect in real time. +- You can use the `--bind-refresh` parameter to specify the interval to refresh the local network card information, the default is `5`, the unit is second. + ### 6.13 Certificate parameters use base64 data By default, the -C, -K parameter is the path to the crt certificate and the key file. diff --git a/docs/sitemap.xml b/docs/sitemap.xml index 9facd59..5ae94c9 100644 --- a/docs/sitemap.xml +++ b/docs/sitemap.xml @@ -17,12 +17,6 @@ 2019-06-14T16:29:13+08:00 - - https://snail007.host900.com/goproxy/tags/cdn/ - 2019-07-05T08:20:48+08:00 - 0 - - https://snail007.host900.com/goproxy/categories/ 2019-07-05T08:20:48+08:00 @@ -47,6 +41,12 @@ 0 + + https://snail007.host900.com/goproxy/tags/cdn/ + 2019-07-05T08:20:48+08:00 + 0 + + https://snail007.host900.com/goproxy/tags/cloudflare/ 2019-07-05T08:20:48+08:00 diff --git a/docs/tags/cdn/index.html b/docs/tags/cdn/index.html index a7beca7..e9d7646 100644 --- a/docs/tags/cdn/index.html +++ b/docs/tags/cdn/index.html @@ -14,7 +14,7 @@ - CDN - GOPROXY IN ACTION + cdn - GOPROXY IN ACTION @@ -77,7 +77,7 @@
-

CDN

+

cdn

diff --git a/docs/tags/cdn/index.xml b/docs/tags/cdn/index.xml index cb5d91a..ab1a975 100644 --- a/docs/tags/cdn/index.xml +++ b/docs/tags/cdn/index.xml @@ -1,9 +1,9 @@ - CDN on GOPROXY IN ACTION + cdn on GOPROXY IN ACTION https://snail007.host900.com/goproxy/tags/cdn/ - Recent content in CDN on GOPROXY IN ACTION + Recent content in cdn on GOPROXY IN ACTION Hugo -- gohugo.io zh-CN Fri, 05 Jul 2019 08:20:48 +0800 diff --git a/docs/tags/index.xml b/docs/tags/index.xml index cd84ea7..311e588 100644 --- a/docs/tags/index.xml +++ b/docs/tags/index.xml @@ -12,7 +12,7 @@ - CDN + cdn https://snail007.host900.com/goproxy/tags/cdn/ Fri, 05 Jul 2019 08:20:48 +0800