topic Re: Smart Hub Pro - weird port forwarding problem in Broadband & Landline

Smart Hub Pro - weird port forwarding problem

Saccheri — Sun, 03 Nov 2024 22:50:26 GMT

Hi. Just moved from BT to EE with the Smart Hub Pro. A set-up which was working on the BT router, doesn't on the Smart Hub Pro.

The Smart Hub Pro connects to a switch, behind which are two computers. One is a web server and port forwarding rules are setup. From outside the network, everything is working fine - I can connect via my domain name and hit the web server. So port forwarding is working fine.

However, inside my network - the second computer connected to the switch can't connect to the web server using the domain name. I can connect using the raw internal IP address.

Now if I take this computer and plug it directly into another port on the Smart Hub Pro (so no longer going through the switch), I can connect to the web server using the domain name! I've tried lots of switches, managed and unmanaged (to try and rule out any physical port isolation going on) but the behaviour is consistent.

My OCD hates the idea of using raw IPs inside the LAN and domain names outside or running a second cable from the office to the hall - have a missed something basic?

Thanks

Re: Smart Hub Pro - weird port forwarding problem

XRaySpeX — Sun, 03 Nov 2024 23:14:21 GMT

What domain name? You aren't given 1, are you? And DDNS is not supported on the EE SH Pro.

Re: Smart Hub Pro - weird port forwarding problem

CamtasticVision — Mon, 04 Nov 2024 07:23:35 GMT

Just wondering if the router is being used for your DNS, I would most certainly change it and try again. Have to wonder why you choose to host your own domain these days as hosting is so cheap, I have two dedicated servers running and even that's not expensive I actually couldn't run one of my servers cheaper per month than the price I would pay for my electric.

Re: Smart Hub Pro - weird port forwarding problem

XRaySpeX — Mon, 04 Nov 2024 07:29:29 GMT

@CamtasticVision : The EE SH Pro does not facilitate changing of DNS.

Re: Smart Hub Pro - weird port forwarding problem

CamtasticVision — Mon, 04 Nov 2024 07:31:54 GMT

He would simply change the DNS on his PC not the router, or he could run his own DNS server or lets face it make an entry in his HOSTS file pointing to the IP

Re: Smart Hub Pro - weird port forwarding problem

XRaySpeX — Mon, 04 Nov 2024 07:35:24 GMT

@CamtasticVision : True!

Re: Smart Hub Pro - weird port forwarding problem

Saccheri — Mon, 04 Nov 2024 08:51:57 GMT

Thanks for the replies all.

I have my own domain name with scripts on an Ubuntu server to update my Cloudflare DNS entries if the EE router changes WAN IP address. This all works fine. Outside the house, port forwarding is working - and I can reach all the services with my domain name.

The Smart Hub Pro has the WAN connection and one port to a 8 way switch under the stairs. Any computer connected to that switch CAN'T connect to the servers using the domain name. Anything on Wifi can connect and if I connect via another port on the Smart Hub Pro, that also works.

Hardcoding the hosts file on all the laptops and computers should work. Bit of a pain, but an option.

Hosting is generally cheap - unless your son runs a minecraft server with 128GB of RAM and Core i7-13700K!

Re: Smart Hub Pro - weird port forwarding problem

CamtasticVision — Mon, 04 Nov 2024 09:08:03 GMT

If they connect via IP it will remove a few ms to not use the DNS, the side effect is they might have a slight edge over the other players 😁

Re: Smart Hub Pro - weird port forwarding problem

Saccheri — Sat, 09 Nov 2024 16:06:38 GMT

Right. Think I know what's going on. To recap, I have a domain name and DDNS keeping that in-synch with the router's (dynamic IP address). With the BT homehub, inside my LAN, I can connect to port-forwarded services using this domain name. The Smart Hub Pro drops these packets on the physical port they arrive on.

To try and prove this, I replaced the entire Smart Hub Pro with a firewall appliance running OPNsense. That had the same behaviour 😶

After a week of reading manuals/Wireshark, it seems the behaviour the Smart Hub Pro is doing is correct. Routers are not expecting to see inbound (to the routers public IP) coming from the LAN side of things, so even this firewall appliance was dropping the packets. On the firewall appliance you can set up "NAT reflection" settings to get things working, but that's not the best way to solve this (apparently) - LAN traffic should stay on the LAN etc etc.

So to solve this, I've setup an override in the OPNsense DNS service. So anybody on the LAN using my domain name - get directed straight to the LAN server IP address.

Would I recommend a dedicated firewall appliance/OPNsense over the Smart Hub Pro? No. Its cool and clever, but its been a long week to get it stable and working for me and ended up with mini-server room of flashing lights I'm scared to leave on overnight 🤣

Re: Smart Hub Pro - weird port forwarding problem

bobpullen — Sat, 09 Nov 2024 16:45:51 GMT

@Saccheri - in order for the hub to route out/back in to your hosted services it will need to support NAT loopback/hairpinning. I'd expect the Smart Hub Pro to behave the same as your BT hub in this regard to be honest so it's interesting that it doesn't. I have a set up not that disimilar to yours so will make a note to see if I'm able to replicate the problem.

@XRaySpeX wrote:
And DDNS is not supported on the EE SH Pro.

Dynamic DNS is supported on the SH Pro.

Re: Smart Hub Pro - weird port forwarding problem

Saccheri — Sat, 09 Nov 2024 17:00:09 GMT

If the computer making the request and the end server were on different physical LAN ports at the back of the Smart Hub Pro, then things worked (or if the client PC was on Wifi). Only when they share the same physical LAN port with a (downsteam) switch, then the packets got dropped.

Maybe I messed something simple up. Tried many switches - managed and unmanaged - same behaviour which to me seemed to point to the Hub.

But then this new, fancy firewall appliance had the same behaviour as well. Maybe old routers just were more tolerant. Seems this problem is reported weekly on the OPNsense forums with more modern kit.