Roughly 70% of mobile carriers in Southeast Asia quietly throttle UDP traffic the moment they sniff it — and most people never realize it until their game rubber-bands at 300ms ping or a WhatsApp call drops mid-sentence. That gap is exactly what a free SSH UDP BadVPN setup fills. It’s old-school, slightly nerdy, and yes — it still works in 2026.
I’ve been running this combo on and off since 2018, mostly on crappy hotel Wi-Fi and campus networks that block everything except port 443. Let me save you the six hours I wasted on trial and error.
What BadVPN Actually Does Inside Your SSH Tunnel
Here’s the thing most tutorials skip: SSH only forwards TCP. That’s it. Your UDP packets — game traffic, DNS queries, voice calls — get dropped at the tunnel entrance like they never existed.
BadVPN’s udpgw module fixes that. It’s a small UDP gateway that wraps your UDP packets inside a TCP stream, pushes them through the SSH tunnel, and unwraps them at the other end. Default listen port is 7300, and you’ll see that number everywhere in free SSH configs.
On the server side, the command looks like this:
badvpn-udpgw --listen-addr 127.0.0.1:7300 --max-clients 1000 --max-connections-for-client 10
You don’t run this yourself — the SSH provider does. Your only job is pointing your client at that port. Simple.
Why This Setup Still Matters in 2026
Fair question. A premium VPN is one tap and done, so why bother?
Three reasons, in my experience. Learn more about V2rayNG Android Setup Guide.
- It looks like normal HTTPS. SSH over port 443 with a proper SNI is nearly invisible to deep packet inspection. Commercial VPN protocols get fingerprinted fast.
- Captive portals hate VPNs but allow SSH. Hotel and campus Wi-Fi regularly block VPN handshakes yet let port 443 through untouched.
- Gaming latency on mobile data. UDP forwarding through a nearby SSH node often shaves 40–80ms versus a congested free VPN server.
Cost? Zero. A free SSH account plus a free app. That’s it.
The 7-Step Setup, In Order
Follow this sequence. Skipping ahead is how people end up with a tunnel that connects but loads nothing.
- Grab a free SSH account. You need host, port (
22or443), username, password, and the expiry. Check whether the provider also lists a UDPGW host — usually the same hostname on port7300. - Install your client. HTTP Injector, HTTP Custom, NekoBox, or v2rayNG depending on your device. On desktop, plain OpenSSH plus a local
udpgwbinary works. - Create the SSH profile. Pick port
443if your network is strict (it disguises as HTTPS), otherwise22. Enter credentials, set connection timeout to15seconds. - Enable UDP forwarding. In HTTP Injector: SSH settings → UDP Forwarding → set host to
127.0.0.1and port to7300. In NekoBox: SSH outbound → UDP over TCP → port7300. - Add a payload or SNI if required. Many networks need a fake HTTP header to let the initial handshake through. Dropbear on port
143is a common workaround — it mimics IMAP. - Connect and test. Open a terminal and run
ping 8.8.8.8, or check DNS resolution withnslookup google.com. If those respond cleanly, UDP forwarding is alive. - Lock in the config. Enable auto-reconnect, save the profile, and test on mobile data before trusting it on a trip.
Payload or SNI — Do You Need Both?
No. Pick one. Payload injection works on older Android clients; SNI splitting is cleaner and what most modern setups use now. Running both usually breaks the handshake.
Which App Fits Your Device
Quick breakdown, based on what I actually use:
- HTTP Injector (Android) — easiest for beginners, UDP gateway baked in, free tier is enough.
- NekoBox (Android) — best for mixed setups, handles SSH plus VMess plus WireGuard in one profile list.
- v2rayNG — great for Xray configs, but no native SSH UDP gateway. Skip it for pure BadVPN work.
- OpenSSH + local badvpn (Windows/Linux/macOS) — the most reliable option if you’re on a laptop and don’t mind the terminal.
Tip: if your tunnel connects but games still lag, 90% of the time you forgot to enable UDP forwarding in the client. Check that first before blaming the server.
Mistakes That Quietly Kill Your Speed
I’ve made every one of these. Learn from my pain.
- Using a server 8,000km away because it was the only free slot left — ping penalty is brutal.
- Leaving
--max-clientsdefault on busy shared servers. Nothing you can fix, but expect volatility during peak hours. - Forgetting MTU. Drop it to
1400if large packets fail and connections stall halfway. - Running two VPN apps at once. Android will let you, and the result is a black hole of dropped traffic.
Small stuff. Big impact. For more on this, see NekoBox Android Guide 2026.
Picking a Free SSH Provider Without Burning an Afternoon
Most “free SSH” sites are dead links or ad farms. What you want is a provider that publishes a clear UDPGW host, offers 3–7 day accounts, and doesn’t force you through five redirect pages.
If you’re serious about uptime, consider spinning up your own tiny VPS — a cheap box with a bargain-shelf domain and a Let’s Encrypt cert gives you total control over port 443, 7300, and the payload. It costs less than a coffee per month and beats any shared free node. If you also want somewhere to stash your config backups, any basic cloud storage account works fine for that.
Either way, keep your configs synced somewhere safe. Losing a working payload you spent two hours tuning is a special kind of painful.
My Honest Take
After years of testing, I’d skip the sketchy free-account listings and go straight to a service that actually maintains its UDP gateway — it’s the difference between a tunnel that connects and one that performs. Start with a free account at claudessh.com, set up your first profile in ten minutes, and test it on mobile data before trusting it anywhere important.
Then tune from there. That’s the whole game.
If this server is full, RouterSSH SSH UDP is another option with 6,500+ servers across 196 countries.
