Using udpgw over a TCP connection about badvpn HOT 2 CLOSED

Hey.

I don't know what you're talking about, the truth is almost the opposite.
The udpgw daemon listens on TCP, not UDP. And the UdpGwClient communicates
with the daemon through an abstract stream. When UdpGwClient is used from
tun2socks (the only place it's used), it's used via SocksUdpGwClient, which
will connect to the udpgw daemon through the same SOCKS server that
tun2socks forwards TCP connections through (and this is still a SOCKS CONNECT command, i.e. TCP!).

If you only want to tunnel UDP through TCP, and don't want to set up a
dummy SOCKS server, you can implement a class akin to SocksUdpGwClient, but
which would establish TCP connections directly, not through SOCKS.

from badvpn.

Oh interesting, thank you! I am trying to force all of my traffic over USB (TCP) via libusbmuxd.h, for my iPhone tethering project.

The current design is like this:

1. Run a SOCKS server on the iPhone on port 8123
2. Run TetherMac on local computer to listen for TCP connections on port 8000, pretending to be a SOCKS server
3. Use libusbmuxd to tunnel SOCKS connections directed towards mac:8000 to iphone:8123 instead.

So far applications that fully support SOCKS can be pointed at mac:8000 as long as they also rely on the SOCKS proxy for DNS lookups. However this clearly doesn't work for applications that don't speak SOCKS, so I have been trying to figure out how to use tun2socks to tunnel all my traffic through this TCP-only SOCKS connection.

I am still having trouble getting tun2socks to work on OS X, even disregarding UDP support. I'll open a separate issue about that, but I am using this fork with utun OS X fixes by @linusyang

from badvpn.