Hi,
My SmartHub is used only for the purpose of passing through a broadband connection to my main Router (TP Link BE550) and for digital voice. Until the transfer to digital voice, the SmartHub was not even used in my network setup.
Recently our alarm system has stopped connecting to its cloud service (RISCO Cloud) and opening the required ports on the TP Link router won't solve the issue as the WAN IP address of that router is not a public IP address, but a private IP address given by the SmartHub. Essentially it means I have a double NAT situation which I am guessing the alarm cloud service now doesn't like.
However everything on the SmartHub is switched off (WiFi, Firewall etc) so I am little perplexed as to why there is an issue. Could there be something else the SmartHub is doing? I am thinking that setting the DMZ (if possible) on the SmartHub to the TP Link Router should do the trick as then everything would be wide open to that device even though that's essentially what I thought was in place anyway by turning the SmartHub Firewall off.
Is there anything else on the SmartHub side I might have missed? All other cloud services continue to work as normal.
Many thanks
You could try putting the Tp Link in the DMZ of the Smart Hub, you will still be double natting though.
However, I'm not sure why an outbound service requires ports opening or does the alarm system expect to receive unsolicited connections from the cloud?
I have contacted the company to understand better how their cloud service works but I know the suggestion is that the IP module of the alarm system uses the ports 33000 out, 34000 in and to have these open. Putting the TP Link in the DMZ of the Smart Hub is the only way I can think of doing it but as you note, if it's a double NAT issue (as we used to have back in the day with the original XBox Live service that didn't like it), I am not sure what else can be done.
The only other solution would be to bypass my internal network and connect the alarm device direct to the SmartHub which is not a neat solution as it means running cables manually.
Other than the blistering fast WiFi on your TP-Link router, are you using any of it's other advanced features? If not you could always put it into AP mode and leave the BT router in charge of the network. You might even be able to get the SH2 performing NAT and have the BE550 manage the majority of the local IP table, so you don't have to worry about the idiot SH2 and it's inability to perform DHCP garbage disposal (unlike any other router in the last 15 years)