How to reuse OLINK AS9929 GRE tunnel to provide optimized network transfer for all VPS

Host Information has previously introduced how to use OLINK's GRE tunnel to optimize server backhaul routing. However, the GRE tunnel product must be bound to the server IP that needs to be optimized. One package can only provide network optimization for one server. If you want to change the server, you need to Send a work order and let customer service change the IP address.

These restrictions give people a headache. Is there any way to optimize all of my server networks by buying just one GRE tunnel package?

Amway links:

First of all, thank you KB boss for providing good products. If you want to try it, you can buy it yourself. Triple network backhaul AS9929 GRE tunnel port speed————Traffic——————Price 100Mbit————100GB————2USD/Month300Mbit————300GB————6USD/Month500Mbit ————500GB————10USD/Month Choose the appropriate package according to the host location that needs to access the GRE tunnel. If you are a European server, buy the Frankfurt package. If you are an American server, buy the San Jose package: Frankfurt regional link :https://www.olink.cloud/ clients/cart.php?pid=17San Jose area link: https://www.olink.cloud/clients/cart.php?pid=18

Tutorial link:

Spend one dollar to transfer all VPS backhaul routes. The principle is to connect a vps to the optimized tunnel of as9929 first, and then use this vps to provide transfer to all other servers. Since mjj is only for people who want to be lazy, it is impossible to use it, so the blogger has written a forwarding program for mjj who wants to be lazy, making it easy to get started.

Required conditions: One olink gre tunnel package, one VPS for forwarding, and N VPS to be connected to the optimized network

Forward VPS:

Tips: Please turn off the system firewall before use, systemctl stop firewalld.

1. Download the forwarding program and grant execution permission wget tutu.ovh/bash/olink-mgre/mgre;chmod +x mgre2. Create an olink tunnel./mgre olink3. Create a tunnel between the forwarding server and the server to be optimized Tunnel name: You can forward the server tunnel IP at will: just set it to 10.0.1.x, which means setting an unoccupied tunnel subnet IP. Tunnel IP of the server to be optimized: Set it to 10.0.1.x, which means setting an unoccupied tunnel subnet IP. ./mgre forward {tunnel name} {forwarding server tunnel IP} {forwarding server public network IP} {server tunnel IP to be optimized} {server public network IP to be optimized} For example: ./mgre forward virmach1 10.0.1.2 119.118.117.116 10.0 .1.3 45.35.25.15./mgre forward virmach2 10.0.1.4 119.118.117.116 10.0.1.5 46.36.26.16

VPS1 to be optimized network:

1. Download the forwarding program and grant execution permission wget tutu.ovh/bash/olink-mgre/mgre;chmod +x mgre2. Create a tunnel between the server to be optimized and the forwarding server. Tunnel name: Keep it consistent with the forwarding server Forwarding server tunnel IP: Set it to 10.0.1.x, which means setting an unoccupied tunnel subnet IP. Server tunnel IP to be optimized: Keep it consistent with the tunnel IP assigned when the forwarding server is executed./mgre client {tunnel name} {forwarding server tunnel IP} {forwarding server public network IP} {server tunnel IP to be optimized} {server public to be optimized Network IP} For example: ./mgre client virmach1 10.0.1.2 119.118.117.116 10.0.1.3 45.35.25.15

VPS2 to be optimized network:

wget tutu.ovh/bash/olink-mgre/mgre;chmod +x mgre./mgre client {tunnel name} {forwarding server tunnel IP} {forwarding server public network IP} {server tunnel IP to be optimized} {to be Optimize the server public IP} For example: ./mgre client virmach2 10.0.1.4 119.118.117.116 10.0.1.5 46.36.26.16

VPSN of the network to be optimized:

The steps are the same as above.

Big and small packet diversion module (experimental function):

Since AS9929 traffic is expensive, you can choose to optimize only small packets. Small packet scenarios include: dynamic web pages/remote connections/DNS requests/online games, file downloads/online videos/data transmission and other large packet scenarios, take the normal route.< /p>

Enable small packet offloading module: ./mgre client_rules_add Remove small packet offloading module: ./mgre client_rules_remove Test large and small packet return routing: ./mgre client_traceroute

Other operations (please perform them on the corresponding server):

Remove the forwarding server tunnel: ./mgre forward_remove {tunnel name} Remove the server tunnel to be optimized: ./mgre client_remove Remove the olink tunnel on the forwarding server: ./mgre olink_remove

2021/04/30 update: Fixed a bug and added a forwarder startup task. 2021/04/30 update: I was so excited before get off work that I rmted the source code with a shake of my hand. I’ll just use it if the program is not updated. 2022/09/07 update: Zombie fraud update, new experimental function: small packet diversion. AS9929 high-end lines are expensive and have low traffic, causing independent servers to lose the advantage of large bandwidth. This function solves this problem very well. 2022/10/01 update: Added the error of ignoring the SSL certificate, corrected the error description in the tutorial, added notes, and fixed the problem of not cleaning up some configurations when removing the forwarding tunnel.

Recommended site searches: ip purchase, nationwide mixed server, dynamic vps second ip change, domain name check, vps host, free virtual host, godaddy space, me domain name registration, dynamic vps second ip change, Wanwang domain name registration official website ,