# Sky FTTP via BT ONT Dropping WAN Connection When IP Renews

**URL:** <https://forum.gl-inet.com/t/sky-fttp-via-bt-ont-dropping-wan-connection-when-ip-renews/72176>\
**Category:** VPN, DNS, Leaks\
**Created:** [October 19, 2026, 1:33pm UTC](https://forum.gl-inet.com/t/sky-fttp-via-bt-ont-dropping-wan-connection-when-ip-renews/72176 "2026-10-19T13:33:51Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![MrListerSir](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/mrlistersir/32/34304_2.png) [@MrListerSir](https://forum.gl-inet.com/u/MrListerSir)\
**Post date:** [October 19, 2026, 1:33pm UTC](https://forum.gl-inet.com/t/sky-fttp-via-bt-ont-dropping-wan-connection-when-ip-renews/72176/1 "2026-10-19T13:33:51Z")

</div>

I have this issue when Sky renews my public facing IP roughly every 56 days and if I am not around the Flint2 router will fail to re-negotiate a new IP and stay in the 100.x.x.x range.

I have come across a potential work-around but I've not tested it yet and wanted to post it here for someone at GL-iNET to confirm this is the best work-around for me?

**[Automatically Renew via a Cron Watchdog Script](https://forum.openwrt.org/t/lte-dhcp-doesnt-renew-ip-after-lease-time/188956)**

To prevent this issue from happening when you aren't around, you can create a lightweight watchdog script on the Flint 2 that tests for internet connectivity and auto-renews the WAN connection if the connection drops after an IP change.

1. SSH into your Flint 2.

2. Create a script file in an appropriate persistent directory:

3. Paste the following automated script (press `i` to enter insert mode in `vi`):

4. Save and exit (press `ESC`, then type `:wq` and hit `Enter`).

5. Make the script executable:

6. Add it to the system router scheduler (Cron) so it runs every 2 to 5 minutes:

7. Enable and restart the cron daemon to register the task: [[1](https://gist.github.com/protyposis/b7b06e99410d81de688c)]

Thanks

---

<div class="post-metadata">

**Author:** ![PoweredByVeg](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/poweredbyveg/32/25044_2.png) [@PoweredByVeg](https://forum.gl-inet.com/u/PoweredByVeg)\
**Post date:** [October 19, 2026, 2:09pm UTC](https://forum.gl-inet.com/t/sky-fttp-via-bt-ont-dropping-wan-connection-when-ip-renews/72176/2 "2026-10-19T14:09:50Z")

</div>

Technically it’s Openreach ONT and not BT, could be confusing to some people.

---

<div class="post-metadata">

**Author:** ![MrListerSir](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/mrlistersir/32/34304_2.png) [@MrListerSir](https://forum.gl-inet.com/u/MrListerSir)\
**Post date:** [October 19, 2026, 2:22pm UTC](https://forum.gl-inet.com/t/sky-fttp-via-bt-ont-dropping-wan-connection-when-ip-renews/72176/3 "2026-10-19T14:22:17Z")

</div>

> [@PoweredByVeg](#):
>
> Openreach ONT and not BT

Open Reach is owned by BT, but regardless shouldn't distract people from the issue, a quick Google of ONT is obvious what we're talking about.

---

<div class="post-metadata">

**Author:** ![charles2](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/c/9dc877/32.png) [@charles2](https://forum.gl-inet.com/u/charles2)\
**Post date:** [October 24, 2026, 2:38am UTC](https://forum.gl-inet.com/t/sky-fttp-via-bt-ont-dropping-wan-connection-when-ip-renews/72176/5 "2026-10-24T02:38:53Z")

</div>

Hi,

Thank you for sharing this script.

From another related discussion, it appears that your Sky FTTP connection may be using MAP-T. I am not very familiar with this type of connection, based on my understanding, these are some of my thoughts.

The script checks IPv4 connectivity by pinging `8.8.8.8` and runs `ifup wan` if the ping fails. While this may help if the issue is related to the WAN interface, it may not be sufficient if the problem is related to MAP-T.

In a MAP-T setup, `wan6` typically obtains the IPv6 configuration and MAP-T parameters, while `wan6_4` provides the MAP-T IPv4 path. If the issue is related to MAP-T configuration or the `wan6_4` interface, restarting `wan` may not restore IPv4 connectivity. It may be worth investigating whether restarting `wan6` could help in this situation.

Hope these thoughts are helpful, and thank you for sharing your findings with the community.
