Differences

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

--- networking:ziggo:changed-ip [2024/09/13 06:42] – oscar
+++ networking:ziggo:changed-ip [2026/08/30 06:48] (current) – oscar
@@ Line 1: / Line 1: @@
 ====== Changed Ziggo IP ======
-===== IPv6 change =====
+----
+===== Introduction =====
+On the main OpenWrt router a sccript is running every 2 hours to detect a change in assigned IPv4 and IPv6 addresses. It compares the current system IP addresses with what is recorded in the DNS. Information about the installation, setup and script can be found at: [[networking:openwrt:ip-change-detect|OpenWrt IP monitoring]]. This page describes the corrective actions in case a change is detected.
+===== IPv4 Change - Actions =====
+When Ziggo change our IPv4 address. The following steps are required:
+  - Check via external website what our used IPv4 is
+  - Check if our router has this already new IP address: Network/Interfaces/WAN/IPv4
+  - Update the TransIP A record with the new IP of the webserver
+===== IPv6 Change - Actions =====
 When Ziggo change our IPv6 range/subnet, all server already received their new IP address via SLAAC (subnet delegation). Our most important external IPV6 address is our webserver (also needed for LetsEncrypt certificate renewal). When this changes the following updates need to be done on TransIP and our main router/firewall
 The following steps are required:
@@ Line 8: / Line 20: @@
   - On the router update: network/firewall/traffic rules --> Allow-HTTPS-ipv6 to new address of webserver
-===== IPv4 change =====
+Note that the routers IPv6 WAN address is different / outside of the Prefix Delegation (PD) range!
-When Ziggo change our IPv4 address. The following steps are required:
-  - Check via external website what our used IPv4 is
-  - Check if our router has this already new IP address: Network/Interfaces/WAN/IPv4
-  - Update the TransIP A record with the new IP of the webserver