Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
gre_tunnel [2021/04/24 13:18]
cubebuilder
gre_tunnel [2021/04/24 13:20]
cubebuilder
Line 30: Line 30:
 In this document we'll only be covering a Linux GRE tunnel configuration.  In this document we'll only be covering a Linux GRE tunnel configuration. 
  
-This guide will work 100% on both our KVM, and OpenVZ based plans.+This guide will work 100% on our KVM Slices.
  
 ===== Prerequisites ===== ===== Prerequisites =====
Line 96: Line 96:
 iptables -t nat -A POSTROUTING -s 192.168.168.0/30 ! -o gre+ -j SNAT --to-source YOUR_FILTERED_IP iptables -t nat -A POSTROUTING -s 192.168.168.0/30 ! -o gre+ -j SNAT --to-source YOUR_FILTERED_IP
 </code> </code>
-===== GRE Configuration for Pterodactyl/Docker===== 
-Running Pterodactyl or Docker and want to protect your docker container? 
-[[gre_tunnel:docker|Click here for GRE Configuration for Pterodactyl/Docker]] 
  
 ===== Test Outbound Connections ===== ===== Test Outbound Connections =====
Line 135: Line 132:
  
 At this point you should be able to connect to ''YOUR_FILTERED_IP'' and the destination port with your application and get passed through the GRE tunnel without issue. At this point you should be able to connect to ''YOUR_FILTERED_IP'' and the destination port with your application and get passed through the GRE tunnel without issue.
 +===== GRE Configuration for Pterodactyl/Docker=====
 +Running Pterodactyl or Docker and want to protect your docker container?
 +
 +[[gre_tunnel:docker|Click here for GRE Configuration for Pterodactyl/Docker]]
  
 ===== Restarting your GRE Tunnel After Rebooting ===== ===== Restarting your GRE Tunnel After Rebooting =====