update

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.  

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.  

docs/sitemap.xml

@@ -18,31 +18,31 @@
   </url>
   
   <url>
-    <loc>https://snail007.host900.com/goproxy/tags/cdn/</loc>
+    <loc>https://snail007.host900.com/goproxy/categories/</loc>
     <lastmod>2019-07-05T08:20:48+08:00</lastmod>
     <priority>0</priority>
   </url>
   
   <url>
-    <loc>https://snail007.host900.com/goproxy/categories/</loc>
+    <loc>https://snail007.host900.com/goproxy/</loc>
     <lastmod>2019-07-05T08:20:48+08:00</lastmod>
     <priority>0</priority>
   </url>
   
   <url>
-    <loc>https://snail007.host900.com/goproxy/</loc>
+    <loc>https://snail007.host900.com/goproxy/posts/</loc>
     <lastmod>2019-07-05T08:20:48+08:00</lastmod>
     <priority>0</priority>
   </url>
   
   <url>
-    <loc>https://snail007.host900.com/goproxy/posts/</loc>
+    <loc>https://snail007.host900.com/goproxy/tags/</loc>
     <lastmod>2019-07-05T08:20:48+08:00</lastmod>
     <priority>0</priority>
   </url>
   
   <url>
-    <loc>https://snail007.host900.com/goproxy/tags/</loc>
+    <loc>https://snail007.host900.com/goproxy/tags/cdn/</loc>
     <lastmod>2019-07-05T08:20:48+08:00</lastmod>
     <priority>0</priority>
   </url>

docs/tags/cdn/index.html

@@ -14,7 +14,7 @@
     <link href="//maxcdn.bootstrapcdn.com/font-awesome/4.5.0/css/font-awesome.min.css" rel="stylesheet">
     <link rel="stylesheet" href="//maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css">
     <link rel="stylesheet" href="//cdnjs.cloudflare.com/ajax/libs/highlight.js/8.4/styles/solarized_dark.min.css">
-    <title>CDN - GOPROXY IN ACTION</title>
+    <title>cdn - GOPROXY IN ACTION</title>
     
     <link href="https://snail007.host900.com/goproxy/css/styles.css" rel="stylesheet">
     
@@ -77,7 +77,7 @@
 
     
     <header class="page-header">
-      <h1>CDN</h1>
+      <h1>cdn</h1>
     </header>
     
 

docs/tags/cdn/index.xml

@@ -1,9 +1,9 @@
 <?xml version="1.0" encoding="utf-8" standalone="yes" ?>
 <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
   <channel>
-    <title>CDN on GOPROXY IN ACTION</title>
+    <title>cdn on GOPROXY IN ACTION</title>
     <link>https://snail007.host900.com/goproxy/tags/cdn/</link>
-    <description>Recent content in CDN on GOPROXY IN ACTION</description>
+    <description>Recent content in cdn on GOPROXY IN ACTION</description>
     <generator>Hugo -- gohugo.io</generator>
     <language>zh-CN</language>
     <lastBuildDate>Fri, 05 Jul 2019 08:20:48 +0800</lastBuildDate>

docs/tags/index.xml

@@ -12,7 +12,7 @@
     
     
     <item>
-      <title>CDN</title>
+      <title>cdn</title>
       <link>https://snail007.host900.com/goproxy/tags/cdn/</link>
       <pubDate>Fri, 05 Jul 2019 08:20:48 +0800</pubDate>