docs: add warnings for power cycling after subnet changes

Author: aleksander-rudolf

docs/guides/initial-setup.md

@@ -144,6 +144,9 @@ Internet is routed in via a port on the top of the LoadSync(tm) panel.
 
         See the corresponding [Starlink guide](https://starlink.com/support/article/5f5f34ab-2e08-7ce8-75cf-7460597c485c?srsltid=AfmBOorBoLGz3ePovEWVkdK29sqUwtk8VgfQXaH3I_4T8BDdWLI3rXvY).
 
+        !!! warning
+            After changing the subnet, you will need to power down and power up the loadcenter so that the miners and other IoT devices can fetch their updated IP's from the DHCP server.
+
 === "LTE Modem"
 
     !!! tip "Connecting Internet"
@@ -168,6 +171,9 @@ Internet is routed in via a port on the top of the LoadSync(tm) panel.
         The default is `192.168.1.1/24`, which is very common in residential routers, and can cause overlaps.
         If the subnet in the loadcenter overlaps with your local subnet, some features of LoadSync(tm) (such as the Tailscale integration) may not work properly.
 
+        !!! warning
+            After changing the subnet, you will need to power down and power up the loadcenter so that the miners and other IoT devices can fetch their updated IP's from the DHCP server.
+
 === "Other"
 
     !!! tip "Connecting Internet"
@@ -180,6 +186,9 @@ Internet is routed in via a port on the top of the LoadSync(tm) panel.
         The default is `192.168.1.1/24`, which is very common in residential routers, and can cause overlaps.
         If the subnet in the loadcenter overlaps with your local subnet, some features of LoadSync(tm) (such as the Tailscale integration) may not work properly.
 
+        !!! warning
+            After changing the subnet, you will need to power down and power up the loadcenter so that the miners and other IoT devices can fetch their updated IP's from the DHCP server.
+
 ## Startup
 
 === "Hash Huts"