Sky Hub and TPlink AX73 Router dont auto connect after Sky Hub reboot.

[GuyTrem]

Hi All

Recently got Sky Gig Fibre installed ..replacing Starlink. 

The setup was, Starlink Router with the Ethernet Adapter. TPlink AX73 router connected to Ethernet adapter and plugged in the WAN port of the TPlink . TPlink set to dynamic IP mode for Internet . The TPlink is used for all wifi traffic in the house...so the route is wifi into TPlink. Out of the TPlink WAN port into Starlink router and out to internet.  All works fine. Importantly if the Starlink Router reboots, the TPlink reestablishes the WAN link automatically as soon as the Starlink router is up. 

New setup is exactly the same , but replacing the Starlink with the SKy SR203 hub. So the Openreach cable goes into the WAN port on the Sky Hub and the WAN port on the TPlink is plugged into one of the 3 ports on the back of the sky hub. 

All works fine...nice and fast etc....EXCEPT that if the SKy hub reboots, the TPlink doesnt automatically reestablish the WAN link once the SKy hub is up . I have to log into the TPlink and Release/Renew the IP addrees for the WAN link. 

Any Ideas....my thoughts are to make the TPlink a reserved address on the SKy Hub and then set the WAN to a Static link on the TPlink ..I might even take this link out of the DHCP address range. eg:

Sky hub IP address 192.168.0.1

Static ip link for TPlink set to 192.168.0.2

DHCP address range starts at 192.168.0.3

MAke the gateway on the TPlink 192.168.0.1 etc

Will this work do you think ?

[JimM1]

@GuyTrem Just leave the AX and the sky as they are, find the IP that the Sky router is giving to the Tp at present, goto the advanced lan section on the Sky router, there you make the Tp-Link a static IP with what it has just now or another of your choice as long as the IP is not in use. Then you can test and see what is happening!

[GuyTrem]

Think I have sorted it. 

I made the TP link a reserved ip address on the sky hub, and then set the TP link to static IP for the WAN and used the reserved ip address from the sky hub. This way the tplink doesnt wait for the DHCP service from the Sky Hub to give it an IP address, it just uses the static one I inputted. Similarly the Sky hub always expects the TP link the use this address...

Seems to work fine. 

I even thought about taking the static IP address out of the DHCP address range but decided against it just incase the sky box didnt like it. 

[Chrisee]

@GuyTrem in practice either approach will work they are essentially just missing out the delay while the Sky hub DHCP server starts up after a  reboot. General point is you.should only need to restart your Sky hub very occasionally certainly not more than once a month they are best just left connected 24/7. Sky will update firmware etc but that happens pretty rarely after the girst few days.

[GuyTrem]

@Chrisee 

yes..in an ideal world I would just like to leave the settings as default and the TP-Link on Dynamic IP , as I did with the Starlink. However for some reason the Sky Hub and TP-link dont want to play ball. I did a test and even after 45 mins the TP-link was still waiting for the internet. I had to manually release and then renew the IP address on its WAN port for it to pick up the DHCP assigned address from the Sky Hub and connect. 

Its not idea setting the WAN to static IP and reserving the address on the Sky Hub...but if it means a speedy reconnect then fine. 

The last thing I want is an unscheduled reboot on the Sky Hub when I am away ...and the rest of the house network ( the TP-link) doesnt come back up...the kids and wife wouldnt be happy !

[JimM1]

@GuyTrem Got to keep them all off your back, and if the Tp-Link needs it, then that's the way to go.