Three Home Broadband blocks incoming connections

[Ihuss]

Does anyone know why Three blocks incoming connections on their 5G Home Broadband network and how I can circumvent this?

I need to be able to remotely access devices such as NAS, Media server, DVR/NVR, VPN, etc hosted on my home network which was I was able to easily do before with previous ISPs (like Virgin Media, Sky, BT). I have the 5G Outdoor Hub set as IP Passthrough/Modem mode but the traffic is not even reaching my internal firewall router and Three Technical Support said they can't help as it's not supported to port forward and I can cancel my contract within the 30 day cooling off period. 

[PeteG]

Hey there. 

Incoming connections shouldn't be blocked. It's likely you're having the issue due to the IP address changing or something like that. You should be able to resolve the issue by running a DDNS service. Also, you will need to make sure that you're using the 3internet APN on your Hub, as that's the only one that'll give you a dedicated IP address without using CGNAT. 

Pete.

[clivejo]

The '3internet' APN has never given a "dedicated IP address", it assigns a dynamic public IP address and changes anytime the connection is broken.  When I reboot my router, and it reconnects on the network I get assigned a different public IP.  A "dedicated IP address" does not change, and is permanently assigned to your router.

[AdamCG]

Hi Pete, I am hitting the same issue as the others above. And it seems to be less an issue of blocking connections and more that the 5G outdoor hub is not truely behaving like a modem in IP passthrough mode. It is still running the firewall (according to comments above) and in my case it is changing the IP address. this change in IP address (and the fixes attempted above) highight that the device forces us into a double-NAT scenario if we want to use our own routers etc.

How can the device settings be set to ensure that it is not doing it's own NAT, and all of that can be left to my router/firewall?

[Barnbow_Tech]

Sad to hear this issue is still not resolved and others (like AdamCG) are still seeing the issue :-(. I would have thought it was a bug that had been sent back to the manufacturer (GreenPacket) and fixed by now.