udppm(8)

NAME
udppm - UDP port mapper

SYNOPSIS
udppm [-ds] [-l[[@]logfile]] [-iinternal_ip] [-eexternal_ip] local_port remote_host remote_port

DESCRIPTION
udppm forwards datagrams from local to remote UDP 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 datagrams 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 datagrams to. By default, connections to any interface are accepted. It's usually unsafe.

-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  Single packet. By default, only one client can use the udppm service, but if -s is specified, only one packet will be forwarded between client and server. This allows the service to be shared between multiple clients for single-packet services (for example, name lookups).

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

ARGUMENTS

local_port
    - port udppm accepts datagrams on

remote_host
    - IP address of the host datagrams are forwarded to

remote_port
    - remote port datagrams are forwarded to

CLIENTS
Any UDP-based application can be used as a client. Use internal_ip and local_port as the destination in the client application. All datagrams are 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>