User Profile
EricNorcal
Network Novice
Joined 2 years ago
User Widgets
Contribuciones
Re: NAT (Forwarding) in T-Mobile Gateway
I can't edit my post above, but I got the ports backward in this sentence: So now I can reach port 8000 on the 192.168.1.2 device from the outside world from gateway.host.net:8500. You would reach port 8500 on the LAN device via port 8000 on the internet host; my last example got the ports correct.5Visto0likes0ComentariosRe: NAT (Forwarding) in T-Mobile Gateway
It is possible to expose ports, but of course only on your IPv6 address. No, it not possible to expose ports, even for IPv6 addresses, if you are using the gateway they gave me. There is no provision for inbound routing at all; all inbound access is blocked. I can't verify what they do for local IPv6 connections currently (DHCPv6 with SLAAC?), but the addresses assigned on the inside network were either not globally routable, or they are blocked at the router (for good reason). So your only choice for accessing a device/devices on the internal network of a T-Mobile Home/Business Gateway is through port forwarding through an external host, like ngrok or ssh forwarding through a server on which you have an account.4Visto0likes0ComentariosRe: NAT (Forwarding) in T-Mobile Gateway
phenomdadon wrote: EricNorcal wrote: Could you run thru a quick setup?? I'm jus tryna to game on my pc and Tmobile internet is blocking some of my games from connecting. I'm usingPersistent SSH which is and alternative to autossh. It would be much appreciated. You'll need to have these two settings enabled on the ssh server into which you are setting up the tunnels: ClientAliveInterval 60 ClientAliveCountMax 2 Without these, the ssh connection will eventually die, even with something like autossh (presumably also Persistent SSH). Then there is a tunnel per device/port from some ssh host on your LAN (like a Raspberry Pi or whatever) to the ssh out on the internet which you will be using as a gateway: autossh -N -p22 -R *:8000:192.168.1.2:8500 user@gateway.host.net That command sets up a tunnel between your Raspi (or whatever) on your LAN to the gateway machine, with a port 8000 tunnel to the 192.168.1.2 device on your LAN on port 8500. So now I can reach port 8000 on the 192.168.1.2 device from the outside world from gateway.host.net:8500. For example, if you want to be able to ssh on a device 192.168.1.33 (on port 22), then you could set up: autossh -N -R *:8222:192.168.1.33:22 user@gateway.host.net and then you can do "ssh -p8222 root@gateway.host.net" and you will be ssh'd to root@192.168.1.33 on port 22.4Visto0likes0ComentariosRe: NAT (Forwarding) in T-Mobile Gateway
Just another success story here, if you're the type who knows how to use SSH tunneling. T-Mobile (business, in my case; don't think it matters) can't do port forwarding. But my ssh tunnel(s) worked, at least for a little bit. I use autossh, which re-establishes connections when they fail (due to routing changes, etc). It has been very reliable for me in the past to get around bad/broken NAT situations. But I found that my ssh tunnels would only last for a short time (Arkadyan modem, using a router on the LAN connection). Then I read from another post somewhere else on this forum that t-mobile simply closes TCP connections without traffic after a period of time (looks like maybe as short as 5m). So I changed the ssh settings on my server to add a keep-alive, and all is working perfectly. I have three ports forwarded on my LAN through an ssh connection to a server in the cloud; you could probably use ngrok for this (free accounts I think). I have a camera, ssh to a server, and another port forward to an IoT device, and all three have been working perfectly without interruption for over a week. I get between 120 and 250Mbps down and 30up pretty consistently. I'm sold, and am currently on hold cancelling my AT&T DSL account!2Visto0likes0Comentarios