tcppm(8)

NAME
tcppm - TCP port mapper

SYNOPSIS
tcppm [-d] [-l[[@]logfile]] [-iinternal_ip] [-eexternal_ip] local_port remote_host remote_port

DESCRIPTION
tcppm forwards connections from local to remote TCP port

OPTIONS

-I  Inetd mode. Standalone service only.

-d  Daemonize. Detach service from console and run in the background.

-t  Be silenT. Do not log start/stop/accept error records.

-e  External address. IP address of the interface the proxy should initiate connections from. By default, the system will decide which address to use in accordance with the routing table.

-niPATH
    (Linux only) Switch to the network namespace identified by PATH before opening the listening socket. The current namespace is saved and restored immediately after binding, so outgoing connections run in the original namespace unless -ne is also given.

-nePATH
    (Linux only) Switch to the network namespace identified by PATH after the listening socket has been bound (and after restoring from -ni if applicable). Both options accept any namespace file path (e.g. /var/run/netns/myns or /proc/PID/ns/net) and require CAP_SYS_ADMIN.

-i  Internal address. IP address the proxy accepts connections to. By default, connections to any interface are accepted. It's usually unsafe. Unix domain sockets can be specified with -iunix:/path/to/socket syntax (e.g., -iunix:/var/run/tcppm.sock). On Linux, abstract sockets use -iunix:@socketname syntax.

-l  Log. By default logging is to stdout. If logfile is specified logging is to file. Under Unix, if '@' precedes logfile, syslog is used for logging.

-S  Increase or decrease stack size. You may want to try something like -S8192 if you experience 3proxy crashes.

ARGUMENTS

local_port
    - port tcppm accepts connections on

remote_host
    - IP address of the host the connection is forwarded to. Unix domain sockets can be specified with the syntax unix:/path/to/socket (e.g., unix:/var/run/app.sock). On Linux, abstract (fileless) Unix sockets use the syntax unix:@socketname (e.g., unix:@app.socket).

remote_port
    - remote port the connection is forwarded to. Ignored when using Unix socket destination, but must be specified (use any positive value) for syntax compatibility.

CLIENTS
Any TCP-based application can be used as a client. Use internal_ip and local_port as the destination in the client application. The connection is forwarded to remote_host:remote_port

BUGS
Report all bugs to 3proxy@3proxy.org

SEE ALSO
3proxy(8), proxy(8), ftppr(8), socks(8), pop3p(8), udppm(8), syslogd(8),
https://3proxy.org/

AUTHORS
3proxy is designed by Vladimir Dubrovin <vlad@3proxy.org>