NAT (Forwarding) in T-Mobile Gateway

inteller wrote:

I can't use noip with t-mobile because it doesn't support it, but if it was just bridging I could.

 

I'm not willing to wait around for another device when the speeds I get right now are just fine and the device I have is capable of the functions I need.

Sorry, you're incorrect.  You can setup NOIP on other devices other than just your modem.  I set it up on my local server.  But, this doesn't work as T-Mobile doesn't assign you a unique IP address (it's shared with hundreds/thousands of other people).  So even if you setup NOIP, that doesn't help one bit.  Nor would port forwarding or bridge mode.

You're failing to understand the problem.  The issue is how the T-Mobile network is setup for a security aspect.  It was setup to be a secured network for phones.  It's not capable of working with a DDNS service, bridge mode, or port forwarding.  That's why they disabled these features on the T-Mobile modem, as they would never work.  Keep in mind that Nokia added these features to this modem firmware when they designed it (for other markets).  When T-Mobile wanted to use it, they had to disable features as they don't work on their network, not because they wanted to limit the device.

The new modem won't resolve the problem either.  It may happen along with a T-Mobile network change, but a modem alone can't fix the problem, either a firmware update or new hardware.  The only work-around is a service like ZeroTier until T-Mobile changes their network, which very well may never happen.