You finally got your SSH tunnel running. Web browsing works, YouTube loads, everything looks fine — then you open a game, a voice call, or a DNS query and it all falls apart. Nothing loads. The connection just hangs there like it forgot what it was doing. That’s the classic sign your tunnel is only carrying TCP traffic, and UDP is being dropped somewhere along the way. This ssh udp badvpn tutorial free walkthrough fixes exactly that problem, without you paying for anything.
I’ve been setting up tunnels since the days of plain Squid proxies, and BadVPN UDPGW is still one of the cleanest ways to push UDP through an SSH connection. No magic. Just a small gateway running on the server side and a client that knows where to send the packets.
What SSH UDP BadVPN Actually Does
Quick breakdown before we touch any config. SSH tunnels are TCP-only by design. That’s fine for HTTP, but UDP is a different animal — games, QUIC-based browsing, VoIP, and some DNS lookups all depend on it. When UDP has nowhere to go, your tunnel feels “half working.”
BadVPN’s udpgw component solves this by acting as a relay. Your client wraps UDP packets inside the TCP tunnel, ships them to the server, and udpgw unwraps them and forwards them to the real destination. On the way back, the same thing happens in reverse. Simple concept, huge practical difference.
Three moving parts you’ll deal with:
- The SSH account — host, port, username, password. Ports
22,443,80,109, and143are the usual suspects. - The UDPGW daemon — runs on the server, listens on a port like
7300or7200. - The client app — HTTP Injector, NekoBox, v2rayNG, HA Tunnel Plus, or whatever you prefer.
Why This Still Matters in 2026
You’d think UDP tunneling would be obsolete by now. Nope. If anything it’s more relevant. More apps are switching to QUIC and HTTP/3, which ride on UDP — so a TCP-only tunnel breaks more things than it did five years ago. Browsers feel sluggish. Games disconnect at the loading screen.
Then there’s network filtering. Plenty of mobile carriers and campus networks throttle UDP aggressively or block it outright. Running your traffic through port 443 over SSH, with UDP wrapped inside, slips past a surprising amount of that.
Honestly, this is the single biggest upgrade you can make to a free SSH setup. Bigger than switching apps. Bigger than tweaking payloads.
The 7-Step Setup, Start to Finish
Here’s the part you came for. Follow these in order and don’t skip step 2 — that’s where most people get stuck.
Grab a free SSH account. Any reputable free SSH provider works. Note the hostname, the SSH port, your username, and password. Test it first with a plain terminal:
ssh -D 1080 -N -C user@host. If that hangs, the account is dead and nothing else will fix it.Make sure a UDPGW daemon is running server-side. Most free SSH providers already run one on
7300,7200, or7300variants. Ask support or check their docs. If you’re on your own VPS, install BadVPN and start it manually.Start the gateway yourself if needed. On a VPS with root access:
badvpn-udpgw --listen-addr 127.0.0.1:7300 --max-clients 1000 --max-connections-for-client 10 --client-connect-timeout 60Learn more about 7 Best Free SSH Apps for.Run it inside
screenor a systemd unit so it survives logout.Install your client app. On Android, HTTP Injector and HA Tunnel Plus are the friendliest. NekoBox or v2rayNG if you want more control. On desktop, SSH + a local UDP forwarder does the job.
Enter the SSH credentials in the app. Host, port, username, password — plus a payload or SNI if your provider requires one. Keep the payload short and realistic; giant custom payloads cause more failures than they fix.
Point the UDP forwarder at port 7300. In HTTP Injector this sits under the SSH settings as “UDP Forward” or “UDPGW Port.” Set it to
7300(or whatever your server uses) and leave the address as127.0.0.1.Connect and verify. Start the tunnel, then test with something UDP-dependent — a DNS lookup, a game login, or a voice call. If it connects, you’re done. If it doesn’t, check step 2 again.
For more on this, see ClashMeta Android.
Tip: if UDP works but everything feels slow, lower --max-connections-for-client to 5 and raise the timeout instead. Fewer parallel connections often beat more.Client Apps Worth Installing
Android
HTTP Injector is the classic and still my default recommendation for beginners — the UDP forward field is right there in the SSH menu, no hunting required. HA Tunnel Plus is a close second and handles reconnect logic a bit better on flaky mobile data. NekoBox is the power-user pick if you want per-app routing alongside your tunnel.
Desktop
You don’t need a GUI. A combination of ssh -D for SOCKS plus a local UDP relay binary gets you there. WireGuard users can also layer it underneath for cleaner routing, though that’s a different setup entirely.
Mistakes That Waste Your Time
I’ve made all of these. Learn from my pain.
- Assuming the server has UDPGW. Nine times out of ten, this is the actual problem. Verify before you touch anything else.
- Using port 22 when it’s blocked. Try
443or80. Same tunnel, different door. - Forgetting the local address. The UDPGW address is
127.0.0.1, not your server’s public IP. The tunnel handles the rest. - Testing with the wrong app. Plain web browsing won’t tell you anything. Use a UDP-heavy app or a DNS query.
- Stacking two tunnels. SSH inside another VPN usually breaks UDP forwarding entirely. Pick one path.
Free vs Paid: Where the Line Sits
Free SSH accounts are fine for testing and light use. The catch is shared bandwidth, random disconnects, and daemons that go down without warning. If you’re doing anything that matters — remote work, client calls, long sessions — a cheap VPS with your own BadVPN instance is the smarter move. You control the ports, the client limits, and the uptime.
Personally, I’d rather pay a few dollars for a small server and a cheap domain for documentation than fight a free host’s downtime at 11 PM. A VPN premium subscription is another route, but most of them don’t let you hand-tune UDPGW ports the way SSH + BadVPN does.
Some things genuinely don’t need the paid tier though. Testing a config? Free account, free tunnel, done in ten minutes.
My Take
If you want the shortest path to a working UDP tunnel, start with a free SSH account from a provider that already runs UDPGW on 7300 — then spend your energy on payload tuning, not server setup. That’s the setup I keep coming back to after years of overcomplicating things.
You can grab a free account and test the whole flow at claudessh.com — spin one up, run through the seven steps above, and see for yourself whether UDP forwarding finally makes your tunnel feel complete.
For an alternative, RouterSSH VMess provides the same protocol with no sign-up and servers ready in under a minute.
