3proxy.cfg +
3proxy.cfg 3proxy configuration file
Common +
Common
structure:
Configuration file is a text file 3proxy reads configuration
from. Each line of the file is a command executed
@@ -51,12 +51,12 @@ command line. Additional space characters are ignored. Think
about 3proxy as "application level router" with
console interface.
Comments:
+
Comments:
Any line beginning with a space character or ´#´
character is a comment. It´s ignored. <LF>s are
ignored. <CR> is the end of a command.
Quotation:
+
Quotation:
The quotation character is " (double quote). Quotation
must be used to quote spaces or other special characters. To
use a quotation character inside a quoted string, the
@@ -65,7 +65,7 @@ to use HELLO "WORLD" as an argument, you should
write it as "HELLO ""WORLD""".
Good practice is to quote any argument you use.
File inclusion: +
File inclusion:
You can include file by using $FILENAME macro (replace
FILENAME with a path to file, for example
@@ -80,10 +80,10 @@ commands (like userlist, network lists, etc). To use dollar
sign somewhere in argument it must be quoted. Recursion is
not allowed.
Next commands +
Next commands start gateway services:
-proxy +
proxy
[options]
socks [options]
pop3p [options]
@@ -119,7 +119,7 @@ destination, the port number is ignored but must be
specified for syntax compatibility.
udppm UDP portmapper
Options:
+
Options:
-pNUMBER change default server port to NUMBER
-6 Only resolve IPv6 addresses. IPv4 addresses are
@@ -286,16 +286,16 @@ FTP client does it for you. That is, if you use 3proxy with
authentication use proxyuser:proxypassword:FTPuser as FTP
username, otherwise do not change original FTP user name
include +
include
<path>
Include config file
config +
config
<path>
Path to configuration file to use on 3proxy restart or to
save configuration.
writable +
writable
ReOpens configuration file for write access via Web
interface, and rereads it. Usually should be first command
@@ -303,10 +303,10 @@ on config file but in combination with config it can be used
anywhere to open alternate config file. Think twice before
using it.
end
+
end
End of configuration
log +
log
[[@|&]logfile] [<LOGTYPE>]
sets logfile for all gateways
@ (for Unix) use syslog, filename is used as ident name
@@ -332,12 +332,12 @@ with "logformat" filename must begin with
Grinwitch time zone for all time-based format
specificators.
rotate +
rotate
<n>
how many archived log files to keep
logformat +
logformat
<format>
Format for log record. First symbol in format must be L
(local time) or G (absolute Grinwitch time). It can be
@@ -349,7 +349,7 @@ logformat means comma and percent are replaced with space
and all time based elemnts are in local time zone.
You can use:
%y Year in 2 +
%y Year in 2
digit format
%Y Year in 4 digit format
%m Month number
@@ -394,7 +394,7 @@ l_service, l_in, l_out, l_descr) values (´%d-%m-%Y
%H:%M:%S´, ´%U´, ´%N´, %I, %O,
´%T´)"
logdump +
logdump
<in_traffic_limit> <out_traffic_limit>
Immediately creates additional log records if given amount
@@ -404,7 +404,7 @@ to prevent information about long-lasting downloads on
server shutdown.
delimchar +
delimchar
<char>
Sets the delimiter character used to separate username from
hostname in proxy authentication strings (e.g. for FTP, POP3
@@ -412,14 +412,14 @@ proxies). Default is ´@´. For example, to use
´#´ instead: delimchar #. This allows usernames
to contain the ´@´ character.
archiver +
archiver
<ext> <commandline>
Archiver to use for log files. <ext> is file extension
produced by archiver. Filename will be last argument to
archiver, optionally you can use %A as produced archive name
and %F as filename.
timeouts +
timeouts
<BYTE_SHORT> <BYTE_LONG> <STRING_SHORT>
<STRING_LONG> <CONNECTION_SHORT>
<CONNECTION_LONG> <DNS> <CHAIN>
@@ -450,14 +450,14 @@ tail of the data to be lost on slow connections, too large
one delays release of the sockets.
default timeouts 1 5 30 60 180 1800 15 60 15 5 5
maxseg +
maxseg
<value>
Sets TCP maximum segment size (MSS) for outgoing
connections. This can be used to work around path MTU
discovery issues or to optimize traffic for specific network
conditions.
radius +
radius <NAS_SECRET> <radius_server_1[:port][/local_address_1] <radius_server_2[:port][/local_address_2] @@ -484,7 +484,7 @@ user), Reply-Message. Use authcache to speedup authentication. RADIUS feature is currently experimental.
-nserver +
nserver
<ipaddr>[:port][/tcp]
Nameserver to use for name resolutions. If none specified
system routines for name resolution is used. Optional port
@@ -492,13 +492,13 @@ number may be specified. If optional /tcp is added to IP
address, name resolution is performed over TCP.
authnserver +
authnserver
<ipaddr>[:port][/tcp]
Nameserver to use for DNS-based authentication (e.g. dnsname
auth type). If not specified, nserver is used. The syntax is
the same as for nserver.
nscache +
nscache
<cachesize> nscache6
<cachesize>
Cache <cachesize> records for name resolution
@@ -506,7 +506,7 @@ Cache <cachesize> records for name resolution
cache size should usually be large enough (for example,
65536).
nsrecord +
nsrecord
<hostname> <hostaddr>
Adds static record to nscache. nscache must be
enabled. If 0.0.0.0 is used as a hostaddr host will never
@@ -514,14 +514,14 @@ resolve, it can be used to blacklist something or together
with dialer command to set up UDL for dialing.
fakeresolve +
fakeresolve
All names are resolved to the 127.0.0.2 address. Useful if
all requests are redirected to a parent proxy with
http, socks4+, connect+ or
socks5+.
dialer +
dialer
<progname>
Execute progname if external name can´t be resolved.
Hint: if you use nscache, dialer may not work, because names
@@ -529,7 +529,7 @@ will be resolved through cache. In this case you can use
something like http://dial.right.now/ from browser to set up
connection.
internal +
internal
<ipaddr>
sets ip address of internal interface. This IP address will
be used to bind gateways. Alternatively you can use -i
@@ -543,7 +543,7 @@ Unix sockets are supported with the syntax
using Unix sockets, the socket file is automatically created
and removed on service start/stop.
external +
external
<ipaddr>
sets ip address of external interface. This IP address will
be source address for all connections made by proxy.
@@ -552,7 +552,7 @@ address for gateway. Since 0.8 version External or -e
can be given twice: once with IPv4 and once with IPv6
address.
maxconn +
maxconn
<number>
sets the maximum number of simultaneous connections to each
service started after this command at the network level.
@@ -562,13 +562,13 @@ will silently ignore new connections, while connlim
will report back to the client that the connection limit has
been reached.
backlog +
backlog
sets the listening socket backlog of new connections.
Default is 1 + maxconn/8. Maximum value is capped by
kernel tunable somaxconn.
service +
service
(deprecated). Indicates that 3proxy should behave as a
Windows 95/98/NT/2000/XP service; has no effect under Unix.
@@ -576,7 +576,7 @@ Not required for 3proxy 0.6 and above. If you upgraded from
a previous version of 3proxy, use --remove and --install to
reinstall the service.
daemon +
daemon
Should be specified to close the console. Do not use
´daemon´ with ´service´. At least
@@ -584,7 +584,7 @@ under FreeBSD, daemon should precede any proxy
service and log commands to avoid socket problems. Always
place it in the beginning of the configuration file.
auth +
auth
<authtype> [...]
Type of user authorization. Currently supported:
none - no authentication or authorization required.
@@ -624,7 +624,7 @@ address is then restored from the cache entry.
radius - authentication with RADIUS.
Plugins may add additional authentication types.
It´s +
It´s
possible to use multiple authentication types in the same
command. E.g.
auth iponly strong
@@ -638,7 +638,7 @@ for dedicated laptops and request a username/password for
shared ones.
authcache +
authcache
<cachtype> <cachtime> <cachesize>
Cache authentication information for a given amount of time
@@ -683,7 +683,7 @@ see allow.
Use auth type cache (or cacheacl) for cached
authentication
allow +
allow
<userlist> <sourcelist> <targetlist>
<targetportlist> <operationlist>
<weekdayslist> <timeperiodslist>
@@ -719,7 +719,7 @@ specific addresses immediately without any conditions you
should either bind proxy to appropriate interface only or to
use ip filters.
Operation is one +
Operation is one
of:
CONNECT establish outgoing TCP connection
BIND bind TCP port for listening
@@ -743,7 +743,7 @@ remote side.
FTP matches any FTP/FTP Data request
ADMIN access to administration interface
Weekdays are +
Weekdays are
week day numbers or periods, 0 or 7 means Sunday, 1 is
Monday, 1-5 means Monday through Friday.
Timeperiodlists is a list of time periods in
@@ -788,7 +788,7 @@ RADIUS or plugin authentication: cacheacl with the
destination in the cache key if no parent proxy is used,
cache otherwise, see cacheacl.
parent +
parent
<weight> <type> <ip> <port>
<username> <password>
this command must follow "allow" rule. It extends
@@ -818,7 +818,7 @@ connections. Chains are only applied to new connections,
pipelined (keep-alive) requests in the same connection use
the same chain.
type is one of: +
type is one of:
extip does not actually redirect the request; it sets
the external address for this request to <ip>.
@@ -877,7 +877,7 @@ Requires SSL/TLS support (WITH_SSL) and is used with
ssl_client_mode 3, which only handshakes TLS for
s-suffixed parents.
IP and port are +
IP and port are ip addres and port of parent proxy server. If IP is zero, ip is taken from original request, only port is changed. If port is zero, it´s taken from original request, only @@ -898,7 +898,7 @@ unix:@parent.proxy 3128). When using Unix sockets, the port number is ignored but must be specified for syntax compatibility.
-Main purpose of +
Main purpose of local redirections is to have the requested resource (URL or POP3 username) logged and protocol-specific filters applied. In case of local redirection, ACLs are reviewed twice: @@ -923,19 +923,19 @@ parent proxy. Username of ´*´ means username must be supplied by user.
-parentretries +
parentretries
<number>
Number of retries to connect to parent proxy. Default is
1.
nolog +
nolog
<n>
extends last allow or deny command to prevent logging, e.g.
allow * * 192.168.1.1
nolog
weight +
weight
<n>
extends last allow or deny command to set weight for this
request
@@ -943,7 +943,7 @@ allow * * 192.168.1.1
weight 100
Weight may be used for different purposes.
force
+
force
noforce
If force is specified for service, configuration reload will
require all current sessions of this service to be
@@ -953,7 +953,7 @@ closed. noforce allows to keep previously authenticated
connections.
bandlimin +
bandlimin
<rate> <userlist> <sourcelist>
<targetlist> <targetportlist>
<operationlist> <weekdayslist>
@@ -995,7 +995,7 @@ POP3, you can use
nobandlimin * * * 110
before the rest of bandlim rules.
connlim +
connlim <rate> <period> <userlist> <sourcelist> <targetlist> <targetportlist> <operationlist> <weekdayslist> @@ -1017,7 +1017,7 @@ required per client, a separate rule must be added for every client. Like with nobandlimin, noconnlim adds an exception.
-counter +
counter
<filename> <reporttype>
<reportname>
countin <number> <type> <limit>
@@ -1045,7 +1045,7 @@ nocountall <userlist> <sourcelist>
<operationlist> <weekdayslist>
<timeperiodslist>
counter, +
counter, countin, nocountin, countout, nocountout, countall, nocountall commands are used to set a traffic limit in MB for a period of time (day, week or month). Filename is a @@ -1070,7 +1070,7 @@ report is a text file with counter values in the format: The rest of parameters is identical to bandlim/nobandlim.
-users +
users
username[:pwtype:password] ...
pwtype is one of:
none (empty) - use system authentication
@@ -1088,7 +1088,7 @@ users "test4:CR:$3$salt$G47yV9w...."
Note: double quotes are required because the password
contains a $ sign.
flush +
flush
empty the active access list. The access list must be
flushed every time you create a new access list for a new
@@ -1100,35 +1100,35 @@ allow * 192.168.1.0/24
socks
sets different ACLs for pop3p and socks
system +
system
<command>
execute system command
pidfile +
pidfile
<filename>
write pid of current process to file. It can be used to
manipulate 3proxy with signals under Unix. Currently next
signals are available:
monitor +
monitor
<filename>
If file monitored changes in modification time or size,
3proxy reloads configuration within one minute. Any number
of files may be monitored.
setuid +
setuid
<uid>
calls setuid(uid), uid can be numeric or since 0.9 username.
Unix only. Warning: under some Linux kernels setuid() works
for current thread only. It makes it impossible to suid for
all threads.
setgid +
setgid
<gid>
calls setgid(gid), gid can be numeric or since 0.9
groupname. Unix only.
chroot +
chroot
<path> [<uid>]
[<gid>]
calls chroot(path) and sets gid/uid. Unix only. uid/gid
@@ -1136,7 +1136,7 @@ supported since 0.9, can be numeric or
username/groupname
stacksize +
stacksize
<value_to_add_to_default_stack_size>
Change the default size for thread stacks. May be required
in some situations, e.g. with non-default plugins, or on
@@ -1165,7 +1165,7 @@ disable the thread stack.
plugin +
plugin
<path_to_shared_library>
<function_to_call> [<arg1> ...]
Loads specified library and calls given export function with
@@ -1176,7 +1176,7 @@ function_to_call must return 0 in case of success, value
> 0 to indicate error.
filtermaxsize +
filtermaxsize
<max_size_of_data_to_filter>
If Content-length (or another data length) is greater than
the given value, no data filtering will be performed through
@@ -1188,13 +1188,13 @@ Content-Length changing. Default is 1MB (1048576).
SSL/TLS support +
SSL/TLS support is built into 3proxy (since 0.9.7) when compiled with OpenSSL (WITH_SSL). Previously available as SSLPlugin, the functionality is now integrated into the main binary. The plugin line is no longer required.
-SSL/TLS can be +
SSL/TLS can be used for: - transparent MITM (Man-in-the-Middle) for TLS traffic inspection - https:// proxy (TLS-encrypted connection between client and proxy) - TLS client @@ -1207,7 +1207,7 @@ certificates
-ssl_mitm +
ssl_mitm
- spoof certificates for services started below. Usage
without ssl_client_verify is insecure.
ssl_nomitm - do not spoof certificates for services
@@ -1218,7 +1218,7 @@ started below
ssl_serv +
ssl_serv
(or ssl_server) - require TLS connection from clients for
services below
ssl_noserv (or ssl_noserver) - do not require TLS
@@ -1229,7 +1229,7 @@ connection from clients for services below
ssl_cli +
ssl_cli
(or ssl_client) - establish TLS connection to upstream
server for services below
ssl_nocli (or ssl_noclient) - do not establish TLS
@@ -1241,7 +1241,7 @@ connection to upstream server for services below
ssl_server_cert +
ssl_server_cert
/path/to/cert - Server certificate (should not be
self-signed, must contain SAN) for ssl_serv
ssl_server_key /path/to/key - Server certificate
@@ -1306,14 +1306,14 @@ generated MITM certificates cache
PCRE (Perl +
PCRE (Perl Compatible Regular Expressions) filtering is built into 3proxy (since 0.9.7) when compiled with PCRE2 support (WITH_PCRE). Previously available as PCREPlugin, the functionality is now integrated into the main binary. The plugin line is no longer required.
-PCRE filtering +
PCRE filtering allows creating matching and replacement rules with regular expressions for client requests, headers, and data.
@@ -1322,7 +1322,7 @@ expressions for client requests, headers, and data. -pcre +
pcre
TYPE FILTER_ACTION REGEXP [ACE]
Apply a rule for matching regular expression.
pcre_rewrite TYPE FILTER_ACTION REGEXP
@@ -1358,7 +1358,7 @@ PCRE_BSR_UNICODE.
TYPE - type of +
TYPE - type of
filtered data (comma-delimited list):
request - content of the client’s request (e.g., HTTP
GET request string)
@@ -1369,7 +1369,7 @@ data)
srvdata - data received from the server (e.g., HTML
page)
FILTER_ACTION - +
FILTER_ACTION -
action on match:
allow - allow this request without checking the rest of the
rules
@@ -1378,18 +1378,18 @@ rules
dunno - continue with the rest of the rules (useful with
pcre_rewrite)
REGEXP - PCRE +
REGEXP - PCRE (Perl) regular expression. Use * if no regexp matching is required.
-REWRITE_EXPRESSION +
REWRITE_EXPRESSION - substitution string. May contain Perl-style substrings $1, $2, etc. $0 means the whole matched string. \r and \n may be used to insert new lines; the string may be empty ("").
-ACE - access +
ACE - access control entry (user names, source IPs, destination IPs, ports, etc.), identical to allow/deny/bandlimin commands. The regular expression is only matched if the ACL matches @@ -1402,7 +1402,7 @@ authentication and/or allow/deny ACLs.
-Report all bugs +
Report all bugs to 3proxy@3proxy.org
3proxy(8), +
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),
@@ -1421,7 +1421,7 @@ https://3proxy.org/
3proxy is +
3proxy is designed by Vladimir Dubrovin <vlad@3proxy.org>
3proxy - +
3proxy - 3[APA3A] tiny proxy server, or trivial proxy server, or free proxy server
@@ -34,7 +34,7 @@ proxy server -3proxy +
3proxy
[config_file]
3proxy [--install]
3proxy [--remove]
3proxy is +
3proxy is a universal proxy server. It can be used to provide internal users with fully controllable access to external resources or to provide external users with access to internal @@ -71,7 +71,7 @@ under Unix). So you can play your favourite games, listen to music, exchange files and messages and even accept incoming connections behind a proxy server.
-dnspr +
dnspr does not exist as an independent service. It’s a DNS caching proxy (it requires nscache and nserver to be set in the configuration. Only A-records are cached. @@ -79,7 +79,7 @@ Please note that this caching is mostly a ’hack’ and has nothing to do with a real DNS server, but it works perfectly for SOHO networks.
-3proxy supports +
3proxy supports access control lists (ACL) like network router. Source and destination networks and destination port can be specified. In addition, usernames and gateway action (for example GET @@ -92,7 +92,7 @@ ACL action request can be allowed, denied or redirected to another host or to another proxy server or even to a chain of proxy servers.
-It supports +
It supports different types of logging: to logfiles, syslog(3) (only under Unix) or to an ODBC database. Logging format is tunable to provide compatibility with existing log file @@ -105,9 +105,9 @@ Apache or Squid log parsers.
-config_file
+config_file
-Name of config file. See +
Name of config file. See
3proxy.cfg(3) for configuration file format. Under
Windows, if config_file is not specified, 3proxy
looks for a file named 3proxy.cfg in the default
@@ -119,14 +119,14 @@ script just by setting +x mode and adding
#!/usr/local/3proxy/3proxy
as a first line in 3proxy.cfg
--install
+--install
-(Windows NT family only) +
(Windows NT family only) install 3proxy as a system service
---remove
+--remove
-(Windows NT family only) remove +
(Windows NT family only) remove 3proxy from system services
Under Unix there +
Under Unix there
are a few signals 3proxy catches. See kill(1).
SIGTERM
clean up connections and +
clean up connections and exit
-SIGPAUSE
+SIGPAUSE
-stop accepting new connections, +
stop accepting new connections, on second signal - start and re-read configuration
-SIGCONT
+SIGCONT
-start to accept new +
start to accept new connections
-SIGUSR1
+SIGUSR1
-reload configuration
+reload configuration
-Under Windows, +
Under Windows,
if 3proxy is installed as a service you can use
standard service management to start, stop, pause and
continue the 3proxy service, for example:
@@ -165,7 +165,7 @@ net stop 3proxy
net pause 3proxy
net continue 3proxy
Web admin +
Web admin service can also be used to reload configuration. Use wget to automate this task.
@@ -175,10 +175,10 @@ to automate this task. -/usr/local/3proxy/3proxy.cfg +
/usr/local/3proxy/3proxy.cfg (3proxy.cfg)
-3proxy configuration +
3proxy configuration file
Report all bugs +
Report all bugs to 3proxy@3proxy.org
3proxy.cfg(5), +
3proxy.cfg(5),
proxy(8), ftppr(8), socks(8), pop3p(8), imapp(8), tcppm(8),
udppm(8), kill(1), syslogd(8),
https://3proxy.org/
3proxy is +
3proxy is designed by Vladimir Dubrovin <vlad@3proxy.org>
3proxy_crypt +
3proxy_crypt - utility to generate encrypted passwords for 3proxy
3proxy_crypt +
3proxy_crypt
password
3proxy_crypt salt password
3proxy_crypt +
3proxy_crypt is a utility to generate encrypted password hashes for use with 3proxy configuration. Encrypted passwords allow the system to avoid storing passwords in cleartext in configuration files.
-When invoked +
When invoked with a single argument, it produces an NT password hash (MD4-based, suitable for NTLM authentication). The output is prefixed with NT:.
-When invoked +
When invoked with two arguments (salt and password), it produces a BLAKE2b password hash. The salt length is limited to 64 characters. The output is prefixed with CR:.
-The resulting +
The resulting hash can be used in the 3proxy configuration file with the users directive instead of a cleartext password.
@@ -71,25 +71,25 @@ hash can be used in the 3proxy configuration file with the -password
+password
-Cleartext password to +
Cleartext password to encrypt.
| + |
salt |
- | + |
Salt string for BLAKE2b hashing (max 64 characters). |
-+ |
Generate NT +
Generate NT password hash:
-3proxy_crypt +
3proxy_crypt MySecretPassword
-Result:
+Result:
-NT:3F7E6D8D96E8E7A9B0C1D2E3F4A5B6C7
+NT:3F7E6D8D96E8E7A9B0C1D2E3F4A5B6C7
-Generate BLAKE2b password hash +
Generate BLAKE2b password hash with salt:
-3proxy_crypt MySalt +
3proxy_crypt MySalt MySecretPassword
-Result:
+Result:
-CR:$3$MySalt$...
+CR:$3$MySalt$...
-Using in 3proxy.cfg:
+Using in 3proxy.cfg:
-users +
users user1:CR:$3$MySalt$...
The NT hash uses +
The NT hash uses the RSA MD4 Message-Digest Algorithm. The BLAKE2b hash uses the BLAKE2 cryptographic hash function.
-When a password +
When a password hash is prefixed with NT: or CR:, 3proxy uses the corresponding algorithm to verify passwords instead of comparing cleartext strings.
@@ -143,7 +143,7 @@ comparing cleartext strings. -Report all bugs +
Report all bugs to 3proxy@3proxy.org
3proxy(8), +
3proxy(8),
3proxy.cfg(5),
https://3proxy.org/
3proxy is +
3proxy is designed by Vladimir Dubrovin <vlad@3proxy.org>
ftppr - +
ftppr - FTP proxy gateway service
ftppr +
ftppr [-d] [-l[[@]logfile]] [-pport] [-iinternal_ip] [-eexternal_ip] @@ -43,7 +43,7 @@ FTP proxy gateway service
-ftppr is +
ftppr is FTP gateway service to allow internal users to access external FTP servers.
@@ -55,81 +55,80 @@ external FTP servers.| + |
-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. | |
| + |
- -u |
+- | + |
- Never look for username -authentication. | |
| + |
- -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
+-niPATH
-(Linux only) Switch to the +
(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
+-nePATH
-(Linux only) Switch to the +
(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 @@ -140,13 +139,13 @@ file path (e.g. /var/run/netns/myns or
| + |
-i |
- | + |
Internal address. IP address the proxy accepts @@ -156,56 +155,55 @@ be specified with -iunix:/path/to/socket syntax (e.g., -iunix:/var/run/ftppr.sock). On Linux, abstract sockets use -iunix:@socketname syntax. | |
| + |
- -h |
+- | + |
- Default destination. It’s -used if the target address is not specified by the user. | |
| + |
- -p |
+- | + |
- Port. Port proxy listens for -incoming connections. Default is 21. | |
| + |
- -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. |
You can use any +
You can use any FTP client, regardless of FTP proxy support. For a client with FTP proxy support, configure internal_ip and port in the FTP proxy parameters. For clients without @@ -232,7 +230,7 @@ supported.
-Report all bugs +
Report all bugs to 3proxy@3proxy.org
3proxy(8), +
3proxy(8),
proxy(8), pop3p(8), socks(8), tcppm(8), udppm(8),
syslogd(8),
https://3proxy.org/
3proxy is +
3proxy is designed by Vladimir Dubrovin <vlad@3proxy.org>
imapp - +
imapp - IMAPv4 proxy gateway service
imapp +
imapp [-d] [-l[[@]logfile]] [-pport] [-iinternal_ip] [-eexternal_ip] @@ -44,7 +44,7 @@ IMAPv4 proxy gateway service
-imapp +
imapp is IMAPv4 (IMAP4rev1) gateway service to allow internal users to access external IMAP servers.
@@ -56,81 +56,80 @@ users to access external IMAP servers.| + |
-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. | |
| + |
- -u |
+- | + |
- Never look for username -authentication. | |
| + |
- -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
+-niPATH
-(Linux only) Switch to the +
(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
+-nePATH
-(Linux only) Switch to the +
(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 @@ -141,13 +140,13 @@ file path (e.g. /var/run/netns/myns or
| + |
-i |
- | + |
Internal address. IP address the proxy accepts @@ -157,69 +156,68 @@ be specified with -iunix:/path/to/socket syntax (e.g., -iunix:/var/run/imapp.sock). On Linux, abstract sockets use -iunix:@socketname syntax. | |
| + |
- -p |
+- | + |
- Port. Port proxy listens for -incoming connections. Default is 143. | |
| + |
- -h |
+- | + |
- Default destination. It’s -used if the target address is not specified by the user. | |
| + |
- -x |
+- | + |
- Disable STARTTLS support. -STARTTLS is not announced in the CAPABILITY response and the -STARTTLS command is not accepted. | |
| + |
- -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. |
You can use any +
You can use any MUA (Mail User Agent) with IMAPv4 support. Set the client to use internal_ip and port as an IMAP server. The address of the real IMAP server must be configured as a @@ -262,7 +260,7 @@ fails.
-Report all bugs +
Report all bugs to 3proxy@3proxy.org
3proxy(8), +
3proxy(8),
ftppr(8), pop3p(8), proxy(8), smtpp(8), socks(8), tcppm(8),
tlspr(8), udppm(8), syslogd(8),
https://3proxy.org/
3proxy is +
3proxy is designed by Vladimir Dubrovin <vlad@3proxy.org>
pop3p - +
pop3p - POP3 proxy gateway service
pop3p +
pop3p [-d] [-l[[@]logfile]] [-pport] [-iinternal_ip] [-eexternal_ip] @@ -44,7 +44,7 @@ POP3 proxy gateway service
-pop3p +
pop3p is POP3 gateway service to allow internal users to access external POP3 servers.
@@ -56,81 +56,80 @@ external POP3 servers.| + |
-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. | |
| + |
- -u |
+- | + |
- Never look for username -authentication. | |
| + |
- -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
+-niPATH
-(Linux only) Switch to the +
(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
+-nePATH
-(Linux only) Switch to the +
(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 @@ -141,13 +140,13 @@ file path (e.g. /var/run/netns/myns or
| + |
-i |
- | + |
Internal address. IP address the proxy accepts @@ -157,69 +156,68 @@ be specified with -iunix:/path/to/socket syntax (e.g., -iunix:/var/run/pop3p.sock). On Linux, abstract sockets use -iunix:@socketname syntax. | |
| + |
- -p |
+- | + |
- Port. Port proxy listens for -incoming connections. Default is 110. | |
| + |
- -h |
+- | + |
- Default destination. It’s -used if the target address is not specified by the user. | |
| + |
- -x |
+- | + |
- Disable STARTTLS (STLS) support. -STLS is not announced in the CAPA response and the STLS -command is not accepted. | |
| + |
- -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. |
You can use any +
You can use any MUA (Mail User Agent) with POP3 support. Set the client to use internal_ip and port as a POP3 server. The address of the real POP3 server must be configured as a part @@ -255,7 +253,7 @@ TLS handshake with the client fails.
-Report all bugs +
Report all bugs to 3proxy@3proxy.org
3proxy(8), +
3proxy(8),
ftppr(8), proxy(8), socks(8), tcppm(8), udppm(8),
syslogd(8),
https://3proxy.org/
3proxy is +
3proxy is designed by Vladimir Dubrovin <vlad@3proxy.org>
proxy - +
proxy - HTTP proxy gateway service
proxy +
proxy [-d][-a] [-l[[@]logfile]] [-pport] [-iinternal_ip] [-eexternal_ip]
@@ -42,7 +42,7 @@ HTTP proxy gateway service -proxy is +
proxy is HTTP gateway service with HTTPS and FTP over HTTPS support.
@@ -54,81 +54,80 @@ support.| + |
-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. | |
| + |
- -u |
+- | + |
- Never ask for username -authentication | |
| + |
- -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
+-niPATH
-(Linux only) Switch to the +
(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
+-nePATH
-(Linux only) Switch to the +
(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 @@ -139,13 +138,13 @@ file path (e.g. /var/run/netns/myns or
| + |
-i |
- | + |
Internal address. IP address the proxy accepts @@ -155,68 +154,65 @@ be specified with -iunix:/path/to/socket syntax (e.g., -iunix:/var/run/proxy.sock). On Linux, abstract sockets use -iunix:@socketname syntax. | |
| + |
- -a |
+- | + |
- Anonymous. Hide information -about client. | |
| + |
- -a1 |
+- | + |
- Anonymous. Show fake information -about client. | |
| + |
- -p |
+- | + |
- Port. Port proxy listens for -incoming connections. Default is 3128. | |
| + |
- -l |
+- | + |
- Log. By default logging is to -stdout. If logfile is specified logging is to file. -Under Unix, if ´@´ preceeds -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. |
You should use a +
You should use a client with HTTP proxy support or configure a router to redirect HTTP traffic to the proxy (transparent proxy). Configure the client to connect to internal_ip and @@ -237,7 +233,7 @@ TCP-based protocol. If you need to limit clients, use -
Report all bugs +
Report all bugs to 3proxy@3proxy.org
3proxy(8), +
3proxy(8),
ftppr(8), socks(8), pop3p(8), tcppm(8), udppm(8),
syslogd(8),
https://3proxy.org/
3proxy is +
3proxy is designed by Vladimir Dubrovin <vlad@3proxy.org>
smtpp - +
smtpp - SMTP proxy gateway service
smtpp +
smtpp [-d] [-l[[@]logfile]] [-pport] [-iinternal_ip] [-eexternal_ip] @@ -44,7 +44,7 @@ SMTP proxy gateway service
-smtpp +
smtpp is SMTP gateway service to allow internal users to access external SMTP servers.
@@ -56,81 +56,80 @@ external SMTP servers.| + |
-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. | |
| + |
- -u |
+- | + |
- Never look for username -authentication. | |
| + |
- -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
+-niPATH
-(Linux only) Switch to the +
(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
+-nePATH
-(Linux only) Switch to the +
(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 @@ -141,13 +140,13 @@ file path (e.g. /var/run/netns/myns or
| + |
-i |
- | + |
Internal address. IP address the proxy accepts @@ -157,69 +156,68 @@ be specified with -iunix:/path/to/socket syntax (e.g., -iunix:/var/run/smtpp.sock). On Linux, abstract sockets use -iunix:@socketname syntax. | |
| + |
- -p |
+- | + |
- Port. Port proxy listens for -incoming connections. Default is 587. | |
| + |
- -h |
+- | + |
- Default destination. It’s -used if the target address is not specified by the user. | |
| + |
- -x |
+- | + |
- Disable STARTTLS support. -STARTTLS is not announced in the EHLO response and the -STARTTLS command is not accepted. | |
| + |
- -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. |
You can use any +
You can use any MUA (Mail User Agent) with SMTP authentication support. Set the client to use internal_ip and port as an SMTP server. The address of the real SMTP server must be @@ -256,7 +254,7 @@ fails.
-Report all bugs +
Report all bugs to 3proxy@3proxy.org
3proxy(8), +
3proxy(8),
ftppr(8), proxy(8), socks(8), tcppm(8), udppm(8),
syslogd(8),
https://3proxy.org/
3proxy is +
3proxy is designed by Vladimir Dubrovin <vlad@3proxy.org>
socks - +
socks - SOCKS 4/4.5/5 gateway service
socks +
socks [-d] [-l[[@]logfile]] [-pport] [-iinternal_ip] [-eexternal_ip]
@@ -42,7 +42,7 @@ SOCKS 4/4.5/5 gateway service -socks is +
socks is SOCKS server. It supports SOCKSv4, SOCKSv4.5 (extension to v4 for server side name resolution) and SOCKSv5. SOCKSv5 specification allows both outgoing and reverse TCP @@ -56,82 +56,81 @@ connections and UDP portmapping.
| + |
-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. | |
| + |
- -u |
+- | + |
- Never ask for username -authentication | |
| + |
- -e |
+- | + |
- External address. IP address of -the interface the proxy should initiate connections from. -External IP must be specified if you need incoming -connections. By default, the system will decide which -address to use in accordance with the routing table. |
-niPATH
+-niPATH
-(Linux only) Switch to the +
(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
+-nePATH
-(Linux only) Switch to the +
(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 @@ -142,13 +141,13 @@ file path (e.g. /var/run/netns/myns or
| + |
-Ne |
- | + |
External NAT address 3proxy reports to client for @@ -157,77 +156,75 @@ and destination server. By default, the external address is reported. It’s only useful in the case of IP-IP NAT and does not work with port translation. | |
| + |
- -Ni |
+- | + |
- Internal NAT address 3proxy -reports to client for UDPASSOC. This is external address of -the NAT between 3proxy and the client, client uses to -connect to 3proxy. By default, the internal address is -reported. It’s only useful in the case of IP-IP NAT -and does not work with port translation. | |
| + |
- -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/socks.sock). On Linux, abstract sockets use --iunix:@socketname syntax. | |
| + |
- -p |
+- | + |
- Port. Port proxy listens for -incoming connections. Default is 1080. | |
| + |
- -l |
+- | + |
- Log. By default logging is to -stdout. If logfile is specified logging is to file. -Under Unix, if ´@´ preceeds -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. |
You should use a +
You should use a client with SOCKS support or use some socksification support (for example SocksCAP or FreeCAP). Configure client to use internal_ip and port. SOCKS @@ -250,7 +247,7 @@ privileges). If you need to control access, use -
Report all bugs +
Report all bugs to 3proxy@3proxy.org
3proxy(8), +
3proxy(8),
proxy(8), ftppr(8), pop3p(8), tcppm(8), udppm(8),
syslogd(8),
https://3proxy.org/
3proxy is +
3proxy is designed by Vladimir Dubrovin <vlad@3proxy.org>
tcppm - +
tcppm - TCP port mapper
tcppm +
tcppm [-d] [-l[[@]logfile]] [-iinternal_ip] [-eexternal_ip] local_port remote_host remote_port
@@ -44,7 +44,7 @@ TCP port mapper -tcppm +
tcppm forwards connections from local to remote TCP 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 connections from. By -default, the system will decide which address to use in -accordance with the routing table. |
-niPATH
+-niPATH
-(Linux only) Switch to the +
(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
+-nePATH
-(Linux only) Switch to the +
(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 @@ -128,13 +128,13 @@ file path (e.g. /var/run/netns/myns or
| + |
-i |
- | + |
Internal address. IP address the proxy accepts @@ -144,32 +144,31 @@ 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. |
local_port
+local_port
-- port tcppm accepts +
- port tcppm accepts connections on
-remote_host
+remote_host
-- IP address of the host the +
- 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
-- remote port the connection is +
- remote port the connection is forwarded to. Ignored when using Unix socket destination, but must be specified (use any positive value) for syntax compatibility.
@@ -204,7 +203,7 @@ compatibility. -Any TCP-based +
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 @@ -215,7 +214,7 @@ application. The connection is forwarded to -
Report all bugs +
Report all bugs to 3proxy@3proxy.org
3proxy(8), +
3proxy(8),
proxy(8), ftppr(8), socks(8), pop3p(8), udppm(8),
syslogd(8),
https://3proxy.org/
3proxy is +
3proxy is designed by Vladimir Dubrovin <vlad@3proxy.org>
tlspr - +
tlspr - SNI proxy gateway service
tlspr +
tlspr [-d][-a] [-l[[@]logfile]] [-plistening_port] [-Pdestination_port] @@ -45,7 +45,7 @@ SNI proxy gateway service
-tlspr is +
tlspr is an SNI gateway service (destination host is taken from TLS handshake). The destination port must be specified via the -P option (or it may be detected with the Transparent @@ -61,81 +61,80 @@ access control is required.
| + |
-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. | |
| + |
- -u |
+- | + |
- Never ask for username -authentication | |
| + |
- -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
+-niPATH
-(Linux only) Switch to the +
(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
+-nePATH
-(Linux only) Switch to the +
(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 @@ -146,13 +145,13 @@ file path (e.g. /var/run/netns/myns or
| + |
-i |
- | + |
Internal address. IP address the proxy accepts @@ -162,93 +161,90 @@ be specified with -iunix:/path/to/socket syntax (e.g., -iunix:/var/run/tlspr.sock). On Linux, abstract sockets use -iunix:@socketname syntax. | |
| + |
- -a |
+- | + |
- Anonymous. Hide information -about client. | |
| + |
- -a1 |
+- | + |
- Anonymous. Show fake information -about client. | |
| + |
- -p |
+- | + |
- listening_port. Port proxy -listens for incoming connections. Default is 1443. | |
| + |
- -P |
+- | + |
- destination_port. Port to -establish outgoing connections. Required unless the -Transparent plugin is used, because the TLS handshake does -not contain port information. Default is 443. | |
| + |
- -c |
+- | + |
- TLS_CHECK_LEVEL. 0 (default) - -allow non-TLS traffic to pass, 1 - require TLS, only check -client HELLO packet, 2 - require TLS, check both client and -server HELLO, 3 - require TLS, check that the server sends a -certificate (not compatible with TLS 1.3), 4 - require -mutual TLS, check that the server sends a certificate -request and the client sends a certificate (not compatible -with TLS 1.3) | |
| + |
- -s |
+- | + |
- Split the TLS Client HELLO -packet across multiple TCP segments to make SNI-based DPI -detection harder. An optional numeric value can follow (e.g. --s1) to control the splitting behaviour. |
-Ximap | -Xpop3 | +
-Ximap | -Xpop3 | -Xsmtp
-STARTTLS mode for the given +
STARTTLS mode for the given protocol. The proxy speaks the plaintext protocol with the client (greeting, capability advertisement with STARTTLS only, STARTTLS command), then, after the client issues @@ -262,13 +258,13 @@ client fails.
| + |
-l |
- | + |
Log. By default logging is to stdout. If logfile @@ -276,18 +272,17 @@ 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. |
You should use a +
You should use a client with TLS support or configure a router to redirect TLS traffic to the proxy (transparent proxy). Configure the client to connect to internal_ip and port. If @@ -306,7 +301,7 @@ you need to limit clients, use 3proxy(8) instead.
-Report all bugs +
Report all bugs to 3proxy@3proxy.org
3proxy(8), +
3proxy(8),
ftppr(8), proxy(8), socks(8), pop3p(8), smtpp(8), tcppm(8),
udppm(8), syslogd(8),
https://3proxy.org/
3proxy is +
3proxy is designed by Vladimir Dubrovin <vlad@3proxy.org>
udppm - +
udppm - UDP port mapper
udppm +
udppm [-ds] [-l[[@]logfile]] [-iinternal_ip] [-eexternal_ip] local_port remote_host remote_port
@@ -44,7 +44,7 @@ UDP port mapper -udppm +
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. |
-niPATH
+-niPATH
-(Linux only) Switch to the +
(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
+-nePATH
-(Linux only) Switch to the +
(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 @@ -128,61 +128,59 @@ file path (e.g. /var/run/netns/myns or
| + |
-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
+local_port
-- port udppm accepts datagrams +
- port udppm accepts datagrams on
-remote_host
+remote_host
-- IP address of the host +
- IP address of the host datagrams are forwarded to
-remote_port
+remote_port
-- remote port datagrams are +
- remote port datagrams are forwarded to
Any UDP-based +
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 @@ -222,7 +220,7 @@ application. All datagrams are forwarded to -
Report all bugs +
Report all bugs to 3proxy@3proxy.org
3proxy(8), +
3proxy(8),
proxy(8), ftppr(8), socks(8), pop3p(8), udppm(8),
syslogd(8),
https://3proxy.org/
3proxy is +
3proxy is designed by Vladimir Dubrovin <vlad@3proxy.org>