tcptoudp, udptotcp: tunnels between TCP and UDP
C/C++ CI Linux / ${{ matrix.target }} (ubuntu-24.04-arm) (push) Has been cancelled
C/C++ CI Linux / ${{ matrix.target }} (ubuntu-latest) (push) Has been cancelled
C/C++ CI MacOS / ${{ matrix.target }} (macos-15) (push) Has been cancelled
C/C++ CI Windows / ${{ matrix.target }} (windows-2022) (push) Has been cancelled
C/C++ CI cmake / ${{ matrix.target }} (macos-15) (push) Has been cancelled
C/C++ CI cmake / ${{ matrix.target }} (ubuntu-24.04-arm) (push) Has been cancelled
C/C++ CI cmake / ${{ matrix.target }} (ubuntu-latest) (push) Has been cancelled
C/C++ CI cmake / ${{ matrix.target }} (windows-2022) (push) Has been cancelled
C/C++ CI cmake / ubuntu-latest (wolfSSL) (push) Has been cancelled

Datagrams on a TCP connection, each with a two byte length in network
order in front of it, which is how udptunnel (the rfc1036 one) and
ProxyGuard (eduVPN) put them there, the framing alone or after a
handshake: udptunnel's 32 bytes, or ProxyGuard's HTTP Upgrade for
UoTLV/1 answered with 101 Switching Protocols.

tcptoudp takes the connections, a UDP socket of its own to the target
for each, the handshake a client speaks recognised by its first bytes
and answered; a parent the ACL gives is a SOCKS5 UDP relay, as for
udppm. udptotcp takes the datagrams, each client a session of the
service's with a TCP connection of its own, connected as the service's
loop sees it writable (dnspr asks a name server over TCP the same way);
-m sends udptunnel's handshake to the target, -m2 ProxyGuard's, -m0
(the default) none, so both ends of either tool are stood in for.

The service names take two places of the string table, the default
configuration path moving two later (stringtable[27]).

Built by the Makefiles and CMake, with the standalone binaries, and
installed by them; a case of the test suite speaks all three handshakes.
This commit is contained in:
Vladimir Dubrovin committed 2026-11-15 16:03:15 +03:00
1 parent 79583d7aa7
commit 51559e12c4
21 files changed
+1043 -28

No files matched your search

+28 -1
View File
@@ -79,6 +79,14 @@ Recursion is not allowed.
.B udppm
[options]
\fI<SRCPORT>\fR \fI<DSTADDR>\fR \fI<DSTPORT>\fR
.br
.B tcptoudp
[options]
\fI<SRCPORT>\fR \fI<DSTADDR>\fR \fI<DSTPORT>\fR
.br
.B udptotcp
[options]
\fI<SRCPORT>\fR \fI<DSTADDR>\fR \fI<DSTPORT>\fR
.br
Descriptions:
.br
@@ -127,6 +135,25 @@ but must be specified for syntax compatibility.
.B udppm
UDP portmapper
.br
.B tcptoudp
TCP to UDP tunnel: connections on SRCPORT carry datagrams, each with a
two byte length in network order in front of it, sent as UDP datagrams
to DSTADDR:DSTPORT, the answers framed the same way back. The handshake
a client speaks \(em udptunnel's (the rfc1036 one) or ProxyGuard's HTTP
Upgrade for UoTLV/1 (eduVPN) \(em is recognised and answered; a
connection that begins with a length needs none. Each connection has a
UDP socket of its own to the target.
.br
.B udptotcp
UDP to TCP tunnel: each client sending datagrams to SRCPORT is a session
of the service with a TCP connection of its own to DSTADDR:DSTPORT, its
datagrams sent on it with a two byte length in front of each, what comes
back answered to the client. \fB-m\fR sends udptunnel's handshake to the
target first, \fB-m2\fR ProxyGuard's (an HTTP Upgrade for UoTLV/1), \fB-m0\fR
sends none, which is the default.
.br
Options:
.br
@@ -2085,7 +2112,7 @@ the tree is refused outright.
Report all bugs to
.BR 3proxy@3proxy.org
.SH SEE ALSO
3proxy(8), 3proxy_crypt(8), proxy(8), ftppr(8), socks(8), pop3p(8), imapp(8), smtpp(8), tlspr(8), tcppm(8), udppm(8), syslogd(8),
3proxy(8), 3proxy_crypt(8), proxy(8), ftppr(8), socks(8), pop3p(8), imapp(8), smtpp(8), tlspr(8), tcppm(8), udppm(8), tcptoudp(8), udptotcp(8), syslogd(8),
.br
https://3proxy.org/
.SH AUTHORS