Forum Discussion
NAT (Forwarding) in T-Mobile Gateway
I recently signed up for T-Mobile internet, and I am VERY disappointed that I could not even forward NAT traffic to my home security system. I saw that this was discussed 7 months ago in a previous...
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 using Persistent 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.
