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
Last revision Both sides next revision
gre_tunnel [2021/04/24 13:19]
cubebuilder
gre_tunnel [2021/04/24 13:20]
cubebuilder
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 136: 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.
 +
  
 ===== Restarting your GRE Tunnel After Rebooting ===== ===== Restarting your GRE Tunnel After Rebooting =====
Line 142: Line 139:
  
 Your distribution of choice (like Debian) may have hooks in ''/etc/network/interfaces'' to bring your GRE tunnels up at boot time but that's outside the scope of this guide. Your distribution of choice (like Debian) may have hooks in ''/etc/network/interfaces'' to bring your GRE tunnels up at boot time but that's outside the scope of this guide.
 +
 +===== 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]]