doc/html/man8/udppm.8.html
NAME
SYNOPSIS
DESCRIPTION
OPTIONS
ARGUMENTS
CLIENTS
BUGS
SEE ALSO
AUTHORS
udppm - UDP port mapper
udppm [-ds] [-l [[@]logfile]] [-i internal_ip] [-e external_ip] local_port remote_host remote_port
_ udppm _ forwards datagrams from local to remote UDP port
| |
-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.
| | |
-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.
|
local_port
remote_host
remote_port
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
Report all bugs to [email protected]
3proxy(8), proxy(8), ftppr(8), socks(8), pop3p(8), udppm(8), syslogd(8),
https://3proxy.org/
3proxy is designed by Vladimir 3APA3A Dubrovin ([email protected])