aboutsummaryrefslogtreecommitdiffstats
path: root/doc/update-gre-address.md
diff options
context:
space:
mode:
authorGravatar Christian Hesse <mail@eworm.de>2020-03-27 22:15:43 +0100
committerGravatar Christian Hesse <mail@eworm.de>2020-03-27 22:15:43 +0100
commit54a8f2839dd32d9c8bd60c2edbbca3606b250bbb (patch)
treeb8164b53f21696c30869ca2b4c3699efd3eb1579 /doc/update-gre-address.md
parenta87fbb4be1e1e090b01db9eebd7799a0e1d62771 (diff)
parent1d93e92dcda753b855e89295f74dafae4743bb80 (diff)
Merge branch 'documentation'
Diffstat (limited to 'doc/update-gre-address.md')
-rw-r--r--doc/update-gre-address.md38
1 files changed, 38 insertions, 0 deletions
diff --git a/doc/update-gre-address.md b/doc/update-gre-address.md
new file mode 100644
index 0000000..870759e
--- /dev/null
+++ b/doc/update-gre-address.md
@@ -0,0 +1,38 @@
+Update GRE configuration with dynamic addresses
+===============================================
+
+[◀ Go back to main README](../README.md)
+
+Description
+-----------
+
+Running a GRE tunnel over IPSec with IKEv2 is a common scenario. This is
+easy to configure on client, but has an issue on server side: client IP
+addresses are assigned dynamically via mode-config and have to be updated
+for GRE interface.
+
+This script handles the address updates and disables the interface if the
+client is disconnected.
+
+Requirements and installation
+-----------------------------
+
+Just install the script:
+
+ $ScriptInstallUpdate update-gre-address;
+
+... and add a scheduler to run the script periodically:
+
+ / system scheduler add interval=30s name=update-gre-address on-event="/ system script run update-gre-address;" start-time=startup;
+
+Configuration
+-------------
+
+The configuration goes to interface's comment. Add the client's IKEv2
+certificate CN into the comment:
+
+ / interface gre set comment="ikev2-client1" gre-client1;
+
+---
+[◀ Go back to main README](../README.md)
+[▲ Go back to top](#top)