Smart Hub Pro Hairpin NAT

[Keezza]

Is it possible for the Smart Hub Pro to have hairpin NAT allowing external IP calls from inside the network. Just with previous routers on Virgin Media this was possible. Allowing me to seamlessly use my CCTV inside and out of the network. 

[bobpullen]

Is this something you're yet to try, or have you tried and found it not to be working?

I'm not sat at my Smart Hub Pro at the moment but I'm sure I've seen this working with some of the servers I have hosted on my local network.

What cameras do you have and what device/app are you using to access them? How are the cameras/connecting device connected to the hub? Wired or Wi-Fi? Anything connected via extenders? 

[Keezza]

They're connected wired via switch on Smart Wifi Pro (Extender) using xeoma as camera host. and DDNS via NOIP updated by Smart Hub Pro. 

Just doesn't seem to resolve back to internal ip inside the network. It will work fine outside of the network, Just a pain changing the address inside and out.

[bobpullen]

Differs a little to my setup as I don't have anything wired to my extender (all my wired connections are via switches to the hub). Easy enough to give it a go though.

When inside the network, how's the device connected that you're trying to access the feeds from? Wired to extender as well?

[Keezza]

A variety of ways. All have the same result 

[bobpullen]

I checked mine quickly (host desktop machine wired to hub, connecting laptop wireless to hub) and can reach a locally hosted Windows RDP server using its public IP address.

[bobpullen]

@Keezza - I've revisited this and it seems it's not quite as clear cut as my last reply.

I have a desktop wired to my network via a couple of unmanaged switches. My Smart WiFI Pro extender is wired to the same switch as the desktop.

I have spun up a web server on the desktop and made it accessible to the outside world via domain name/dynamic DNS and the findings are interesting 🤔

If the device I am using is connected wirelessly to my Smart Hub Pro then NAT loopback is working and I can access the website without issue using its domain name.

However, if the device I am using is connected wirelessly to my Smart WiFi Pro then NAT loopback does not seem to be working and I cannot access the website via its domain name, only its local IP address.

So for me, the problem only seems to be evident if the connecting device is going via my extender rather than hub. I wonder how this compares to what you're seeing?

[Keezza]

Thanks for your extensive testing. It's not just me. For now I went with the process of just changing the address in vs out on the client side. When I get time I may do a work around in line with what you mentioned.

Be great if EE could update their firmware though!

[bobpullen]

Thanks @Keezza - I'd be interested to know if things work for you when the connecting device is associated with the hub rather than the extender? One way to check would be to take the device next to the hub and toggle the Wi-Fi connection on the device off/back on.

If you still have problems, then perhaps the rabbit hole goes a little deeper, and the fact that your cameras are attached to the extender is also contributing to things (in my setup the server is connected to the hub).

Either way, agree it looks like a bug.