Forum Discussion
NAT/forwarding issues while gaming/streaming
Hey guys, I'm new here... I just got my gateway in yesterday... I must say, I'm highly disappointed and I only wish I researched this further before I ordered it...I've already done multiple searches on this topic, so I'm not gonna ask the question I've been wanting to ask which was: "Why isn't my connection open NAT?", or "Why can't I port forward?". I've pretty much answered all of those questions myself by simply searching. I have taken it upon myself to call T-mobile's tech support anyways in the event that somehow a miracle is sent my way....
Fortunately for me, a very kind gentleman by the name of Alex, employee number 786457, assured me that they will be fixing the problem within a 48 hour period. I was told there will be some Beta software sent to my unit "possibly". And yes, that was the word used... Not sure how far I can believe that, seeing as how a lot of you are having issues. But anyway, this is my journey. I will post some updates here n there to let y'all know the outcome. Worst case scenario this causes me to vacate the community & the service entirely. Because this is probably one of the largest handicaps any network can have, it's almost like having parental control without it actually being implemented. Stay tuned folks, I'll let you know what happens.
Hopefully this "beta" program isn't bullcucky.
Probably getting "spammed" because very specific questions were not getting answered.
The true problem has always been tied to unsolicited inbound traffic properly getting through the perimeter network layers... even with the local router set to open/forward inbound packets, those packets were still getting filtered/blocked further up the chain. Basically, it is making the consoles think you have a different NAT type than you actually have. When it comes to truly unsolicited inbound traffic (not coming back in from a previous outbound communication), it was still getting blocked at a higher level. All of this was confirmed back on the Askey modems... the ones that gave us local control over both DMZ and port traversal.
djb14336 wrote:
Probably getting "spammed" because very specific questions were not getting answered.
The true problem has always been tied to unsolicited inbound traffic properly getting through the perimeter network layers... even with the local router set to open/forward inbound packets, those packets were still getting filtered/blocked further up the chain. Basically, it is making the consoles think you have a different NAT type than you actually have. When it comes to truly unsolicited inbound traffic (not coming back in from a previous outbound communication), it was still getting blocked at a higher level. All of this was confirmed back on the Askey modems... the ones that gave us local control over both DMZ and port traversal.
The above video literally just answered every question on this thread.
So your response is basically null and void.
On second thought, I'm glad this video is up now. So, anyone past this point in the discussion that is complaining has nobody to blame but themselves. You're basically a laughing stock.
Alright then, that's a wrap. Good game, and if you can't follow simple directions then you deserve zero port forwarding abilities.
💀
Actually, it does not answer the specific questions being asked.
What goes in in that video is still a workaround.
It is not a native fix to the problem.
As in a firmware update that in and of itself solves the problem end to end.
You posted that tmobile fixed the problem for you, presumably by updates from their end.
Not that a reverse proxy approach solved it (as in third party tools).
You were asked for firmware details, port details, a means to confirm end to end unsolicited inbound port forwarding was actually working properly (as can be tested with the likes of Shieldsup or speedguide.net).
https://www.speedguide.net/scan.php
THAT is likely why people kept pinging you.
I already had my extensive back and forth over the issues with both parties. Realized they were not willing to move away from their XLAT464 anytime soon (which is stated by design specifically to break this functionality). I ran the numbers and decided it wasn't worth the extra headaches and costs, even though there was a viable solution available through my personal router, and managed to set up a better deal with an ISP that does it properly.
Anonymous wrote:
A "specific question" was answered. And that's how to (paraphrasing here) work around the problem. If you honestly think that you will find a "fix" for a cellular data connection not giving you a static IPv4 connection... Then I don't know what to tell you. In my honest opinion, workarounds are the only absolute thing you've got right now. Go call the FCC and tell them how butthurt you are.
You're the one butthurt about people replying to you. Next time don't create a whole forum if people may experience the same problems as you bozo.
Would need a third party service that will allow you to forward packets back to your local router/devices.
Nater Tater has a YT video up about a reverse proxy tou can set up... there are other similar products with varying degrees of complexity to set up.
A more straight forward approach may be a VPN service that allows port forwarding.
There is the dedicated approach for gaming like WTFast that have been built into some routers (lime Asus, and they may support Netgear too?)... but those often tend to be limited a their own list of supported games (though, they do cover the more popular ones out there).
There is a "normal" VPN though, Windscribe, that you can set up to "reserve" an IP (not permanently, it will still renew and rotate periodically, but with much longer leases). It allows you to assign up to 10 ports to forward. Got to Features,, then click the link about static IP's to readout on it all..
They also provide scripts for installing the service on personal routers (with a supported OS like Tomato, DDWRT, Merlin, etc. that can also be installed on consumer brands like Netgear, Linksys, and Asus, among others) so your whole network can take advantage of it (like consoles, streaming boxes, etc.). Nite that the cost will vary depending on how you set up the IP reservation... it costs more to have access to more locations, etc. so you will want to read up on it all.
Go through all the options thoroughly if you want to go down this path. It is going to cost extra, and want to make sure you understand what you are getting into up front.
Having the same issue with the new sagecom 5688 gateway I hope the come up with some kind of update for it.
I called and they said they couldn’t change the NAT and there was nothing I could do.
Yep, same here. One of my devices cannot connect to the cloud and I talked to Tech Support, answer is that they 'may' do something about it in the future. I have a work order to end my TMO Home Internet at the end of this billing period. I guess TMO is looking to capture just the low hanging fruit for now.
