Smart Hub 2 - cannot get basic port-forwarding to function

[CC4096]

Hello,

I have a Smart Hub 2 (model number GRV9517UAC34-A-SA) running firmware v0.45.00.08028-BT. I have tried unsuccessfully to set up a simple port-forward to allow a small web-server to be reachable from the wider internet. To do this I have forwarded port 80 external to port 80 internal using the Firewall.

My web server is live and will deliver pages correctly (over port 80) to machines on the local (192.168.1.x) network. However, port-forwarding to the 'outside' internet doesn't work at all; attempts at connection just time out. My method of testing is to point a browser to the 'Broadband IP address' the router reports. However, nothing is seen, just an eventual timeout. Even a commercial 'check my site' website reports the same condition - 'no response'.

I contacted BT Support through their app and we ran through the port-forward rule setup process again together, but it still did not work after that.

I would like to get this working. I'd be grateful for any help or insight. I'm assuming because all the necessary functionality seems to be present in the hub, it 'can' work, it just doesn't.

Thanks.

[licquorice]

If you are attempting to access your public IP address via your LAN it won't work. Try using a mobile via 4/5G

[WSH]

“However, port-forwarding to the 'outside' internet doesn't work at all;”

I may have misunderstood you here, but port-forwarding is not about forwarding things to the outside world, it’s about forwarding incoming traffic to the correct service inside your network, so of course it doesn’t work.

[CC4096]

I'm sorry, I wrote this carelessly. I meant to say that ports are not being forwarded to internal services running on machines on the local network when accessed from the wider internet.

[CC4096 · Accepted solution]

In any case, I have managed to solve this problem. It turns out my internal machine (running various services I wished to be accessible from 'outside' via port-forwarding) had the default gateway misconfigured. Once the default gateway on the server was set to 192.168.1.254 everything worked as expected.