mirror of
https://github.com/3proxy/3proxy.git
synced 2026-11-21 23:20:26 +00:00
Update documentation
parent
ce7841a8c4
commit
a1a45bc4e6
27 changed files with 2345 additions and 2311 deletions
1
.gitignore
vendored
Normal file
1
.gitignore
vendored
Normal file
|
|
@ -0,0 +1 @@
|
|||
.DS_Store
|
||||
484
3proxy.cfg.md
484
3proxy.cfg.md
|
|
@ -1,4 +1,4 @@
|
|||
<!-- Creator : groff version 1.22.4 -->
|
||||
<!-- Creator : groff version 1.24.1 -->
|
||||
<html>
|
||||
<head>
|
||||
|
||||
|
|
@ -24,7 +24,7 @@
|
|||
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>3proxy.cfg</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>3proxy.cfg</b>
|
||||
3proxy configuration file</p>
|
||||
|
||||
<h2>DESCRIPTION
|
||||
|
|
@ -32,33 +32,33 @@
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">Common
|
||||
<p style="margin-left:6%; margin-top: 1em">Common
|
||||
structure: <br>
|
||||
Configuration file is a text file 3proxy reads configuration
|
||||
from. Each line of the file is a command executed
|
||||
immediately, as it was given from console. Sequence of
|
||||
commands is important. Configuration file as actually a
|
||||
script for 3proxy executable. Each line of the file is
|
||||
treated as a blank (space or tab) separated command line.
|
||||
Additional space characters are ignored. Think about 3proxy
|
||||
as "application level router" with console
|
||||
interface.</p>
|
||||
immediately, as if it were given from the console. The
|
||||
sequence of commands is important. The configuration file is
|
||||
actually a script for the 3proxy executable. Each line of
|
||||
the file is treated as a blank (space or tab) separated
|
||||
command line. Additional space characters are ignored. Think
|
||||
about 3proxy as "application level router" with
|
||||
console interface.</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">Comments: <br>
|
||||
Any string beginning with space character or ´#´
|
||||
character is comment. It´s ignored. <LF>s are
|
||||
ignored. <CR> is end of command.</p>
|
||||
<p style="margin-left:6%; margin-top: 1em">Comments: <br>
|
||||
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.</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">Quotation: <br>
|
||||
Quotation character is " (double quote). Quotation must
|
||||
be used to quote spaces or another special characters. To
|
||||
use quotation character inside quotation character must be
|
||||
dubbed (BASIC convention). For example to use HELLO
|
||||
"WORLD" as an argument you should use it as
|
||||
"HELLO ""WORLD""". Good
|
||||
practice is to quote any argument you use.</p>
|
||||
<p style="margin-left:6%; margin-top: 1em">Quotation: <br>
|
||||
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
|
||||
character must be doubled (BASIC convention). For example,
|
||||
to use HELLO "WORLD" as an argument, you should
|
||||
write it as "HELLO ""WORLD""".
|
||||
Good practice is to quote any argument you use.</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">File inclusion:
|
||||
<p style="margin-left:6%; margin-top: 1em">File inclusion:
|
||||
<br>
|
||||
You can include file by using $FILENAME macro (replace
|
||||
FILENAME with a path to file, for example
|
||||
|
|
@ -68,15 +68,15 @@ is required in last example because path contains space
|
|||
character. For included file <CR> (end of line
|
||||
characters) is treated as space character (arguments
|
||||
delimiter instead of end of command delimiter). Thus,
|
||||
include files are only useful to store long signle-line
|
||||
include files are only useful to store long single-line
|
||||
commands (like userlist, network lists, etc). To use dollar
|
||||
sign somewhere in argument it must be quoted. Recursion is
|
||||
not allowed.</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">Next commands
|
||||
<p style="margin-left:6%; margin-top: 1em">Next commands
|
||||
start gateway services:</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>proxy</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>proxy</b>
|
||||
[options] <b><br>
|
||||
socks</b> [options] <b><br>
|
||||
pop3p</b> [options] <b><br>
|
||||
|
|
@ -103,16 +103,15 @@ dnspr</b> caching DNS proxy (default port 53) <b><br>
|
|||
tcppm</b> TCP portmapper <b><br>
|
||||
udppm</b> UDP portmapper</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">Options:
|
||||
<b><br>
|
||||
<p style="margin-left:6%; margin-top: 1em">Options: <b><br>
|
||||
-pNUMBER</b> change default server port to NUMBER <b><br>
|
||||
-n</b> disable NTLM authentication (required if passwords
|
||||
are stored in Unix crypt format). <b><br>
|
||||
-n1</b> enable NTLMv1 authentication. <b><br>
|
||||
-g(GRACE_TRAFF,GRACE_NUM,GRACE_DELAY)</b> delay GRACE_DELAY
|
||||
milliseconds before polling if average polling size below
|
||||
GRACE_TRAFF bytes and GRACE_NUM read operations in single
|
||||
directions are detected within 1 second. Useful to minimize
|
||||
milliseconds before polling if average polling size is below
|
||||
GRACE_TRAFF bytes and GRACE_NUM read operations in a single
|
||||
direction are detected within 1 second. Useful to minimize
|
||||
polling <b>-s</b> <br>
|
||||
(for admin) secure, allow only secure operations, currently
|
||||
only traffic counters view without ability to reset. <br>
|
||||
|
|
@ -127,7 +126,7 @@ authentication methods <b><br>
|
|||
client reported) <b><br>
|
||||
-a1</b> (for proxy) anonymous proxy (random client
|
||||
information reported) <b><br>
|
||||
-a2</b> (for proxy) generate Via: and X-Forwared-For:
|
||||
-a2</b> (for proxy) generate Via: and X-Forwarded-For:
|
||||
instead of Forwarded: <b><br>
|
||||
-6</b> Only resolve IPv6 addresses. IPv4 addresses are
|
||||
packed in IPv6 in IPV6_V6ONLY compatible way. <b><br>
|
||||
|
|
@ -158,20 +157,20 @@ SO_REUSEPORT, SO_PORT_SCALABILITY, SO_REUSE_UNICASTPORT,
|
|||
SO_KEEPALIVE, SO_DONTROUTE may be supported depending on OS.
|
||||
<b><br>
|
||||
-DiINTERFACE, -DeINTERFACE</b> bind internal interface /
|
||||
external inteface to given INTERFACE (e.g. eth0) if
|
||||
SO_BINDTODEVICE supported by system. You may need to run as
|
||||
root or to have CAP_NET_RAW capability in order to bind to
|
||||
interface, depending on system, so this option may require
|
||||
root privileges and can be incompatible with some
|
||||
configuraton commands like chroot and setuid (and daemon if
|
||||
external interface to given INTERFACE (e.g. eth0) if
|
||||
SO_BINDTODEVICE is supported by the system. You may need to
|
||||
run as root or have CAP_NET_RAW capability in order to bind
|
||||
to an interface, depending on the system, so this option may
|
||||
require root privileges and can be incompatible with some
|
||||
configuration commands like chroot and setuid (and daemon if
|
||||
setcap is used). <b><br>
|
||||
-e</b> External address. IP address of interface proxy
|
||||
should initiate connections from. External IP must be
|
||||
specified if you need incoming connections. By default
|
||||
system will deside which address to use in accordance with
|
||||
routing table. <b><br>
|
||||
-i</b> Internal address. IP address proxy accepts
|
||||
connections to. By default connection to any interface is
|
||||
-e</b> 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. <b><br>
|
||||
-i</b> Internal address. IP address the proxy accepts
|
||||
connections to. By default, connections to any interface are
|
||||
accepted. <b><br>
|
||||
-N</b> (for socks) External NAT address 3proxy reports to
|
||||
client for BIND and UDPASSOC By default external address is
|
||||
|
|
@ -205,17 +204,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</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>include</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>include</b>
|
||||
<path> <br>
|
||||
Include config file</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>config</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>config</b>
|
||||
<path> <br>
|
||||
Path to configuration file to use on 3proxy restart or to
|
||||
save configuration.</p>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>writable</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>writable</b>
|
||||
<br>
|
||||
ReOpens configuration file for write access via Web
|
||||
interface, and rereads it. Usually should be first command
|
||||
|
|
@ -223,10 +221,10 @@ on config file but in combination with config it can be used
|
|||
anywhere to open alternate config file. Think twice before
|
||||
using it.</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>end</b> <br>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>end</b> <br>
|
||||
End of configuration</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>log</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>log</b>
|
||||
[[@|&]logfile] [<LOGTYPE>] <br>
|
||||
sets logfile for all gateways <br>
|
||||
@ (for Unix) use syslog, filename is used as ident name <br>
|
||||
|
|
@ -250,12 +248,12 @@ with "logformat" filename must begin with
|
|||
Grinwitch time zone for all time-based format
|
||||
specificators.</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>rotate</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>rotate</b>
|
||||
<n> <br>
|
||||
how many archived log files to keep</p>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>logformat</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>logformat</b>
|
||||
<format> <br>
|
||||
Format for log record. First symbol in format must be L
|
||||
(local time) or G (absolute Grinwitch time). It can be
|
||||
|
|
@ -267,25 +265,25 @@ logformat means comma and percent are replaced with space
|
|||
and all time based elemnts are in local time zone. <br>
|
||||
You can use:</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">%y Year in 2
|
||||
<p style="margin-left:6%; margin-top: 1em">%y Year in 2
|
||||
digit format <br>
|
||||
%Y Year in 4 digit format <br>
|
||||
%m Month number <br>
|
||||
%o Month abbriviature <br>
|
||||
%o Month abbreviation <br>
|
||||
%d Day <br>
|
||||
%H Hour <br>
|
||||
%M Minute <br>
|
||||
%S Second <br>
|
||||
%t Timstamp (in seconds since 01-Jan-1970) <br>
|
||||
%t Timestamp (in seconds since 01-Jan-1970) <br>
|
||||
%. milliseconds <br>
|
||||
%z timeZone (from Grinvitch) <br>
|
||||
%z time zone (from Greenwich) <br>
|
||||
%D request duration (in milliseconds) <br>
|
||||
%b average send rate per request (in Bytes per second) this
|
||||
speed is typically below connection speed shown by download
|
||||
manager. <br>
|
||||
%B average receive rate per request (in Bytes per second)
|
||||
this speed is typically below connection speed shown by
|
||||
%b average send rate per request (in bytes per second); this
|
||||
speed is typically below the connection speed shown by the
|
||||
download manager. <br>
|
||||
%B average receive rate per request (in bytes per second);
|
||||
this speed is typically below the connection speed shown by
|
||||
the download manager. <br>
|
||||
%U Username <br>
|
||||
%N service Name <br>
|
||||
%p service Port <br>
|
||||
|
|
@ -304,15 +302,15 @@ download manager. <br>
|
|||
%h Hops (redirections) count <br>
|
||||
%T service specific Text <br>
|
||||
%N1-N2T (N1 and N2 are positive numbers) log only fields
|
||||
from N1 thorugh N2 of service specific text <br>
|
||||
in the case of ODBC logging logformat specifies SQL
|
||||
statement, for exmample: <br>
|
||||
from N1 through N2 of service-specific text <br>
|
||||
In the case of ODBC logging, logformat specifies an SQL
|
||||
statement, for example: <br>
|
||||
logformat "-´+_Linsert into log (l_date, l_user,
|
||||
l_service, l_in, l_out, l_descr) values (´%d-%m-%Y
|
||||
%H:%M:%S´, ´%U´, ´%N´, %I, %O,
|
||||
´%T´)"</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>logdump</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>logdump</b>
|
||||
<in_traffic_limit> <out_traffic_limit> <br>
|
||||
Immediately creates additional log records if given amount
|
||||
of incoming/outgoing traffic is achieved for connection,
|
||||
|
|
@ -320,16 +318,14 @@ without waiting for connection to finish. It may be useful
|
|||
to prevent information about long-lasting downloads on
|
||||
server shutdown.</p>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>archiver</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>archiver</b>
|
||||
<ext> <commandline> <br>
|
||||
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.</p>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>timeouts</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>timeouts</b>
|
||||
<BYTE_SHORT> <BYTE_LONG> <STRING_SHORT>
|
||||
<STRING_LONG> <CONNECTION_SHORT>
|
||||
<CONNECTION_LONG> <DNS> <CHAIN>
|
||||
|
|
@ -354,7 +350,7 @@ DNS timeout for DNS request before requesting next server
|
|||
CHAIN timeout for reading data from chained connection <br>
|
||||
default timeouts 1 5 30 60 180 1800 15 60 15 5</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>radius</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>radius</b>
|
||||
<NAS_SECRET>
|
||||
<radius_server_1[:port][/local_address_1]>
|
||||
<radius_server_2[:port][/local_address_2]> <br>
|
||||
|
|
@ -380,21 +376,20 @@ user), Reply-Message. Use authcache to speedup
|
|||
authentication. RADIUS feature is currently
|
||||
experimental.</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>nserver</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>nserver</b>
|
||||
<ipaddr>[:port][/tcp] <br>
|
||||
Nameserver to use for name resolutions. If none specified
|
||||
system routines for name resolution is used. Optional port
|
||||
number may be specified. If optional /tcp is added to IP
|
||||
address, name resolution is performed over TCP.</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>nscache</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>nscache</b>
|
||||
<cachesize> <b>nscache6</b> <cachesize> <br>
|
||||
Cache <cachesize> records for name resolution (nscache
|
||||
for IPv4, nscache6 for IPv6). Cachesize usually should be
|
||||
large enougth (for example 65536).</p>
|
||||
for IPv4, nscache6 for IPv6). The cache size should usually
|
||||
be large enough (for example, 65536).</p>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>nsrecord</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>nsrecord</b>
|
||||
<hostname> <hostaddr> <br>
|
||||
Adds static record to nscache. nscache must be enabled. If
|
||||
0.0.0.0 is used as a hostaddr host will never resolve, it
|
||||
|
|
@ -402,13 +397,13 @@ can be used to blacklist something or together with
|
|||
<b>dialer</b> command to set up UDL for dialing.</p>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>fakeresolve</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>fakeresolve</b>
|
||||
<br>
|
||||
All names are resolved to 127.0.0.2 address. Usefull if all
|
||||
requests are redirected to parent proxy with http, socks4+,
|
||||
connect+ or socks5+.</p>
|
||||
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+.</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>dialer</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>dialer</b>
|
||||
<progname> <br>
|
||||
Execute progname if external name can´t be resolved.
|
||||
Hint: if you use nscache, dialer may not work, because names
|
||||
|
|
@ -416,16 +411,14 @@ will be resolved through cache. In this case you can use
|
|||
something like http://dial.right.now/ from browser to set up
|
||||
connection.</p>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>internal</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>internal</b>
|
||||
<ipaddr> <br>
|
||||
sets ip address of internal interface. This IP address will
|
||||
be used to bind gateways. Alternatively you can use -i
|
||||
option for individual gateways. Since 0.8 version, IPv6
|
||||
address may be used.</p>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>external</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>external</b>
|
||||
<ipaddr> <br>
|
||||
sets ip address of external interface. This IP address will
|
||||
be source address for all connections made by proxy.
|
||||
|
|
@ -433,43 +426,44 @@ Alternatively you can use -e option to specify individual
|
|||
address for gateway. Since 0.8 version External or -e can be
|
||||
given twice: once with IPv4 and once with IPv6 address.</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>maxconn</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>maxconn</b>
|
||||
<number> <br>
|
||||
sets maximum number of simulationeous connections to each
|
||||
service started after this command on network level. Default
|
||||
is 100. <br>
|
||||
sets the maximum number of simultaneous connections to each
|
||||
service started after this command at the network level.
|
||||
Default is 100. <br>
|
||||
To limit clients, use connlim instead. maxconn will silently
|
||||
ignore new connections, while connlim will report back to
|
||||
the client that the connection limit has been reached.</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>backlog</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>backlog</b>
|
||||
<br>
|
||||
sets the listening socket backlog of new connections.
|
||||
Default is 1 + maxconn/8. Maximum value is capped by kernel
|
||||
tunable somaxconn.</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>service</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>service</b>
|
||||
<br>
|
||||
(depricated). Indicates 3proxy to behave as Windows
|
||||
95/98/NT/2000/XP service, no effect for Unix. Not required
|
||||
for 3proxy 0.6 and above. If you upgraded from previous
|
||||
version of 3proxy use --remove and --install to reinstall
|
||||
service.</p>
|
||||
(deprecated). Indicates that 3proxy should behave as a
|
||||
Windows 95/98/NT/2000/XP service; has no effect under Unix.
|
||||
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.</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>daemon</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>daemon</b>
|
||||
<br>
|
||||
Should be specified to close console. Do not use
|
||||
Should be specified to close the console. Do not use
|
||||
´daemon´ with ´service´. At least
|
||||
under FreeBSD ´daemon´ should preceed any proxy
|
||||
service and log commands to avoid sockets problem. Always
|
||||
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.</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>auth</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>auth</b>
|
||||
<authtype> [...] <br>
|
||||
Type of user authorization. Currently supported: <br>
|
||||
none - no authentication or authorization required. <br>
|
||||
Note: is auth is none any ip based limitation, redirection,
|
||||
etc will not work. This is default authentication type <br>
|
||||
Note: if auth is none, any IP-based limitation, redirection,
|
||||
etc. will not work. This is the default authentication type
|
||||
<br>
|
||||
iponly - authentication by access control list with username
|
||||
ignored. <br>
|
||||
Appropriate for most cases <br>
|
||||
|
|
@ -477,12 +471,12 @@ useronly - authentication by username without checking for
|
|||
any password with authorization by ACLs. Useful for e.g.
|
||||
SOCKSv4 proxy and icqpr (icqpr set UIN / AOL screen name as
|
||||
a username) <br>
|
||||
dnsname - authentication by DNS hostnname with authorization
|
||||
by ACLs. DNS hostname is resolved via PTR (reverse) record
|
||||
and validated (resolved name must resolve to same IP
|
||||
address). It´s recommended to use authcache by ip for
|
||||
this authentication. NB: there is no any password check,
|
||||
name may be spoofed. <br>
|
||||
dnsname - authentication by DNS hostname with authorization
|
||||
by ACLs. The DNS hostname is resolved via a PTR (reverse)
|
||||
record and validated (the resolved name must resolve to the
|
||||
same IP address). It´s recommended to use authcache by
|
||||
IP for this authentication. NB: there is no password check;
|
||||
the name may be spoofed. <br>
|
||||
strong - username/password authentication required. It will
|
||||
work with SOCKSv5, FTP, POP3 and HTTP proxy. <br>
|
||||
cache - cached authentication, may be used with
|
||||
|
|
@ -490,24 +484,24 @@ cache - cached authentication, may be used with
|
|||
radius - authentication with RADIUS. <br>
|
||||
Plugins may add additional authentication types.</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">It´s
|
||||
possible to use few authentication types in the same
|
||||
commands. E.g. <br>
|
||||
<p style="margin-left:6%; margin-top: 1em">It´s
|
||||
possible to use multiple authentication types in the same
|
||||
command. E.g. <br>
|
||||
auth iponly strong <br>
|
||||
In this case ´strong´ authentication will be
|
||||
used only in case resource access can not be performed with
|
||||
´iponly´ authentication, that is username is
|
||||
required in ACL. It´s usefull to protect access to
|
||||
some resources with password allowing passwordless access to
|
||||
another resources, or to use IP-based authentication for
|
||||
dedicated laptops and request username/password for shared
|
||||
ones.</p>
|
||||
In this case, ´strong´ authentication will be
|
||||
used only if resource access cannot be performed with
|
||||
´iponly´ authentication, that is, a username is
|
||||
required in the ACL. It´s useful to protect access to
|
||||
some resources with a password while allowing passwordless
|
||||
access to other resources, or to use IP-based authentication
|
||||
for dedicated laptops and request a username/password for
|
||||
shared ones.</p>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>authcache</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>authcache</b>
|
||||
<cachtype> <cachtime> <br>
|
||||
Cache authentication information to given amount of time
|
||||
(cachetime) in seconds. Cahtype is one of: <br>
|
||||
Cache authentication information for a given amount of time
|
||||
(cachetime) in seconds. Cachetype is one of: <br>
|
||||
ip - after successful authentication all connections during
|
||||
caching time from same IP are assigned to the same user,
|
||||
username is not requested. <br>
|
||||
|
|
@ -525,7 +519,7 @@ ext - cache external IP <br>
|
|||
Use auth type ´cache´ for cached
|
||||
authentication</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>allow</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>allow</b>
|
||||
<userlist> <sourcelist> <targetlist>
|
||||
<targetportlist> <operationlist>
|
||||
<weekdayslist> <timeperiodslist> <b><br>
|
||||
|
|
@ -538,13 +532,13 @@ spaces are allowed. Usernames are case sensitive (if used
|
|||
with authtype nbname username must be in uppercase). Source
|
||||
and target lists may contain IP addresses (W.X.Y.Z), ranges
|
||||
A.B.C.D - W.X.Y.Z (since 0.8) or CIDRs (W.X.Y.Z/L). Since
|
||||
0.6, targetlist may also contain host names, instead of
|
||||
addresses. It´s possible to use wildmask in the
|
||||
begginning and in the the end of hostname, e.g. *badsite.com
|
||||
or *badcontent*. Hostname is only checked if hostname
|
||||
presents in request. Targetportlist may contain ports (X) or
|
||||
port ranges lists (X-Y). For any field * sign means ANY. If
|
||||
access list is empty it´s assumed to be <br>
|
||||
0.6, the targetlist may also contain host names, instead of
|
||||
addresses. It´s possible to use a wildmask in the
|
||||
beginning and at the end of the hostname, e.g. *badsite.com
|
||||
or *badcontent*. The hostname is only checked if a hostname
|
||||
is present in the request. Targetportlist may contain ports
|
||||
(X) or port ranges lists (X-Y). For any field * sign means
|
||||
ANY. If access list is empty it´s assumed to be <br>
|
||||
allow * <br>
|
||||
If access list is not empty last item in access list is
|
||||
assumed to be <br>
|
||||
|
|
@ -557,8 +551,8 @@ specific addresses immediately without any conditions you
|
|||
should either bind proxy to appropriate interface only or to
|
||||
use ip filters.</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">Operation is
|
||||
one of: <br>
|
||||
<p style="margin-left:6%; margin-top: 1em">Operation is one
|
||||
of: <br>
|
||||
CONNECT establish outgoing TCP connection <br>
|
||||
BIND bind TCP port for listening <br>
|
||||
UDPASSOC make UDP association <br>
|
||||
|
|
@ -575,20 +569,20 @@ FTP_GET FTP get request <br>
|
|||
FTP_PUT FTP put request <br>
|
||||
FTP_LIST FTP list request <br>
|
||||
FTP_DATA FTP data connection. Note: FTP_DATA requires access
|
||||
to dynamic non-ptivileged (1024-65535) ports on remote side.
|
||||
<br>
|
||||
to dynamic non-privileged (1024-65535) ports on the remote
|
||||
side. <br>
|
||||
FTP matches any FTP/FTP Data request <br>
|
||||
ADMIN access to administration interface</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">Weeksdays are
|
||||
week days numbers or periods, 0 or 7 means Sunday, 1 is
|
||||
<p style="margin-left:6%; margin-top: 1em">Weekdays are
|
||||
week day numbers or periods, 0 or 7 means Sunday, 1 is
|
||||
Monday, 1-5 means Monday through Friday. <br>
|
||||
Timeperiodlists is a list of time periods in
|
||||
HH:MM:SS-HH:MM:SS format. For example,
|
||||
00:00:00-08:00:00,17:00:00-24:00:00 lists non-working
|
||||
hours.</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>parent</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>parent</b>
|
||||
<weight> <type> <ip> <port>
|
||||
<username> <password> <br>
|
||||
this command must follow "allow" rule. It extends
|
||||
|
|
@ -597,9 +591,9 @@ grouped. Proxy inside the group is selected randomly. If few
|
|||
groups are specified one proxy is randomly picked from each
|
||||
group and chain of proxies is created (that is second proxy
|
||||
connected through first one and so on). Weight is used to
|
||||
group proxies. Weigt is a number between 1 and 1000. Weights
|
||||
are summed and proxies are grouped together untill weight of
|
||||
group is 1000. That is: <br>
|
||||
group proxies. Weight is a number between 1 and 1000.
|
||||
Weights are summed and proxies are grouped together until
|
||||
the weight of the group is 1000. That is: <br>
|
||||
allow * <br>
|
||||
parent 500 socks5 192.168.10.1 1080 <br>
|
||||
parent 500 connect 192.168.10.1 3128 <br>
|
||||
|
|
@ -618,12 +612,12 @@ connections. Chains are only applied to new connections,
|
|||
pipelined (keep-alive) requests in the same connection use
|
||||
the same chain.</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">type is one of:
|
||||
<p style="margin-left:6%; margin-top: 1em">type is one of:
|
||||
<br>
|
||||
extip does not actully redirect request, it sets external
|
||||
address for this request to <ip>. It can be chained
|
||||
with another parent types. It’s usefaul to set
|
||||
external IP based on ACL or make it random. <br>
|
||||
extip does not actually redirect the request; it sets the
|
||||
external address for this request to <ip>. It can be
|
||||
chained with another parent type. It’s useful to set
|
||||
the external IP based on ACL or make it random. <br>
|
||||
tcp simply redirect connection. TCP is always last in chain.
|
||||
This type of proxy is a simple TCP redirection, it does not
|
||||
support parent authentication. <br>
|
||||
|
|
@ -643,10 +637,10 @@ socks4+ parent is SOCKSv4 proxy with name resolution
|
|||
socks5 parent is SOCKSv5 proxy <br>
|
||||
socks5+ parent is SOCKSv5 proxy with name resolution <br>
|
||||
socks4b parent is SOCKS4b (broken SOCKSv4 implementation
|
||||
with shortened server reply. I never saw this kind ofservers
|
||||
byt they say there are). Normally you should not use this
|
||||
option. Do not mess this option with SOCKSv4a (socks4+).
|
||||
<br>
|
||||
with shortened server reply; I never saw this kind of
|
||||
server, but they say there are some). Normally you should
|
||||
not use this option. Do not confuse this option with
|
||||
SOCKSv4a (socks4+). <br>
|
||||
socks5b parent is SOCKS5b (broken SOCKSv5 implementation
|
||||
with shortened server reply. I think you will never find it
|
||||
useful). Never use this option unless you know exactly you
|
||||
|
|
@ -656,7 +650,7 @@ admin redirect request to local ´admin´ service
|
|||
Use "+" proxy only with "fakeresolve"
|
||||
option</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">IP and port are
|
||||
<p style="margin-left:6%; margin-top: 1em">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
|
||||
|
|
@ -665,18 +659,19 @@ special case of local redirection, it works only with
|
|||
<b>socks</b> proxy. In case of local redirection request is
|
||||
redirected to different service, <b>ftp</b> locally
|
||||
redirects to <b>ftppr pop3</b> locally redirects to <b>pop3p
|
||||
http</b> locally redurects to <b>proxy admin</b> locally
|
||||
redirects to admin -s service.</p>
|
||||
http</b> locally redirects to <b>proxy admin</b> locally
|
||||
redirects to the admin -s service.</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">Main purpose of
|
||||
local redirections is to have requested resource (URL or
|
||||
POP3 username) logged and protocol-specific filters to be
|
||||
applied. In case of local redirection ACLs are revied twice:
|
||||
first, by SOCKS proxy up to ´parent´ command and
|
||||
then with gateway service connection is redirected (HTTP,
|
||||
FTP or POP3) after ´parent´ command. It means,
|
||||
additional ´allow´ command is required for
|
||||
redirected requests, for example: <br>
|
||||
<p style="margin-left:6%; margin-top: 1em">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:
|
||||
first, by the SOCKS proxy up to the ´parent´
|
||||
command and then by the gateway service the connection is
|
||||
redirected to (HTTP, FTP or POP3) after the
|
||||
´parent´ command. It means an additional
|
||||
´allow´ command is required for redirected
|
||||
requests, for example: <br>
|
||||
allow * * * 80 <br>
|
||||
parent 1000 http 0.0.0.0 0 <br>
|
||||
allow * * * 80 HTTP_GET,HTTP_POST <br>
|
||||
|
|
@ -685,20 +680,20 @@ redirects all SOCKS requests with target port 80 to local
|
|||
HTTP proxy, local HTTP proxy parses requests and allows only
|
||||
GET and POST requests. <br>
|
||||
parent 1000 http 1.2.3.4 0 <br>
|
||||
Changes external address for given connection to 1.2.3.4 (an
|
||||
equivalent to -e1.2.3.4) <br>
|
||||
Changes the external address for a given connection to
|
||||
1.2.3.4 (equivalent to -e1.2.3.4) <br>
|
||||
Optional username and password are used to authenticate on
|
||||
parent proxy. Username of ´*´ means username
|
||||
must be supplied by user.</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>nolog</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>nolog</b>
|
||||
<n> <br>
|
||||
extends last allow or deny command to prevent logging, e.g.
|
||||
<br>
|
||||
allow * * 192.168.1.1 <br>
|
||||
nolog</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>weight</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>weight</b>
|
||||
<n> <br>
|
||||
extends last allow or deny command to set weight for this
|
||||
request <br>
|
||||
|
|
@ -706,7 +701,7 @@ allow * * 192.168.1.1 <br>
|
|||
weight 100 <br>
|
||||
Weight may be used for different purposes.</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>force <br>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>force <br>
|
||||
noforce</b> <br>
|
||||
If force is specified for service, configuration reload will
|
||||
require all current sessions of this service to be
|
||||
|
|
@ -716,7 +711,7 @@ closed. noforce allows to keep previously authenticated
|
|||
connections.</p>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>bandlimin</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>bandlimin</b>
|
||||
<rate> <userlist> <sourcelist>
|
||||
<targetlist> <targetportlist>
|
||||
<operationlist> <weekdayslist>
|
||||
|
|
@ -733,30 +728,31 @@ nobandlimout</b> <userlist> <sourcelist>
|
|||
<targetlist> <targetportlist>
|
||||
<operationlist> <weekdayslist>
|
||||
<timeperiodslist> <br>
|
||||
bandlim sets bandwith limitation filter to <rate> bps
|
||||
(bits per second) If you want to specife bytes per second -
|
||||
multiply your value to 8. bandlim rules act in a same manner
|
||||
as allow/deny rules except one thing: bandwidth limiting is
|
||||
applied to all services, not to some specific service.
|
||||
bandlimin and nobandlimin applies to incoming traffic
|
||||
bandlimout and nobandlimout applies to outgoing traffic If
|
||||
tou want to ratelimit your clients with IPs 192.168.10.16/30
|
||||
(4 addresses) to 57600 bps you have to specify 4 rules like
|
||||
<br>
|
||||
bandlim sets a bandwidth limitation filter to <rate>
|
||||
bps (bits per second). If you want to specify bytes per
|
||||
second, multiply your value by 8. bandlim rules act in the
|
||||
same manner as allow/deny rules, except for one thing:
|
||||
bandwidth limiting is applied to all services, not to some
|
||||
specific service. bandlimin and nobandlimin apply to
|
||||
incoming traffic <br>
|
||||
bandlimout and nobandlimout apply to outgoing traffic <br>
|
||||
If you want to ratelimit your clients with IPs
|
||||
192.168.10.16/30 (4 addresses) to 57600 bps, you have to
|
||||
specify 4 rules like <br>
|
||||
bandlimin 57600 * 192.168.10.16 <br>
|
||||
bandlimin 57600 * 192.168.10.17 <br>
|
||||
bandlimin 57600 * 192.168.10.18 <br>
|
||||
bandlimin 57600 * 192.168.10.19 <br>
|
||||
and every of you clients will have 56K channel. If you
|
||||
and each of your clients will have a 56K channel. If you
|
||||
specify <br>
|
||||
bandlimin 57600 * 192.168.10.16/30 <br>
|
||||
you will have 56K channel shared between all clients. if you
|
||||
want, for example, to limit all speed ecept access to POP3
|
||||
you can use <br>
|
||||
you will have a 56K channel shared between all clients. If
|
||||
you want, for example, to limit all speed except access to
|
||||
POP3, you can use <br>
|
||||
nobandlimin * * * 110 <br>
|
||||
before the rest of bandlim rules.</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>connlim</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>connlim</b>
|
||||
<rate> <period> <userlist>
|
||||
<sourcelist> <targetlist> <targetportlist>
|
||||
<operationlist> <weekdayslist>
|
||||
|
|
@ -772,13 +768,13 @@ connections. <br>
|
|||
connlim 100 60 * 127.0.0.1 <br>
|
||||
allows 100 connections per minute for 127.0.0.1. <br>
|
||||
connlim 20 0 * 127.0.0.1 <br>
|
||||
allows 20 simulationeous connections for 127.0.0.1. <br>
|
||||
Like with bandlimin, if individual limit is required per
|
||||
client, separate rule mustbe added for every client. Like
|
||||
with nobanlimin, noconnlim adds an exception.</p>
|
||||
allows 20 simultaneous connections for 127.0.0.1. <br>
|
||||
Like with bandlimin, if an individual limit is required per
|
||||
client, a separate rule must be added for every client. Like
|
||||
with nobandlimin, noconnlim adds an exception.</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>counter</b>
|
||||
<filename> <reporttype> <repotname>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>counter</b>
|
||||
<filename> <reporttype> <reportname>
|
||||
<b><br>
|
||||
countin</b> <number> <type> <limit>
|
||||
<userlist> <sourcelist> <targetlist>
|
||||
|
|
@ -805,30 +801,32 @@ nocountall</b> <userlist> <sourcelist>
|
|||
<operationlist> <weekdayslist>
|
||||
<timeperiodslist></p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">counter,
|
||||
countin, nocountin, countout, noucountout, countall,
|
||||
nocountall commands are used to set traffic limit in MB for
|
||||
period of time (day, week or month). Filename is a path to a
|
||||
special file where traffic information is permanently
|
||||
stored. number is sequential number of record in this file.
|
||||
If number is 0 this counter is not preserved in counter file
|
||||
(that is if proxy restarted all counters with 0 are flushed)
|
||||
overwise it should be unique sequential number which points
|
||||
to position of the couter within the file. Type specifies a
|
||||
<p style="margin-left:6%; margin-top: 1em">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
|
||||
path to a special file where traffic information is
|
||||
permanently stored. The number is the sequential number of
|
||||
the record in this file. If the number is 0, this counter is
|
||||
not preserved in the counter file (that is, if the proxy is
|
||||
restarted, all counters with 0 are flushed); otherwise, it
|
||||
should be a unique sequential number which points to the
|
||||
position of the counter within the file. Type specifies a
|
||||
type of counter. Type is one of: <br>
|
||||
H - counter is resetted hourly <br>
|
||||
D - counter is resetted daily <br>
|
||||
W - counter is resetted weekly <br>
|
||||
M - counter is resetted monthely <br>
|
||||
reporttype/repotname may be used to generate traffic
|
||||
reports. Reporttype is one of D,W,M,H(hourly) and repotname
|
||||
specifies filename template for reports. Report is text file
|
||||
with counter values in format: <br>
|
||||
H - counter is reset hourly <br>
|
||||
D - counter is reset daily <br>
|
||||
W - counter is reset weekly <br>
|
||||
M - counter is reset monthly <br>
|
||||
reporttype/reportname may be used to generate traffic
|
||||
reports. Reporttype is one of D, W, M, H (hourly) and
|
||||
reportname specifies the filename template for reports. The
|
||||
report is a text file with counter values in the format:
|
||||
<br>
|
||||
<COUNTERNUMBER> <TRAF> <br>
|
||||
The rest of parameters is identical to
|
||||
bandlim/nobandlim.</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>users</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>users</b>
|
||||
username[:pwtype:password] ... <br>
|
||||
pwtype is one of: <br>
|
||||
none (empty) - use system authentication <br>
|
||||
|
|
@ -843,16 +841,21 @@ users test3:NT:BD7DFBF29A93F93C63CB84790DA00E63</p>
|
|||
<table width="100%" border="0" rules="none" frame="void"
|
||||
cellspacing="0" cellpadding="0">
|
||||
<tr valign="top" align="left">
|
||||
<td width="6%"></td>
|
||||
|
||||
|
||||
<p>Note: double quotes are requiered because password
|
||||
contains $ sign.</p></table>
|
||||
<p>Note: double quotes are required because the password
|
||||
contains a $ sign.</p></td>
|
||||
<td width="88%"></td>
|
||||
<td width="6%">
|
||||
</td></tr>
|
||||
</table>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>flush</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>flush</b>
|
||||
<br>
|
||||
empty active access list. Access list must be flushed avery
|
||||
time you creating new access list for new service. For
|
||||
example: <br>
|
||||
empty the active access list. The access list must be
|
||||
flushed every time you create a new access list for a new
|
||||
service. For example: <br>
|
||||
allow * <br>
|
||||
pop3p <br>
|
||||
flush <br>
|
||||
|
|
@ -860,60 +863,61 @@ allow * 192.168.1.0/24 <br>
|
|||
socks <br>
|
||||
sets different ACLs for <b>pop3p</b> and <b>socks</b></p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>system</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>system</b>
|
||||
<command> <br>
|
||||
execute system command</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>pidfile</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>pidfile</b>
|
||||
<filename> <br>
|
||||
write pid of current process to file. It can be used to
|
||||
manipulate 3proxy with signals under Unix. Currently next
|
||||
signals are available:</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>monitor</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>monitor</b>
|
||||
<filename> <br>
|
||||
If file monitored changes in modification time or size,
|
||||
3proxy reloads configuration within one minute. Any number
|
||||
of files may be monitored.</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>setuid</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>setuid</b>
|
||||
<uid> <br>
|
||||
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.</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>setgid</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>setgid</b>
|
||||
<gid> <br>
|
||||
calls setgid(gid), gid can be numeric or since 0.9
|
||||
groupname. Unix only.</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>chroot</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>chroot</b>
|
||||
<path> [<uid>] [<gid>] <br>
|
||||
calls chroot(path) and sets gid/uid. Unix only. uid/gid
|
||||
supported since 0.9, can be numeric or
|
||||
username/groupname</p>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>stacksize</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>stacksize</b>
|
||||
<value_to_add_to_default_stack_size> <br>
|
||||
Change default size for threads stack. May be required in
|
||||
some situation, e.g. with non-default plugins, on on some
|
||||
platforms (some FreeBSD version may require adjusting stack
|
||||
size due to invalid defined value in system header files,
|
||||
this value is also oftent reqruied to be changed for ODBC
|
||||
and PAM support on Linux. If you experience 3proxy crash on
|
||||
request processing, try to set some positive value. You may
|
||||
start with stacksize 65536 and then find the minimal value
|
||||
for service to work. If you experience memory shortage, you
|
||||
can try to experiment with negative values.</p>
|
||||
Change the default size for thread stacks. May be required
|
||||
in some situations, e.g. with non-default plugins, or on
|
||||
some platforms (some FreeBSD versions may require adjusting
|
||||
the stack size due to an incorrectly defined value in system
|
||||
header files; this value is also often required to be
|
||||
changed for ODBC and PAM support on Linux). If you
|
||||
experience 3proxy crash on request processing, try to set
|
||||
some positive value. You may start with stacksize 65536 and
|
||||
then find the minimal value for the service to work. If you
|
||||
experience memory shortage, you can try to experiment with
|
||||
negative values.</p>
|
||||
|
||||
<h2>PLUGINS
|
||||
<a name="PLUGINS"></a>
|
||||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>plugin</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>plugin</b>
|
||||
<path_to_shared_library> <function_to_call>
|
||||
[<arg1> ...] <br>
|
||||
Loads specified library and calls given export function with
|
||||
|
|
@ -924,19 +928,19 @@ function_to_call must return 0 in case of success, value
|
|||
> 0 to indicate error.</p>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>filtermaxsize</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>filtermaxsize</b>
|
||||
<max_size_of_data_to_filter> <br>
|
||||
If Content-length (or another data length) is greater than
|
||||
given value, no data filtering will be performed thorugh
|
||||
the given value, no data filtering will be performed through
|
||||
filtering plugins to avoid data corruption and/or
|
||||
Content-Length chaging. Default is 1MB (1048576).</p>
|
||||
Content-Length changing. Default is 1MB (1048576).</p>
|
||||
|
||||
<h2>BUGS
|
||||
<a name="BUGS"></a>
|
||||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">Report all bugs
|
||||
<p style="margin-left:6%; margin-top: 1em">Report all bugs
|
||||
to <b>3proxy@3proxy.org</b></p>
|
||||
|
||||
<h2>SEE ALSO
|
||||
|
|
@ -944,7 +948,7 @@ to <b>3proxy@3proxy.org</b></p>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">3proxy(8),
|
||||
<p style="margin-left:6%; margin-top: 1em">3proxy(8),
|
||||
proxy(8), ftppr(8), socks(8), pop3p(8), tcppm(8), udppm(8),
|
||||
syslogd(8), <br>
|
||||
https://3proxy.org/</p>
|
||||
|
|
@ -954,7 +958,7 @@ https://3proxy.org/</p>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">3APA3A is
|
||||
<p style="margin-left:6%; margin-top: 1em">3APA3A is
|
||||
pronounced as ``zaraza´´.</p>
|
||||
|
||||
<h2>AUTHORS
|
||||
|
|
@ -962,7 +966,7 @@ pronounced as ``zaraza´´.</p>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">3proxy is
|
||||
<p style="margin-left:6%; margin-top: 1em">3proxy is
|
||||
designed by Vladimir 3APA3A Dubrovin
|
||||
(<i>3proxy@3proxy.org</i>)</p>
|
||||
<hr>
|
||||
|
|
|
|||
139
3proxy.md
139
3proxy.md
|
|
@ -1,4 +1,4 @@
|
|||
<!-- Creator : groff version 1.22.4 -->
|
||||
<!-- Creator : groff version 1.24.1 -->
|
||||
<html>
|
||||
<head>
|
||||
|
||||
|
|
@ -26,7 +26,7 @@
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>3proxy</b> -
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>3proxy</b> -
|
||||
3[APA3A] tiny proxy server, or trivial proxy server, or free
|
||||
proxy server</p>
|
||||
|
||||
|
|
@ -35,7 +35,7 @@ proxy server</p>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>3proxy</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>3proxy</b>
|
||||
[<i>config_file</i>] <b><br>
|
||||
3proxy</b> [<i>--install</i>] <b><br>
|
||||
3proxy</b> [<i>--remove</i>]</p>
|
||||
|
|
@ -45,41 +45,42 @@ proxy server</p>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>3proxy</b>
|
||||
is universal proxy server. It can be used to provide
|
||||
internal users wuth fully controllable access to external
|
||||
resources or to provide external users with access to
|
||||
internal resources. 3proxy is not developed to replace
|
||||
<b>squid</b>(8), but it can extend functionality of existing
|
||||
cashing proxy. It can be used to route requests between
|
||||
different types of clients and proxy servers. Think about it
|
||||
as application level gateway with configuration like
|
||||
hardware router has for network layer. It can establish
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>3proxy</b> 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
|
||||
resources. 3proxy is not developed to replace
|
||||
<b>squid</b>(8), but it can extend the functionality of an
|
||||
existing caching proxy. It can be used to route requests
|
||||
between different types of clients and proxy servers. Think
|
||||
about it as application level gateway with configuration
|
||||
like hardware router has for network layer. It can establish
|
||||
multiple gateways with HTTP and HTTPS proxy with FTP over
|
||||
HTTP support, SOCKS v4, v4.5 and v5, POP3 proxy, UDP and TCP
|
||||
portmappers. Each gateway is started from configuration file
|
||||
like independant service <b>proxy</b>(8) <b>socks</b>(8)
|
||||
<b>pop3p</b>(8) <b>tcppm</b>(8) <b>udppm</b>(8)
|
||||
<b>ftppr</b>(8) <b>dnspr</b> but <b>3proxy</b> is not a kind
|
||||
of wrapper or superserver for this daemons. It just has same
|
||||
code compiled in, but provides much more functionality.
|
||||
SOCKSv5 implementatation allows to use 3proxy with any UDP
|
||||
or TCP based client applications designed without proxy
|
||||
support (with <i>SocksCAP</i>, <i>FreeCAP</i> or another
|
||||
client-side redirector under Windows of with socksification
|
||||
library under Unix). So you can play your favourite games,
|
||||
listen music, exchange files and messages and even accept
|
||||
incoming connections behind proxy server.</p>
|
||||
portmappers. Each gateway is started from the configuration
|
||||
file like an independent service <b>proxy</b>(8)
|
||||
<b>socks</b>(8) <b>pop3p</b>(8) <b>tcppm</b>(8)
|
||||
<b>udppm</b>(8) <b>ftppr</b>(8) <b>dnspr</b> but
|
||||
<b>3proxy</b> is not a kind of wrapper or superserver for
|
||||
these daemons. It just has the same code compiled in, but
|
||||
provides much more functionality. SOCKSv5 implementation
|
||||
allows you to use 3proxy with any UDP or TCP based client
|
||||
applications designed without proxy support (with
|
||||
<i>SocksCAP</i>, <i>FreeCAP</i> or another client-side
|
||||
redirector under Windows or with a socksification library
|
||||
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.</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><i>dnspr</i>
|
||||
does not exist as independant service. It´ DNS caching
|
||||
proxy (it requires <i>nscache</i> and <i>nserver</i> to be
|
||||
set in configuration. Only A-records are cached. Please
|
||||
note, the this caching is mostly a ’hack’ and
|
||||
has nothing to do with real DNS server, but it works
|
||||
<p style="margin-left:6%; margin-top: 1em"><i>dnspr</i>
|
||||
does not exist as an independent service. It’s a DNS
|
||||
caching proxy (it requires <i>nscache</i> and <i>nserver</i>
|
||||
to be set in the configuration. Only A-records are cached.
|
||||
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.</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">3proxy supports
|
||||
<p style="margin-left:6%; margin-top: 1em">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,10 +93,10 @@ 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.</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">It supports
|
||||
<p style="margin-left:6%; margin-top: 1em">It supports
|
||||
different types of logging: to logfiles, <b>syslog</b>(3)
|
||||
(only under Unix) or to ODBC database. Logging format is
|
||||
turnable to provide compatibility with existing log file
|
||||
(only under Unix) or to an ODBC database. Logging format is
|
||||
tunable to provide compatibility with existing log file
|
||||
parsers. It makes it possible to use 3proxy with IIS, ISA,
|
||||
Apache or Squid log parsers.</p>
|
||||
|
||||
|
|
@ -105,28 +106,28 @@ Apache or Squid log parsers.</p>
|
|||
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>config_file</b></p>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>config_file</b></p>
|
||||
|
||||
<p style="margin-left:22%;">Name of config file. See
|
||||
<p style="margin-left:15%;">Name of config file. See
|
||||
<b>3proxy.cfg</b>(3) for configuration file format. Under
|
||||
Windows, if config_file is not specified, <b>3proxy</b>
|
||||
looks for file named <i>3proxy.cfg</i> in the default
|
||||
location (in same directory with executable file and in
|
||||
current directory). Under Unix, if no config file is
|
||||
looks for a file named <i>3proxy.cfg</i> in the default
|
||||
location (in the same directory as the executable file and
|
||||
in the current directory). Under Unix, if no config file is
|
||||
specified, 3proxy reads configuration from stdin. It makes
|
||||
it possible to use 3proxy.cfg file as executable script just
|
||||
by setting +x mode and adding <br>
|
||||
it possible to use the 3proxy.cfg file as an executable
|
||||
script just by setting +x mode and adding <br>
|
||||
#!/usr/local/3proxy/3proxy <br>
|
||||
as a first line in 3proxy.cfg</p>
|
||||
|
||||
<p style="margin-left:11%;"><b>--install</b></p>
|
||||
<p style="margin-left:6%;"><b>--install</b></p>
|
||||
|
||||
<p style="margin-left:22%;">(Windows NT family only)
|
||||
<p style="margin-left:15%;">(Windows NT family only)
|
||||
install <b>3proxy</b> as a system service</p>
|
||||
|
||||
<p style="margin-left:11%;"><b>--remove</b></p>
|
||||
<p style="margin-left:6%;"><b>--remove</b></p>
|
||||
|
||||
<p style="margin-left:22%;">(Windows NT family only) remove
|
||||
<p style="margin-left:15%;">(Windows NT family only) remove
|
||||
<b>3proxy</b> from system services</p>
|
||||
|
||||
<h2>SIGNALS
|
||||
|
|
@ -134,38 +135,38 @@ install <b>3proxy</b> as a system service</p>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">Under Unix
|
||||
there are few signals <b>3proxy</b> catches. See
|
||||
<b>kill</b>(1). <b><br>
|
||||
<p style="margin-left:6%; margin-top: 1em">Under Unix there
|
||||
are a few signals <b>3proxy</b> catches. See <b>kill</b>(1).
|
||||
<b><br>
|
||||
SIGTERM</b></p>
|
||||
|
||||
<p style="margin-left:22%;">cleanup connections and
|
||||
<p style="margin-left:15%;">clean up connections and
|
||||
exit</p>
|
||||
|
||||
<p style="margin-left:11%;"><b>SIGPAUSE</b></p>
|
||||
<p style="margin-left:6%;"><b>SIGPAUSE</b></p>
|
||||
|
||||
<p style="margin-left:22%;">stop to accept new connections,
|
||||
<p style="margin-left:15%;">stop accepting new connections,
|
||||
on second signal - start and re-read configuration</p>
|
||||
|
||||
<p style="margin-left:11%;"><b>SIGCONT</b></p>
|
||||
<p style="margin-left:6%;"><b>SIGCONT</b></p>
|
||||
|
||||
<p style="margin-left:22%;">start to accept new
|
||||
conenctions</p>
|
||||
<p style="margin-left:15%;">start to accept new
|
||||
connections</p>
|
||||
|
||||
<p style="margin-left:11%;"><b>SIGUSR1</b></p>
|
||||
<p style="margin-left:6%;"><b>SIGUSR1</b></p>
|
||||
|
||||
<p style="margin-left:22%;">reload configuration</p>
|
||||
<p style="margin-left:15%;">reload configuration</p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">Under Windows,
|
||||
if <b>3proxy</b> is installed as service you can standard
|
||||
service management to start, stop, pause and continue 3proxy
|
||||
service, for example: <b><br>
|
||||
<p style="margin-left:6%; margin-top: 1em">Under Windows,
|
||||
if <b>3proxy</b> is installed as a service you can use
|
||||
standard service management to start, stop, pause and
|
||||
continue the 3proxy service, for example: <b><br>
|
||||
net start 3proxy <br>
|
||||
net stop 3proxy <br>
|
||||
net pause 3proxy <br>
|
||||
net continue 3proxy</b></p>
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">Web admin
|
||||
<p style="margin-left:6%; margin-top: 1em">Web admin
|
||||
service can also be used to reload configuration. Use wget
|
||||
to automate this task.</p>
|
||||
|
||||
|
|
@ -175,10 +176,10 @@ to automate this task.</p>
|
|||
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><i>/usr/local/3proxy/3proxy.cfg
|
||||
<p style="margin-left:6%; margin-top: 1em"><i>/usr/local/3proxy/3proxy.cfg
|
||||
(3proxy.cfg)</i></p>
|
||||
|
||||
<p style="margin-left:22%;"><b>3proxy</b> configuration
|
||||
<p style="margin-left:15%;"><b>3proxy</b> configuration
|
||||
file</p>
|
||||
|
||||
<h2>BUGS
|
||||
|
|
@ -186,7 +187,7 @@ file</p>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">Report all bugs
|
||||
<p style="margin-left:6%; margin-top: 1em">Report all bugs
|
||||
to <b>3proxy@3proxy.org</b></p>
|
||||
|
||||
<h2>SEE ALSO
|
||||
|
|
@ -194,7 +195,7 @@ to <b>3proxy@3proxy.org</b></p>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">3proxy.cfg(3),
|
||||
<p style="margin-left:6%; margin-top: 1em">3proxy.cfg(3),
|
||||
proxy(8), ftppr(8), socks(8), pop3p(8), tcppm(8), udppm(8),
|
||||
kill(1), syslogd(8), <br>
|
||||
https://3proxy.org/</p>
|
||||
|
|
@ -204,7 +205,7 @@ https://3proxy.org/</p>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">3APA3A is
|
||||
<p style="margin-left:6%; margin-top: 1em">3APA3A is
|
||||
pronounced as ``zaraza´´.</p>
|
||||
|
||||
<h2>AUTHORS
|
||||
|
|
@ -212,7 +213,7 @@ pronounced as ``zaraza´´.</p>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">3proxy is
|
||||
<p style="margin-left:6%; margin-top: 1em">3proxy is
|
||||
designed by Vladimir 3APA3A Dubrovin
|
||||
(<i>3proxy@3proxy.org</i>)</p>
|
||||
<hr>
|
||||
|
|
|
|||
280
High-Load.md
280
High-Load.md
|
|
@ -1,12 +1,12 @@
|
|||
<h3>Optimizing 3proxy for high load</h3>
|
||||
<p>Precaution 1: 3proxy was not initially developed for high load and is positioned as a SOHO product, the main reason is "one connection - one thread" model 3proxy uses. 3proxy is known to work with above 200,000 connections under proper configuration, but use it in production environment under high loads at your own risk and do not expect too much.
|
||||
<p>Precaution 2: This documentation is incomplete and is not sufficient. High loads may require very specific system tuning including, but not limited to specific or cusomized kernels, builds, settings, sysctls, options, etc. All this is not covered by this documentation.
|
||||
<h3>Optimizing 3proxy for High Load</h3>
|
||||
<p>Precaution 1: 3proxy was not initially developed for high load and is positioned as a SOHO product. The main reason is the "one connection - one thread" model 3proxy uses. 3proxy is known to work with over 200,000 connections under proper configuration, but use it in a production environment under high loads at your own risk and do not expect too much.
|
||||
<p>Precaution 2: This documentation is incomplete and insufficient. High loads may require very specific system tuning including, but not limited to, specific or customized kernels, builds, settings, sysctls, options, etc. All of this is not covered by this documentation.
|
||||
|
||||
<h4>Configuring 'maxconn'</h4>
|
||||
|
||||
A number of simulatineous connections per service is limited by 'maxconn' option.
|
||||
Default maxconn value since 3proxy 0.8 is 500. You may want to set 'maxconn'
|
||||
to higher value. Under this configuration:
|
||||
The number of simultaneous connections per service is limited by the 'maxconn' option.
|
||||
The default maxconn value since 3proxy 0.8 is 500. You may want to set 'maxconn'
|
||||
to a higher value. Under this configuration:
|
||||
<pre>
|
||||
maxconn 1000
|
||||
proxy -p3129
|
||||
|
|
@ -14,53 +14,53 @@ proxy -p3128
|
|||
socks
|
||||
</pre>
|
||||
maxconn for every service is 1000, and there are 3 services running
|
||||
(2 proxy and 1 socks), so, for all services there can be up to 3000
|
||||
simulatineous connections to 3proxy.
|
||||
<p>Avoid setting 'maxconn' to arbitrary high value, it should be carefully
|
||||
choosen to protect system and proxy from resources exhaution. Setting maxconn
|
||||
above resources available can lead to denial of service conditions.
|
||||
<h4>Understanding resources requirements</h4>
|
||||
Each running service require:
|
||||
(2 proxy and 1 socks), so for all services there can be up to 3000
|
||||
simultaneous connections to 3proxy.
|
||||
<p>Avoid setting 'maxconn' to an arbitrarily high value; it should be carefully
|
||||
chosen to protect the system and proxy from resource exhaustion. Setting maxconn
|
||||
above available resources can lead to denial of service conditions.
|
||||
<h4>Understanding Resource Requirements</h4>
|
||||
Each running service requires:
|
||||
<ul>
|
||||
<li>1*thread (process)
|
||||
<li>1*socket (file descriptor)
|
||||
<li>1 thread (process)
|
||||
<li>1 socket (file descriptor)
|
||||
<li>1 stack memory segment + some heap memory, ~64K-128K depending on the system
|
||||
</ul>
|
||||
Each connected client require:
|
||||
Each connected client requires:
|
||||
<ul>
|
||||
<li>1*thread (process)
|
||||
<li>2*socket (file descriptor). For FTP 4 sockets are required.
|
||||
<br>Under linux since 0.9 splice() is used. It's much more effective, but requires
|
||||
<br>2*socket (file descriptor) + 2*pipe (file descriptors) = 4 file descriptors.
|
||||
<br>For FTP 4 sockets and 2 pipes are required with splice().
|
||||
<br>Up to 128K (up to 256K in the case of splice()) of kernel buffers memory. This is theoretical maximum, actual numbers depend on connection quality and traffic amount.
|
||||
<li>1 thread (process)
|
||||
<li>2 sockets (file descriptors). For FTP, 4 sockets are required.
|
||||
<br>Under Linux since 0.9, splice() is used. It's much more efficient but requires
|
||||
<br>2 sockets (file descriptors) + 2 pipes (file descriptors) = 4 file descriptors.
|
||||
<br>For FTP with splice(), 4 sockets and 2 pipes are required.
|
||||
<br>Up to 128K (up to 256K in the case of splice()) of kernel buffer memory. This is the theoretical maximum; actual numbers depend on connection quality and traffic amount.
|
||||
<br>1 additional socket (file descriptor) during name resolution for non-cached names
|
||||
<br>1 additional socket during authentication or logging for RADIUS authentication or logging.
|
||||
<li>1*ephemeral port (3*ephemeral ports for FTP connection).
|
||||
<li>1 stack memory segment of ~32K-128K depending on the system + at least 16K and up to few MB (for 'proxy' and 'ftppr') of heap memory. If you are short of memory, prefer 'socks' to 'proxy' and 'ftppr'.
|
||||
<li>a lot of system buffers, specially in the case of slow network connections.
|
||||
<li>1 ephemeral port (3 ephemeral ports for FTP connections).
|
||||
<li>1 stack memory segment of ~32K-128K depending on the system + at least 16K and up to a few MB (for 'proxy' and 'ftppr') of heap memory. If you are short on memory, prefer 'socks' over 'proxy' and 'ftppr'.
|
||||
<li>Many system buffers, especially in the case of slow network connections.
|
||||
</ul>
|
||||
Also, additional resources like system buffers are required for network activity.
|
||||
|
||||
<h4>Setting ulimits</h4>
|
||||
|
||||
Hard and soft ulimits must be set above calculated requirements. Under Linux, you can
|
||||
check limits of running process with
|
||||
check the limits of a running process with
|
||||
<pre>
|
||||
cat /proc/PID/limits
|
||||
</pre>
|
||||
where PID is a pid of the process.
|
||||
Validate ulimits match your expectation, especially if you run 3proxy under dedicated account
|
||||
by adding e.g.
|
||||
where PID is the process ID.
|
||||
Validate that ulimits match your expectations, especially if you run 3proxy under a dedicated account
|
||||
by adding, e.g.:
|
||||
<pre>
|
||||
system "ulimit -Ha >>/tmp/3proxy.ulim.hard"
|
||||
system "ulimit -Sa >>/tmp/3proxy.ulim.soft"
|
||||
</pre>
|
||||
in the beginning (before first service started) and the end of config file.
|
||||
Make both hard restart (that is kill and start 3proxy process) and soft restart
|
||||
by sending SIGUSR1 to 3proxy process, check ulimits recorded to files match your
|
||||
expecation. In systemd based distros (e.g. latest Debian / Ubuntu) changing limits.conf
|
||||
is not enough, limits must be ajusted in systemd configuration, e.g. by setting
|
||||
at the beginning (before the first service is started) and at the end of the config file.
|
||||
Perform both a hard restart (i.e., kill and start the 3proxy process) and a soft restart
|
||||
by sending SIGUSR1 to the 3proxy process; check that the ulimits recorded to files match your
|
||||
expectations. In systemd-based distros (e.g., latest Debian/Ubuntu), changing limits.conf
|
||||
is not enough; limits must be adjusted in the systemd configuration, e.g., by setting:
|
||||
<pre>
|
||||
DefaultLimitDATA=infinity
|
||||
DefaultLimitSTACK=infinity
|
||||
|
|
@ -73,51 +73,51 @@ DefaultLimitMEMLOCK=infinity
|
|||
</pre>
|
||||
in user.conf / system.conf
|
||||
|
||||
<h4>Extending system limitation</h4>
|
||||
<h4>Extending System Limitations</h4>
|
||||
|
||||
Check manuals / documentation for your system limitations e.g. system-wide limit for number of open files
|
||||
Check the manuals/documentation for your system's limitations, e.g., the system-wide limit for the number of open files
|
||||
(fs.file-max in Linux). You may need to change sysctls or even rebuild the kernel from source.
|
||||
<p>
|
||||
To help with socket-based system-dependant settings, since 0.9-devel 3proxy supports different
|
||||
socket options which can be set via -ol option for listening socket, -oc for proxy-to-client
|
||||
socket and -os for proxy-to-server socket. Example:
|
||||
To help with socket-based system-dependent settings, since 0.9-devel, 3proxy supports different
|
||||
socket options which can be set via the -ol option for the listening socket, -oc for the proxy-to-client
|
||||
socket, and -os for the proxy-to-server socket. Example:
|
||||
<pre>
|
||||
proxy -olSO_REUSEADDR,SO_REUSEPORT -ocTCP_TIMESTAMPS,TCP_NODELAY -osTCP_NODELAY
|
||||
</pre>
|
||||
available options are system dependant.
|
||||
Available options are system-dependent.
|
||||
|
||||
<h4>Using 3proxy in virtual environment</h4>
|
||||
<h4>Using 3proxy in a Virtual Environment</h4>
|
||||
|
||||
If 3proxy is used in VPS environment, there can be additional limitations.
|
||||
For example, kernel resources / system CPU usage / IOCTLs can be limited in a different way, and this can become a bottleneck.
|
||||
Since 0.9 devel, 3proxy uses splice() by default on Linux, splice() prevents network traffic from being copied from
|
||||
kernel space to 3proxy process and generally increases throughput, epecially in the case of high volume traffic. It especially
|
||||
true for virtual environment (it can improve thoughput up to 10 times) unless there are additional kernel limitations.
|
||||
Since some work is moved to kernel, it requires up to 2 times more kernel resources in terms of CPU, memory and IOCTLs.
|
||||
If your hosting additionally limits kernel resources (you can see it as nearly 100% CPU usage without any real CPU activity for
|
||||
any application which performs IOCTLS), use -s0 option to disable splice() usage for given service e.g.
|
||||
<pre>
|
||||
If 3proxy is used in a VPS environment, there can be additional limitations.
|
||||
For example, kernel resources, system CPU usage, and IOCTLs can be limited differently, and this can become a bottleneck.
|
||||
Since 0.9-devel, 3proxy uses splice() by default on Linux. splice() prevents network traffic from being copied from
|
||||
kernel space to the 3proxy process and generally increases throughput, especially in the case of high-volume traffic. This is especially
|
||||
true for virtual environments (it can improve throughput up to 10 times) unless there are additional kernel limitations.
|
||||
Since some work is moved to the kernel, it requires up to 2 times more kernel resources in terms of CPU, memory, and IOCTLs.
|
||||
If your hosting additionally limits kernel resources (you can see this as nearly 100% CPU usage without any real CPU activity for
|
||||
any application performing IOCTLs), use the -s0 option to disable splice() usage for a given service, e.g.:
|
||||
<pre>
|
||||
socks -s0
|
||||
</pre>
|
||||
|
||||
<h4>Extending ephemeral port range</h4>
|
||||
<h4>Extending the Ephemeral Port Range</h4>
|
||||
|
||||
Check ephemeral port range for your system and extend it to the number of the
|
||||
Check the ephemeral port range for your system and extend it to the number of
|
||||
ports required.
|
||||
Ephimeral range is always limited to maximum number of ports (64K). To extend the
|
||||
number of outgoing connections above this limit, extending ephemeral port range
|
||||
is not enough, you need additional actions:
|
||||
The ephemeral range is always limited to the maximum number of ports (64K). To extend the
|
||||
number of outgoing connections above this limit, extending the ephemeral port range
|
||||
is not enough; you need additional actions:
|
||||
<ol>
|
||||
<li> Configure multiple outgoing IPs
|
||||
<li> Make sure 3proxy is configured to use different outgoing IP by either setting
|
||||
external IP via RADIUS
|
||||
<li> Make sure 3proxy is configured to use a different outgoing IP by either setting
|
||||
the external IP via RADIUS:
|
||||
<pre>
|
||||
radius secret 1.2.3.4
|
||||
auth radius
|
||||
proxy
|
||||
</pre>
|
||||
or by using multiple services with different external
|
||||
interfaces, example:
|
||||
interfaces, for example:
|
||||
<pre>
|
||||
allow user1,user11,user111
|
||||
proxy -p1111 -e1.1.1.1
|
||||
|
|
@ -133,7 +133,7 @@ proxy -p4444 -e4.4.4.4
|
|||
flush
|
||||
</pre>
|
||||
or via "parent extip" rotation,
|
||||
e.g.
|
||||
e.g.:
|
||||
<pre>
|
||||
allow user1,user11,user111
|
||||
parent 1000 extip 1.1.1.1 0
|
||||
|
|
@ -156,8 +156,8 @@ socks
|
|||
</pre>
|
||||
<pre>
|
||||
</pre>
|
||||
Under latest Linux version you can also start multiple services with different
|
||||
external addresses on the single port with SO_REUSEPORT on listening socket to
|
||||
Under the latest Linux versions, you can also start multiple services with different
|
||||
external addresses on a single port with SO_REUSEPORT on the listening socket to
|
||||
evenly distribute incoming connections between outgoing interfaces:
|
||||
<pre>
|
||||
socks -olSO_REUSEPORT -p3128 -e 1.1.1.1
|
||||
|
|
@ -165,136 +165,136 @@ socks -olSO_REUSEPORT -p3128 -e 2.2.2.2
|
|||
socks -olSO_REUSEPORT -p3128 -e 3.3.3.3
|
||||
socks -olSO_REUSEPORT -p3128 -e 4.4.4.4
|
||||
</pre>
|
||||
for Web browsing last two examples are not recommended, because same client can get
|
||||
different external address for different requests, you should choose external
|
||||
For web browsing, the last two examples are not recommended because the same client can get
|
||||
a different external address for different requests; you should choose the external
|
||||
interface with user-based rules instead.
|
||||
<li> You may need additional system dependant actions to use same port on different IPs,
|
||||
usually by adding SO_REUSEADDR (SO_PORT_SCALABILITY for Windows) socket option to
|
||||
external socket. This option can be set (since 0.9 devel) with -os option:
|
||||
<li> You may need additional system-dependent actions to use the same port on different IPs,
|
||||
usually by adding the SO_REUSEADDR (SO_PORT_SCALABILITY for Windows) socket option to
|
||||
the external socket. This option can be set (since 0.9-devel) with the -os option:
|
||||
<pre>
|
||||
proxy -p3128 -e1.2.3.4 -osSO_REUSEADDR
|
||||
</pre>
|
||||
Behavior for SO_REUSEADDR and SO_REUSEPORT is different between different system,
|
||||
even between different kernel versions and can lead to unexpected results.
|
||||
Specifics is described <a href="https://stackoverflow.com/questions/14388706/socket-options-so-reuseaddr-and-so-reuseport-how-do-they-differ-do-they-mean-t">here</a>.
|
||||
Use this options only if actually required and if you fully understand possible
|
||||
consiquences. E.g. SO_REUSEPORT can help to establish more connections than the
|
||||
number of the client port available, but it can also lead to situation connections
|
||||
are randomely fail due to ip+port pairs collision if remote or local system
|
||||
The behavior for SO_REUSEADDR and SO_REUSEPORT is different between different systems,
|
||||
even between different kernel versions, and can lead to unexpected results.
|
||||
The specifics are described <a href="https://stackoverflow.com/questions/14388706/socket-options-so-reuseaddr-and-so-reuseport-how-do-they-differ-do-they-mean-t">here</a>.
|
||||
Use these options only if actually required and if you fully understand the possible
|
||||
consequences. For example, SO_REUSEPORT can help establish more connections than the
|
||||
number of client ports available, but it can also lead to situations where connections
|
||||
randomly fail due to IP+port pair collisions if the remote or local system
|
||||
doesn't support this trick.
|
||||
</ol>
|
||||
|
||||
<h4>Setting stacksize</h4>
|
||||
<h4>Setting Stack Size</h4>
|
||||
|
||||
'stacksize' is a size added to all stack allocations and can be both positive and
|
||||
negative. Stack is required in functions call. 3proxy itself doesn't require large
|
||||
negative. Stack is required for function calls. 3proxy itself doesn't require a large
|
||||
stack, but it can be required if some
|
||||
purely-written libc, 3rd party libraries or system functions called. There is known\
|
||||
poorly written libc, 3rd party libraries, or system functions are called. There is known
|
||||
dirty code in Unix ODBC
|
||||
implementations, build-in DNS resolvers, especially in the case of IPv6 and large
|
||||
number of interfaces. Under most 64-bit system extending stacksize will lead
|
||||
to additional memory space usage, but do not require actual commited memory,
|
||||
so you can inrease stacksize to relatively large value (e.g. 1024000) without
|
||||
the need to add additional phisical memory,
|
||||
but it's system/libc dependant and requires additional testing under your
|
||||
installation. Don't forget about memory related ulimts.
|
||||
<p>For 32-bit systems address space can be a bottlneck you should consider. If
|
||||
you're short of address space you can try to use negative stack size.
|
||||
implementations and built-in DNS resolvers, especially in the case of IPv6 and a large
|
||||
number of interfaces. Under most 64-bit systems, extending stacksize will lead
|
||||
to additional memory space usage but does not require actual committed memory,
|
||||
so you can increase stacksize to a relatively large value (e.g., 1024000) without
|
||||
the need to add additional physical memory,
|
||||
but it's system/libc dependent and requires additional testing under your
|
||||
installation. Don't forget about memory-related ulimits.
|
||||
<p>For 32-bit systems, address space can be a bottleneck you should consider. If
|
||||
you're short on address space, you can try using a negative stack size.
|
||||
|
||||
<h4>Known system issues</h4>
|
||||
<h4>Known System Issues</h4>
|
||||
|
||||
There are known race condition issues in Linux / glibc resolver. The probability
|
||||
of race condition arises under configuration with IPv6, large number of interfaces
|
||||
or IP addresses or resolvers configured. In this case, install local recursor and
|
||||
use 3proxy built-in resolver (nserver / nscache / nscache6).
|
||||
<h4>Do not use public resolvers</h4>
|
||||
Public resolvers like ones from Google have ratelimits. For large number of
|
||||
requests install local caching recursor (ISC bind named, PowerDNS recursor, etc).
|
||||
There are known race condition issues in the Linux/glibc resolver. The probability
|
||||
of a race condition arises under configuration with IPv6, a large number of interfaces
|
||||
or IP addresses, or with resolvers configured. In this case, install a local recursor and
|
||||
use 3proxy's built-in resolver (nserver / nscache / nscache6).
|
||||
<h4>Do Not Use Public Resolvers</h4>
|
||||
Public resolvers like those from Google have rate limits. For a large number of
|
||||
requests, install a local caching recursor (ISC bind named, PowerDNS recursor, etc).
|
||||
|
||||
<h4>Avoid large lists</h4>
|
||||
<h4>Avoid Large Lists</h4>
|
||||
|
||||
Currently, 3proxy is not optimized to use large ACLs, user lists, etc. All lists
|
||||
are processed lineary. In devel version you can use RADIUS authentication to avoid
|
||||
user lists and ACLs in 3proxy itself. Also, RADIUS allows to easily set outgoing IP
|
||||
on per-user basis or more sophisicated logics.
|
||||
RADIUS is a new beta feature, test it before using in production.
|
||||
are processed linearly. In the devel version, you can use RADIUS authentication to avoid
|
||||
user lists and ACLs in 3proxy itself. Also, RADIUS allows you to easily set an outgoing IP
|
||||
on a per-user basis or implement more sophisticated logic.
|
||||
RADIUS is a new beta feature; test it before using it in production.
|
||||
|
||||
<h4>Avoid changing configuration too often</h4>
|
||||
<h4>Avoid Changing Configuration Too Often</h4>
|
||||
|
||||
Every configuration reload requires additional resources. Do not do frequent
|
||||
changes, like users addition/deletaion via connfiguration, use alternative
|
||||
Every configuration reload requires additional resources. Do not make frequent
|
||||
changes, such as user addition/deletion via configuration; use alternative
|
||||
authentication methods instead, like RADIUS.
|
||||
|
||||
<h4>Consider using 'noforce'</h4>
|
||||
<h4>Consider Using 'noforce'</h4>
|
||||
|
||||
'force' behaviour (default) re-authenticates all connections after
|
||||
configuration reload, it may be resource consuming on large number of
|
||||
connections. Consider adding 'noforce' command before services started
|
||||
to prevent connections reauthentication.
|
||||
The 'force' behavior (default) re-authenticates all connections after
|
||||
configuration reload; it may be resource-consuming with a large number of
|
||||
connections. Consider adding the 'noforce' command before services are started
|
||||
to prevent connection re-authentication.
|
||||
|
||||
<h4>Do not monitor configuration files directly</h4>
|
||||
<h4>Do Not Monitor Configuration Files Directly</h4>
|
||||
|
||||
Using configuration file directly in 'monitor' can lead to race condition where
|
||||
configuration is reloaded while file is being written.
|
||||
Using a configuration file directly in 'monitor' can lead to a race condition where
|
||||
the configuration is reloaded while the file is being written.
|
||||
To avoid race conditions:
|
||||
<ol>
|
||||
<li> Update config files only if there is no lock file
|
||||
<li> Create lock file then 3proxy configuration is updated, e.g. with
|
||||
<li> Create a lock file when the 3proxy configuration is updated, e.g., with
|
||||
"touch /some/path/3proxy/3proxy.lck". If you generate config files
|
||||
asynchronously, e.g. by user's request via web, you should consider
|
||||
implementing existance checking and file creation as atomic operation.
|
||||
<li>add
|
||||
asynchronously, e.g., by a user's request via web, you should consider
|
||||
implementing existence checking and file creation as an atomic operation.
|
||||
<li> Add
|
||||
<pre>
|
||||
system "rm /some/path/3proxy/3proxy.lck"
|
||||
</pre>
|
||||
at the end of config file to remove it after configuration is successfully loaded
|
||||
<li> Use a dedicated version file to monitor, e.g.
|
||||
at the end of the config file to remove it after the configuration is successfully loaded
|
||||
<li> Use a dedicated version file to monitor, e.g.:
|
||||
<pre>
|
||||
monitor "/some/path/3proxy/3proxy.ver"
|
||||
</pre>
|
||||
<li> After config is updated, change version file for 3proxy to reload configuration,
|
||||
e.g. with "touch /some/path/3proxy/3proxy.ver".
|
||||
<li> After the config is updated, change the version file for 3proxy to reload the configuration,
|
||||
e.g., with "touch /some/path/3proxy/3proxy.ver".
|
||||
</ol>
|
||||
|
||||
<h4>Use TCP_NODELAY to speed-up connections with small amount of data</h4>
|
||||
<h4>Use TCP_NODELAY to Speed Up Connections with Small Amounts of Data</h4>
|
||||
|
||||
If most requests require exchange with a small amount of data in a both ways
|
||||
without the need for bandwidth, e.g. messengers or small web request,
|
||||
you can eliminate Nagle's algorithm delay with TCP_NODELAY flag. Usage example:
|
||||
If most requests require an exchange with a small amount of data in both directions
|
||||
without the need for bandwidth, e.g., messengers or small web requests,
|
||||
you can eliminate Nagle's algorithm delay with the TCP_NODELAY flag. Usage example:
|
||||
<pre>
|
||||
proxy -osTCP_NODELAY -ocTCP_NODELAY
|
||||
</pre>
|
||||
sets TCP_NODELAY for client (oc) and server (os) connections.
|
||||
<p>Do not use TCP_NODELAY on slow connections with high delays and then
|
||||
<p>Do not use TCP_NODELAY on slow connections with high delays when
|
||||
connection bandwidth is a bottleneck.
|
||||
|
||||
<h4>Use splice to speedup large data amount transfers</h4>
|
||||
<h4>Use Splice to Speed Up Large Data Amount Transfers</h4>
|
||||
|
||||
splice() allows to copy data between connections without copying to process
|
||||
addres space. It can speedup proxy on high bandwidth connections, if most
|
||||
splice() allows copying data between connections without copying to the process
|
||||
address space. It can speed up the proxy on high-bandwidth connections if most
|
||||
connections require large data transfers. Splice is enabled by default on Linux
|
||||
since 0.9, "-s0" disables splice usage. Example:
|
||||
since 0.9; "-s0" disables splice usage. Example:
|
||||
<pre>
|
||||
proxy -s0
|
||||
</pre>
|
||||
Splice is only available on Linux. Splice requires more system buffers and file descriptors,
|
||||
Splice is only available on Linux. Splice requires more system buffers and file descriptors
|
||||
and produces more IOCTLs but reduces process memory and overall CPU usage.
|
||||
Disable splice if there is a lot of short-living connections with no bandwidth
|
||||
Disable splice if there are a lot of short-lived connections with no bandwidth
|
||||
requirements.
|
||||
<p>Use splice only on high-speed connections (e.g. 10GBE), if processor, memory speed or
|
||||
<p>Use splice only on high-speed connections (e.g., 10GbE) when the processor, memory speed, or
|
||||
system bus are bottlenecks.
|
||||
<p>TCP_NODELAY and splice are not contrary to each over and should be combined on
|
||||
<p>TCP_NODELAY and splice are not contrary to each other and should be combined on
|
||||
high-speed connections.
|
||||
|
||||
<h4>Add grace delay to reduce system calls<h4>
|
||||
<h4>Add Grace Delay to Reduce System Calls</h4>
|
||||
|
||||
<pre>proxy -g8000,3,10</pre>
|
||||
First parameter is average read size we want to keep, second parameter is
|
||||
minimal number of packets in the same direction to apply algorythm,
|
||||
last value is delay added after polling and prior to reading data.
|
||||
An example above adds 10 millisecond delay before reading data if average
|
||||
polling size is below 8000 bytes and 3 read operations are made in the same
|
||||
direction. It's specially usefule with splice. <pre>logdump 1 1</pre> is useful
|
||||
to see how grace delays work, choose delay value to avoid filling the read
|
||||
pipe/buffer (typically 64K) but keep the request sizes close to chosen average
|
||||
on large file upload/download.
|
||||
The first parameter is the average read size we want to keep, the second parameter is
|
||||
the minimal number of packets in the same direction to apply the algorithm,
|
||||
and the last value is the delay added after polling and prior to reading data.
|
||||
The example above adds a 10-millisecond delay before reading data if the average
|
||||
polling size is below 8000 bytes and 3 read operations have been made in the same
|
||||
direction. It's especially useful with splice. <pre>logdump 1 1</pre> is useful
|
||||
to see how grace delays work; choose a delay value to avoid filling the read
|
||||
pipe/buffer (typically 64K) but keep the request sizes close to the chosen average
|
||||
on large file uploads/downloads.
|
||||
|
|
|
|||
File diff suppressed because it is too large
Load diff
|
|
@ -219,7 +219,7 @@
|
|||
<li>Служба уже установлена или запущена
|
||||
</ul>
|
||||
</p>
|
||||
<li><a name="INTEXT">Как разобраться с internal и external</a></li></li>
|
||||
<li><a name="INTEXT">Как разобраться с internal и external</a></li>
|
||||
<p>
|
||||
Убедитесь, что выправильно понимаете что такое internal и external адреса.
|
||||
Оба адреса - это адреса, принадлежищие хосту, на котором установлен 3proxy.
|
||||
|
|
|
|||
|
|
@ -56,7 +56,7 @@ PCRE_BSR_UNICODE
|
|||
<li>srvdata - данные полученные от сервера, например содержимое HTML-страницы
|
||||
</ul>
|
||||
<li>FILTER_ACTION - действие при совпадении. Может принимать значение
|
||||
<ul>allow - разрешить данный запрос без просмотра дальнейших правил
|
||||
<ul><li>allow - разрешить данный запрос без просмотра дальнейших правил
|
||||
<li>deny - запретить данный запрос без просмотра дальнейших правил
|
||||
<li>dunno - продолжить анализ правил (полезно для pcre_rewrite)
|
||||
</ul>
|
||||
|
|
@ -87,4 +87,4 @@ pcre_extend deny * 192.168.0.1/16
|
|||
<ul>
|
||||
<li>Плагин включен в дистрибутив 3proxy 0.6
|
||||
<li>Пример конфигурации (by Dennis Garber): <A HREF="NoPornLitest.cfg.txt">NoPornLitest.cfg</A>
|
||||
</ul>
|
||||
</li></ul>
|
||||
|
|
|
|||
|
|
@ -1,9 +1,9 @@
|
|||
|
||||
<h3>3proxy Perl Compatible Regular Expressions (PCRE) plugin</h3>
|
||||
<h3>3proxy Perl Compatible Regular Expressions (PCRE) Plugin</h3>
|
||||
|
||||
This filtering plugin can be used to create matching and replace
|
||||
rules with regular expressions for client's request, client and
|
||||
servers header and client and server data. It adds 3 additional
|
||||
This filtering plugin can be used to create matching and replacement
|
||||
rules with regular expressions for client requests, client and
|
||||
server headers, and client and server data. It adds 3 additional
|
||||
configuration commands:
|
||||
|
||||
<pre>
|
||||
|
|
@ -12,11 +12,11 @@ pcre_rewrite TYPE FILTER_ACTION REGEXP REWRITE_EXPRESSION [ACE]
|
|||
pcre_extend FILTER_ACTION [ACE]
|
||||
pcre_options OPTION1 [...]
|
||||
</pre>
|
||||
pcre - allows to apply some rule for matching
|
||||
<br>pcre_rewrite - in addition to 'pcre' allows to substitute substrings
|
||||
<br>pcre_extend - extends ACL of the last pcre or pcre_rewrite comand by
|
||||
adding additional ACE (like with allow/deny configuration commands).
|
||||
<br>pcre_options - allows to set matching options. Awailable options are:
|
||||
pcre - allows applying a rule for matching
|
||||
<br>pcre_rewrite - in addition to 'pcre', allows substituting substrings
|
||||
<br>pcre_extend - extends the ACL of the last pcre or pcre_rewrite command by
|
||||
adding an additional ACE (like with allow/deny configuration commands).
|
||||
<br>pcre_options - allows setting matching options. Available options are:
|
||||
PCRE_CASELESS,
|
||||
PCRE_MULTILINE,
|
||||
PCRE_DOTALL,
|
||||
|
|
@ -32,7 +32,7 @@ PCRE_UTF8,
|
|||
PCRE_NO_AUTO_CAPTURE,
|
||||
PCRE_NO_UTF8_CHECK,
|
||||
PCRE_AUTO_CALLOUT,
|
||||
PCRE_PARTIAL,
|
||||
PCRE_PARTIAL,
|
||||
PCRE_DFA_SHORTEST,
|
||||
PCRE_DFA_RESTART,
|
||||
PCRE_FIRSTLINE,
|
||||
|
|
@ -47,32 +47,31 @@ PCRE_BSR_UNICODE
|
|||
|
||||
<ul>
|
||||
<li>TYPE - type of filtered data. May contain one or more
|
||||
(comma delimited list) values:
|
||||
(comma-delimited list) values:
|
||||
<ul>
|
||||
<li>request - content of client's request e.g. HTTP GET request string.
|
||||
(known problem: changing request string doesn't change IP of the host to connect)
|
||||
<li>cliheader - content of client request headers, e.g. HTTP request header.
|
||||
<li>srvheader - content of server's reply headers, e.g. HTTP status and headers.
|
||||
<li>clidata - data received from client, e.g. HTTP POST request data
|
||||
<li>srvdata - data received from server, e.g. HTML page
|
||||
<li>request - content of the client's request, e.g., the HTTP GET request string.
|
||||
(known problem: changing the request string doesn't change the IP of the host to connect to)
|
||||
<li>cliheader - content of the client request headers, e.g., HTTP request headers.
|
||||
<li>srvheader - content of the server's reply headers, e.g., HTTP status and headers.
|
||||
<li>clidata - data received from the client, e.g., HTTP POST request data
|
||||
<li>srvdata - data received from the server, e.g., an HTML page
|
||||
</ul>
|
||||
<li>FILTER_ACTION - action on match
|
||||
<ul>allow - allow this request without checking rest of the given type
|
||||
of the rules
|
||||
<li>deny - deny this request without checking rest of the rules
|
||||
<li>dunno - continue with the rest of rules (useful with pcre_rewrite)
|
||||
<ul><li>allow - allow this request without checking the rest of the rules for the given type
|
||||
<li>deny - deny this request without checking the rest of the rules
|
||||
<li>dunno - continue with the rest of the rules (useful with pcre_rewrite)
|
||||
</ul>
|
||||
<li>REGEXP - PCRE (perl) regular expression. Use * if no regexp matching
|
||||
required.
|
||||
<li>REWRITE_EXPRESSION - substitution string. May contain perl-style
|
||||
<li>REGEXP - PCRE (Perl) regular expression. Use * if no regexp matching
|
||||
is required.
|
||||
<li>REWRITE_EXPRESSION - substitution string. May contain Perl-style
|
||||
substrings
|
||||
(not tested) $1, $2. $0 - means whole matched string. \r and \n may be used
|
||||
to insert new strings, string may be empty ("").
|
||||
(not tested) $1, $2. $0 means the whole matched string. \r and \n may be used
|
||||
to insert new strings; the string may be empty ("").
|
||||
<li>ACE - access control entry (user names, source IPs, destination IPs,
|
||||
ports, etc), absolutely identical to allow/deny/bandlimin commands.
|
||||
Regular expression is only matched if ACL matches connection data.
|
||||
ports, etc.), absolutely identical to allow/deny/bandlimin commands.
|
||||
The regular expression is only matched if the ACL matches the connection data.
|
||||
Warning:
|
||||
reqular expression doesn't require authentication and can not replace
|
||||
Regular expressions don't require authentication and cannot replace
|
||||
authentication and/or allow/deny ACLs.
|
||||
</ul>
|
||||
|
||||
|
|
@ -88,7 +87,7 @@ pcre_extend deny * 192.168.0.1/16
|
|||
|
||||
<h4>Download:</h4>
|
||||
<ul>
|
||||
<li>Plugin is included into 3proxy 0.6 binary and source distribution
|
||||
<li>Plugin is included in the 3proxy 0.6 binary and source distribution
|
||||
<li>Example configuration (by Dennis Garber): <A HREF="NoPornLitest.cfg.txt">NoPornLitest.cfg</A>
|
||||
</ul>
|
||||
</li></ul>
|
||||
|
||||
|
|
|
|||
46
SSLPlugin.md
46
SSLPlugin.md
|
|
@ -1,6 +1,6 @@
|
|||
<h3>3proxy SSL/TLS plugin</h3>
|
||||
<h3>3proxy SSL/TLS Plugin</h3>
|
||||
|
||||
Plugin can be used to transparently decypher SSL/TLS data and TLS encryption for proxy traffic.
|
||||
This plugin can be used to transparently decrypt SSL/TLS data and provide TLS encryption for proxy traffic.
|
||||
|
||||
|
||||
|
||||
|
|
@ -9,35 +9,35 @@ Plugin can be used to transparently decypher SSL/TLS data and TLS encryption for
|
|||
<br>ssl_mitm - spoof certificates for services started below. Usage without ssl_client_verify is insecure.
|
||||
<br>ssl_nomitm - do not spoof certificates for services started below
|
||||
|
||||
<h4>To protect traffic to server (https:// proxy) - since 0.9.5 version</h4>
|
||||
<h4>To protect traffic to the server (https:// proxy) - since version 0.9.5</h4>
|
||||
ssl_serv - require TLS connection for services below
|
||||
<br>ssl_noserv - do not require TLS connection for services below
|
||||
|
||||
Parameters:
|
||||
<br>ssl_server_cert /path/to/cert - Server certificate (should not be selfsigned and must contain Alternative name) for ssl_serv
|
||||
<br>ssl_server_key /path/to/key - Server ceritifacte key for ssl_server_cert or generated mitm certificate
|
||||
<br>ssl_client_ciphersuites ciphersuites_list - TLS client ciphers for TLS 1.3, e.g. ssl_client_ciphersuites TLS_AES_128_GCM_SHA256
|
||||
<br>ssl_server_cert /path/to/cert - Server certificate (should not be self-signed and must contain an Alternative Name) for ssl_serv
|
||||
<br>ssl_server_key /path/to/key - Server certificate key for ssl_server_cert or generated MITM certificate
|
||||
<br>ssl_client_ciphersuites ciphersuites_list - TLS client ciphers for TLS 1.3, e.g., ssl_client_ciphersuites TLS_AES_128_GCM_SHA256
|
||||
<br>ssl_server_ciphersuites ciphersuites_list - TLS server ciphers for TLS 1.3
|
||||
<br>ssl_client_cipher_list ciphersuites_list - TLS client ciphers for TLS 1.2 and below , e.g. ssl_client_cipher_list ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-CHACHA20-POLY1305
|
||||
<br>ssl_client_cipher_list ciphersuites_list - TLS client ciphers for TLS 1.2 and below, e.g., ssl_client_cipher_list ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-CHACHA20-POLY1305
|
||||
<br>ssl_server_cipher_list ciphersuites_list - TLS server ciphers for TLS 1.2 and below
|
||||
<br>ssl_client_min_proto_version tls_version - TLS client min TLS version (e.g. TLSv1.2)
|
||||
<br>ssl_server_min_proto_version tls_version - TLS server min TLS version (e.g. TLSv1.2)
|
||||
<br>ssl_client_max_proto_version tls_version - TLS client max TLS version (e.g. TLSv1.2)
|
||||
<br>ssl_server_max_proto_version tls_version - TLS server max TLS version (e.g. TLSv1.2)
|
||||
<br>ssl_client_verify - verify certificate for upstream server in TLS client functionality (used with ssl_mitm)
|
||||
<br>ssl_client_no_verify - do not verify certificate for upstream server in TLS client functionality (default)
|
||||
<br>ssl_server_ca_file /path/to/cafile - CA certificate file for mitm
|
||||
<br>ssl_server_ca_key /path/to/cakey - key for ssl_server_ca_file mitm CA
|
||||
<br>ssl_client_min_proto_version tls_version - TLS client minimum TLS version (e.g., TLSv1.2)
|
||||
<br>ssl_server_min_proto_version tls_version - TLS server minimum TLS version (e.g., TLSv1.2)
|
||||
<br>ssl_client_max_proto_version tls_version - TLS client maximum TLS version (e.g., TLSv1.2)
|
||||
<br>ssl_server_max_proto_version tls_version - TLS server maximum TLS version (e.g., TLSv1.2)
|
||||
<br>ssl_client_verify - verify the certificate for the upstream server in TLS client functionality (used with ssl_mitm)
|
||||
<br>ssl_client_no_verify - do not verify the certificate for the upstream server in TLS client functionality (default)
|
||||
<br>ssl_server_ca_file /path/to/cafile - CA certificate file for MITM
|
||||
<br>ssl_server_ca_key /path/to/cakey - key for ssl_server_ca_file MITM CA
|
||||
<br>ssl_client_ca_file, ssl_client_ca_dir, ssl_client_ca_store - locations for root CAs used with ssl_client_verify for TLS client
|
||||
<br>ssl_certcache /path/to/cache/ - location for generated mitm certificates cache, optional, if ssl_server_ca_file / ssl_server_ca_key are configured.
|
||||
Cache may contain 3 files: 3proxy.pem - public
|
||||
self-signed certificates (used if ssl_server_ca_file is not configured),
|
||||
3proxy.key - key for public certificates, used if ssl_server_ca_keyserver.key is not configured, server.key - this key is used if ssl_server_key is not configured to generates
|
||||
<br>ssl_certcache /path/to/cache/ - location for the generated MITM certificates cache, optional if ssl_server_ca_file / ssl_server_ca_key are configured.
|
||||
The cache may contain 3 files: 3proxy.pem - public
|
||||
self-signed certificates (used if ssl_server_ca_file is not configured),
|
||||
3proxy.key - key for public certificates, used if ssl_server_ca_key is not configured, server.key - this key is used if ssl_server_key is not configured to generate
|
||||
spoofed certificates. If server.key is absent, 3proxy.key is used to generate certificates.
|
||||
Generated certificates are placed to the same path.
|
||||
Generated certificates are placed in the same path.
|
||||
|
||||
|
||||
<h4>mitm example:</h4>
|
||||
<h4>MITM example:</h4>
|
||||
<pre>
|
||||
plugin /path/to/SslPlugin.dll ssl_plugin
|
||||
ssl_server_ca_file /path/to/cafile
|
||||
|
|
@ -47,7 +47,7 @@ proxy -p3128
|
|||
ssl_nomitm
|
||||
proxy -p3129
|
||||
</pre>
|
||||
mitm's traffic with spoofed ceritifacate for port 3128 proxy.
|
||||
MITM's traffic with a spoofed certificate for the port 3128 proxy.
|
||||
|
||||
<h4>https:// proxy example:</h4>
|
||||
<pre>
|
||||
|
|
@ -59,6 +59,6 @@ proxy -p33128
|
|||
ssl_noserv
|
||||
proxy -p3128
|
||||
</pre>
|
||||
creates https:// proxy on 33128 and http:// proxy on 3128
|
||||
Creates an https:// proxy on port 33128 and an http:// proxy on port 3128
|
||||
|
||||
© Vladimir Dubrovin, License: BSD style
|
||||
|
|
|
|||
|
|
@ -1,35 +1,33 @@
|
|||
<h3>3proxy security considirations</h3>
|
||||
</ul>
|
||||
<h3>3proxy Security Considerations</h3>
|
||||
<ul>
|
||||
<li>Never install 3proxy suid. If you need it to run suid write some
|
||||
wrapper with fixed configuration file.
|
||||
<li>Make configuration file only available to account 3proxy starts with.
|
||||
<li>Under Windows if 3proxy is used as service create new
|
||||
unprivileged local account without "logon locally" right. Assign this account
|
||||
to 3proxy service.
|
||||
<li>Under unix use chroot to jail 3proxy (make sure files included in
|
||||
configuration file after 'chroot' command, if any, are available from jail)
|
||||
<li>Under Unix, either start 3proxy with unprivileged account or, if you need
|
||||
<li>Never install 3proxy suid. If you need it to run suid, write a
|
||||
wrapper with a fixed configuration file.
|
||||
<li>Make the configuration file accessible only to the account 3proxy starts with.
|
||||
<li>Under Windows, if 3proxy is used as a service, create a new
|
||||
unprivileged local account without "logon locally" rights. Assign this account
|
||||
to the 3proxy service.
|
||||
<li>Under Unix, use chroot to jail 3proxy (make sure files included in
|
||||
the configuration file after the 'chroot' command, if any, are available from within the jail).
|
||||
<li>Under Unix, either start 3proxy with an unprivileged account or, if you need
|
||||
some privileged ports to be used by 3proxy, use setgid/setuid commands inside
|
||||
3proxy.cfg immediately after last occurance of service binded to
|
||||
privileged port in configuration file (setgid must preceed setuid).
|
||||
<li>Allways use full paths in configuration file
|
||||
3proxy.cfg immediately after the last occurrence of a service bound to a
|
||||
privileged port in the configuration file (setgid must precede setuid).
|
||||
<li>Always use full paths in the configuration file.
|
||||
<li>Try to avoid 'strong' authentication, because only cleartext
|
||||
authentication method is currently available.
|
||||
authentication is currently available.
|
||||
<li>Always specify internal and external interfaces.
|
||||
<li>Always limit connections to internal network and localhost (to 127.0.0.1 and
|
||||
all interfaces) with ACLs. Be carefull, because BIND command in SOCKS requies
|
||||
BIND method with external interface IP address to be allowed.
|
||||
<li> Before 3proxy 0.8 always use nserver and nscache under Unix, overwise DoS attack is possible
|
||||
with unreachable DNS server (because gethostbyname will block over threads).
|
||||
<li>Keep logs in secure location, because some confidential information from
|
||||
user's request can be logged.
|
||||
<li>Always limit connections to the internal network and localhost (to 127.0.0.1 and
|
||||
all interfaces) with ACLs. Be careful, because the BIND command in SOCKS requires the
|
||||
BIND method with the external interface IP address to be allowed.
|
||||
<li>Before 3proxy 0.8, always use nserver and nscache under Unix; otherwise, a DoS attack is possible
|
||||
with an unreachable DNS server (because gethostbyname will block other threads).
|
||||
<li>Keep logs in a secure location, because some confidential information from
|
||||
user requests can be logged.
|
||||
<li>Use -xyz+A character filtering sequences for 'logformat', especially with
|
||||
ODBC logging to prevent SQL and log record injections.
|
||||
<li>Immediately report all service crashes to developers
|
||||
ODBC logging, to prevent SQL and log record injections.
|
||||
<li>Immediately report all service crashes to the developers.
|
||||
<li>Participate in code audit :)
|
||||
</ol>
|
||||
|
||||
</ul>
|
||||
|
||||
<p>
|
||||
|
||||
|
|
|
|||
|
|
@ -15,4 +15,4 @@ plugin "StringsPlugin.dll" start c:\3proxy\bin\rus-win1251.3ps
|
|||
<h4>Загрузить:</h4>
|
||||
<ul>
|
||||
<li>Плагин включен в дистрибутив 3proxy 0.6
|
||||
</ul>
|
||||
</li></ul>
|
||||
|
|
|
|||
|
|
@ -1,16 +1,16 @@
|
|||
|
||||
<h3>3proxy strings substitution plugin</h3>
|
||||
May be used to make interface more pretty or to translate proxy server
|
||||
messages to different language. All messages are taken from proxy.c and
|
||||
moved to external text file (e.g. rus.3ps). On the moment of
|
||||
writing there are 15 sections. Sections are delimited with "[end]".
|
||||
<h4>Example:</h4>
|
||||
<pre>plugin "StringsPlugin.dll" start c:\3proxy\bin\rus.3ps
|
||||
</pre>
|
||||
|
||||
<h4>Download:</h4>
|
||||
<ul>
|
||||
<li>Plugin is included into 3proxy 0.6 binary and source distribution
|
||||
</li></ul>
|
||||
|
||||
©Kirill Lopuchov
|
||||
|
||||
<h3>3proxy Strings Substitution Plugin</h3>
|
||||
This may be used to make the interface more attractive or to translate proxy server
|
||||
messages to a different language. All messages are taken from proxy.c and
|
||||
moved to an external text file (e.g., rus.3ps). At the time of
|
||||
writing, there are 15 sections. Sections are delimited with "[end]".
|
||||
<h4>Example:</h4>
|
||||
<pre>plugin "StringsPlugin.dll" start c:\3proxy\bin\rus.3ps
|
||||
</pre>
|
||||
|
||||
<h4>Download:</h4>
|
||||
<ul>
|
||||
<li>Plugin is included in the 3proxy 0.6 binary and source distribution
|
||||
</li></ul>
|
||||
|
||||
© Kirill Lopuchov
|
||||
|
|
|
|||
|
|
@ -46,7 +46,7 @@ trafcorrect p <сервис> <tcp/udp> <исходящий пор
|
|||
Когда происходит окончание соединения выполняется первое подходящее правило.
|
||||
</ol>
|
||||
Подсчет трафика в любом режиме не является точным, это некоторая аппроксимация
|
||||
позволяющаяподсчитать трафик с точностью до нескольких процентов.
|
||||
позволяющая подсчитать трафик с точностью до нескольких процентов.
|
||||
|
||||
<h4>Пример:</h4>
|
||||
<pre>
|
||||
|
|
@ -66,4 +66,4 @@ trafcorrect m socks5 6112 4.5
|
|||
<h4>Загрузить:</h4>
|
||||
<ul>
|
||||
<li>Плагин включен в дистрибутив 3proxy 0.6
|
||||
</ul>
|
||||
</li></ul>
|
||||
|
|
|
|||
|
|
@ -1,15 +1,15 @@
|
|||
<h3>3proxy traffic correction plugin</h3>
|
||||
3proxy logs and counts traffic on application level, while provider usually does
|
||||
it on network or link level. It's significant if you use 3proxy for billing,
|
||||
especially in case where network packets are small, e.g. network games.
|
||||
<h3>3proxy Traffic Correction Plugin</h3>
|
||||
3proxy logs and counts traffic at the application level, while providers usually do
|
||||
so at the network or link level. This is significant if you use 3proxy for billing,
|
||||
especially in cases where network packets are small, e.g., online games.
|
||||
<p>
|
||||
This plugin attempts to correct 3proxy computations to approximate network or
|
||||
link level traffic by using either fixed coefficients by port number or
|
||||
attempting to predict number and sizes of network packets.
|
||||
This plugin attempts to correct 3proxy's computations to approximate network or
|
||||
link-level traffic by using either fixed coefficients by port number or
|
||||
by attempting to predict the number and sizes of network packets.
|
||||
</p><h4>Usage:</h4>
|
||||
<ol>
|
||||
<li>Extract TrafficPlugin.dll to the same folder with 3proxy executable.
|
||||
</li><li>Start plugin in 3proxy.cfg with
|
||||
<li>Extract TrafficPlugin.dll to the same folder as the 3proxy executable.
|
||||
</li><li>Start the plugin in 3proxy.cfg with:
|
||||
<pre>plugin TrafficPlugin.dll start
|
||||
</pre>
|
||||
</li><li>Add correction rules:
|
||||
|
|
@ -17,36 +17,36 @@ attempting to predict number and sizes of network packets.
|
|||
FOR FIXED COEFFICIENTS MODE:
|
||||
<pre>trafcorrect m <service> <target port> <coefficient>
|
||||
</pre>
|
||||
where <service> - one of proxy, socks4, socks45, socks5, tcppm, udppm, pop3p, * matches "any".
|
||||
<br> <target port> - target port, * matches any
|
||||
where <service> - one of proxy, socks4, socks45, socks5, tcppm, udppm, pop3p; * matches "any".
|
||||
<br> <target port> - target port; * matches any
|
||||
<br> <coefficient> - coefficient to multiply traffic for this port.
|
||||
<br>
|
||||
FOR PACKET HEADER PREDICTION MODE
|
||||
FOR PACKET HEADER PREDICTION MODE:
|
||||
<pre>trafcorrect p <service> <tcp/udp> <target port> [empty packet size]
|
||||
</pre>
|
||||
tcp ot udp - transport level protocol to apply rule
|
||||
tcp or udp - transport-level protocol to apply the rule to
|
||||
<br>
|
||||
empty packet size - average size of "empty" packet, that is sum of average network/transport headers.
|
||||
You can use network sniffer, such is Ethereal to discover it. Usually packet size
|
||||
is 42 for UDP and
|
||||
empty packet size - average size of an "empty" packet, i.e., the sum of average network/transport headers.
|
||||
You can use a network sniffer such as Ethereal to discover it. Usually, the packet size
|
||||
is 42 for UDP and
|
||||
<br>Modes can be mixed.
|
||||
<br>Plugin creates a list of rules, first matching rule will be applied.
|
||||
<br>The plugin creates a list of rules; the first matching rule will be applied.
|
||||
</li></ol>
|
||||
For any mode plugin approximates traffic, logged or counted amount is not exact.
|
||||
For any mode, the plugin approximates traffic; the logged or counted amount is not exact.
|
||||
<h4>Example:</h4>
|
||||
<pre>plugin "TrafficPlugin.dll" start
|
||||
trafcorrect m socks5 6112 4.5
|
||||
trafcorrect m socks5 * 1.1
|
||||
</pre>
|
||||
wrong usage:
|
||||
Wrong usage:
|
||||
<pre>trafcorrect m socks5 * 1.1
|
||||
trafcorrect m socks5 6112 4.5
|
||||
</pre>
|
||||
second rule will never be applied.
|
||||
The second rule will never be applied.
|
||||
<h4>Download:</h4>
|
||||
<ul>
|
||||
<li>Plugin is included into 3proxy 0.6 binary and source distribution
|
||||
<li>Plugin is included in the 3proxy 0.6 binary and source distribution
|
||||
</li></ul>
|
||||
|
||||
©Maslov Michael aka Flexx(rus)
|
||||
© Maslov Michael aka Flexx(rus)
|
||||
|
||||
|
|
@ -28,6 +28,6 @@ HTTP-запросов по порту TCP/80 будут видны параме
|
|||
<h4>Загрузить:</h4>
|
||||
<ul>
|
||||
<li>Плагин включен в дистрибутив 3proxy 0.8
|
||||
</ul>
|
||||
</li></ul>
|
||||
|
||||
© Vladimir Dubrovin, License: BSD style
|
||||
|
|
|
|||
|
|
@ -1,9 +1,9 @@
|
|||
<h3>3proxy TransparentPlugin plugin (Linux/BSD only)</h3>
|
||||
<h3>3proxy TransparentPlugin (Linux/BSD only)</h3>
|
||||
|
||||
Plugin can turn 3proxy into transparent proxy for virtually any TCP-based protocol
|
||||
This plugin can turn 3proxy into a transparent proxy for virtually any TCP-based protocol
|
||||
and use all 3proxy features - redirections, parent proxies, ACLs, traffic limitations,
|
||||
etc. TransparentPlugin plugin takes destination IP:port from Linux and uses this
|
||||
information as a target IP in proxy. An example of usage:
|
||||
etc. The TransparentPlugin takes the destination IP:port from Linux and uses this
|
||||
information as the target IP in the proxy. An example usage:
|
||||
|
||||
<pre>
|
||||
plugin /path/to/TransparentPlugin.ld.so transparent_plugin
|
||||
|
|
@ -19,13 +19,13 @@ notransparent
|
|||
proxy
|
||||
</pre>
|
||||
Now, any TCP traffic transparently redirected to port 12345 will be routed via
|
||||
parent SOCKSv5 proxy and logged, all URLs for web requests are visible in logs.
|
||||
Paremeters '127.0.0.1 11111' in this case are not used and are overwritten by
|
||||
destination IP:port for each transparent connection.
|
||||
the parent SOCKSv5 proxy and logged; all URLs for web requests are visible in logs.
|
||||
The parameters '127.0.0.1 11111' in this case are not used and are overwritten by
|
||||
the destination IP:port for each transparent connection.
|
||||
|
||||
<h4>Download:</h4>
|
||||
<ul>
|
||||
<li>Plugin included into 3proxy 0.8
|
||||
</ul>
|
||||
<li>Plugin is included in 3proxy 0.8
|
||||
</li></ul>
|
||||
|
||||
© Vladimir Dubrovin, License: BSD style
|
||||
|
|
|
|||
|
|
@ -31,5 +31,5 @@ auth windows
|
|||
<h4>Загрузить:</h4>
|
||||
<ul>
|
||||
<li>Плагин включен в дистрибутив 3proxy 0.6
|
||||
</ul>
|
||||
</li></ul>
|
||||
|
||||
|
|
|
|||
|
|
@ -1,33 +1,33 @@
|
|||
|
||||
<h3>3proxy Windows Authentication plugin</h3>
|
||||
Support for cleartext authentication against Windows domain or local Windows account.
|
||||
<h3>3proxy Windows Authentication Plugin</h3>
|
||||
Support for cleartext authentication against a Windows domain or local Windows account.
|
||||
<h4>Usage:</h4>
|
||||
<ol>
|
||||
<li>Extract WindowsAuthentication.dll to the same folder with 3proxy executable.
|
||||
<li>Create 3ProxyAllowedGroup - Windows system group allowed to use proxy.
|
||||
You can choose different group name. Group can be either local or
|
||||
<li>Extract WindowsAuthentication.dll to the same folder as the 3proxy executable.
|
||||
<li>Create 3ProxyAllowedGroup - a Windows system group allowed to use the proxy.
|
||||
You can choose a different group name. The group can be either local or
|
||||
Active Directory. Every account allowed to use 3proxy must be included in this
|
||||
group either directly or through group nesting.
|
||||
<li>Configure plugin with 'plugin' command in 3proxy.cfg, e.g.:
|
||||
<li>Configure the plugin with the 'plugin' command in 3proxy.cfg, e.g.:
|
||||
<pre><code>
|
||||
plugin "WindowsAuthentication.dll" WindowsAuthentication "3ProxyAllowedGroup"
|
||||
</code></pre>
|
||||
<br>WindowsAuthentication.dll - location of DLL, if DLL is located in different folder
|
||||
from 3proxy.exe you must specify complete path to DLL here. 3ProxyAllowedGroup - Windows
|
||||
<br>WindowsAuthentication.dll - location of the DLL; if the DLL is located in a different folder
|
||||
from 3proxy.exe, you must specify the complete path to the DLL here. 3ProxyAllowedGroup - the Windows
|
||||
system group allowed to use 3proxy.
|
||||
After plugin is loaded, 'windows' authentication type is supported.
|
||||
After the plugin is loaded, the 'windows' authentication type is supported.
|
||||
|
||||
<li>Configure 'auth windows' for services that require Windows authentication.
|
||||
<li>It's recommended you also configure authentication caching (see 'authcache'),
|
||||
to prevent excessive workload for domain controller. Example:
|
||||
<li>It is recommended that you also configure authentication caching (see 'authcache')
|
||||
to prevent excessive workload on the domain controller. Example:
|
||||
<pre>
|
||||
authcache user,pass 900
|
||||
auth cache windows
|
||||
</pre>
|
||||
|
||||
<li>NTLM authentication is not currently supported for plugins, you should use proxy -n key to disable it.
|
||||
<li>NTLM authentication is not currently supported for plugins; you should use the proxy -n switch to disable it.
|
||||
</ol>
|
||||
<h4>Download:</h4>
|
||||
<ul>
|
||||
<li>Plugin is included into 3proxy 0.6 binary and source distribution
|
||||
</ul>
|
||||
<li>Plugin is included in the 3proxy 0.6 binary and source distribution
|
||||
</li></ul>
|
||||
162
ftppr.md
162
ftppr.md
|
|
@ -1,4 +1,4 @@
|
|||
<!-- Creator : groff version 1.22.4 -->
|
||||
<!-- Creator : groff version 1.24.1 -->
|
||||
<html>
|
||||
<head>
|
||||
|
||||
|
|
@ -24,7 +24,7 @@
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>ftppr</b> -
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>ftppr</b> -
|
||||
FTP proxy gateway service</p>
|
||||
|
||||
<h2>SYNOPSIS
|
||||
|
|
@ -32,7 +32,7 @@ FTP proxy gateway service</p>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>ftppr</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>ftppr</b>
|
||||
[<b>-d</b>] [<b>-l</b>[[<i>@</i>]<i>logfile</i>]]
|
||||
[<b>-p</b><i>port</i>] [<b>-i</b><i>internal_ip</i>]
|
||||
[<b>-e</b><i>external_ip</i>]
|
||||
|
|
@ -43,7 +43,7 @@ FTP proxy gateway service</p>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>ftppr</b> is
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>ftppr</b> is
|
||||
FTP gateway service to allow internal users to access
|
||||
external FTP servers.</p>
|
||||
|
||||
|
|
@ -55,128 +55,131 @@ external FTP servers.</p>
|
|||
<table width="100%" border="0" rules="none" frame="void"
|
||||
cellspacing="0" cellpadding="0">
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p style="margin-top: 1em"><b>-I</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p style="margin-top: 1em">Inetd mode. Standalone service
|
||||
only.</p> </td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p><b>-d</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-d</b></p></td>
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Daemonise. Detach service from console and run in the
|
||||
background.</p> </td></tr>
|
||||
<p style="margin-top: 1em">Daemonize. Detach service from
|
||||
console and run in the background.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p><b>-t</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-t</b></p></td>
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Be silenT. Do not log start/stop/accept error
|
||||
records.</p> </td></tr>
|
||||
<p style="margin-top: 1em">Be silenT. Do not log
|
||||
start/stop/accept error records.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p><b>-u</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-u</b></p></td>
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Never look for username authentication.</p></td></tr>
|
||||
<p style="margin-top: 1em">Never look for username
|
||||
authentication.</p> </td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p><b>-e</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-e</b></p></td>
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>External address. IP address of interface proxy should
|
||||
initiate connections from. By default system will deside
|
||||
which address to use in accordance with routing table.</p></td></tr>
|
||||
<p style="margin-top: 1em">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.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p><b>-i</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-i</b></p></td>
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Internal address. IP address proxy accepts connections
|
||||
to. By default connection to any interface is accepted.
|
||||
It´s usually unsafe.</p></td></tr>
|
||||
<p style="margin-top: 1em">Internal address. IP address the
|
||||
proxy accepts connections to. By default, connections to any
|
||||
interface are accepted. It´s usually unsafe.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p><b>-h</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-h</b></p></td>
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Default destination. It’s used if targed address
|
||||
is not specified by user.</p></td></tr>
|
||||
<p style="margin-top: 1em">Default destination. It’s
|
||||
used if the target address is not specified by the user.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p><b>-p</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-p</b></p></td>
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Port. Port proxy listens for incoming connections.
|
||||
Default is 21.</p></td></tr>
|
||||
<p style="margin-top: 1em">Port. Port proxy listens for
|
||||
incoming connections. Default is 21.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p><b>-l</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-l</b></p></td>
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Log. By default logging is to stdout. If <i>logfile</i>
|
||||
is specified logging is to file. Under Unix, if
|
||||
´<i>@</i>´ preceeds <i>logfile</i>, syslog is
|
||||
used for logging.</p></td></tr>
|
||||
<p style="margin-top: 1em">Log. By default logging is to
|
||||
stdout. If <i>logfile</i> is specified logging is to file.
|
||||
Under Unix, if ´<i>@</i>´ precedes
|
||||
<i>logfile</i>, syslog is used for logging.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p><b>-S</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-S</b></p></td>
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Increase or decrease stack size. You may want to try
|
||||
something like -S8192 if you experience 3proxy crashes.</p></td></tr>
|
||||
<p style="margin-top: 1em">Increase or decrease stack size.
|
||||
You may want to try something like -S8192 if you experience
|
||||
3proxy crashes.</p></td></tr>
|
||||
</table>
|
||||
|
||||
<h2>CLIENTS
|
||||
|
|
@ -184,25 +187,26 @@ something like -S8192 if you experience 3proxy crashes.</p></td></tr>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">You can use any
|
||||
FTP client, regardless of FTP proxy support. For client with
|
||||
FTP proxy support configure <i>internal_ip</i> and
|
||||
<i>port</i> in FTP proxy parameters. For clients without FTP
|
||||
proxy support use <i>internal_ip</i> and <i>port</i> as FTP
|
||||
server. Address of real FTP server must be configured as a
|
||||
part of FTP username. Format for username is
|
||||
<i>username</i><b>@</b><i>server</i>, where <i>server</i> is
|
||||
address of FTP server and <i>username</i> is user´s
|
||||
login on this FTP server. Login itself may contain
|
||||
´@´ sign. Only cleartext authentication is
|
||||
currently supported.</p>
|
||||
<p style="margin-left:6%; margin-top: 1em">You can use any
|
||||
FTP client, regardless of FTP proxy support. For a client
|
||||
with FTP proxy support, configure <i>internal_ip</i> and
|
||||
<i>port</i> in the FTP proxy parameters. For clients without
|
||||
FTP proxy support, use <i>internal_ip</i> and <i>port</i> as
|
||||
the FTP server. The address of the real FTP server must be
|
||||
configured as a part of the FTP username. The format for the
|
||||
username is <i>username</i><b>@</b><i>server</i>, where
|
||||
<i>server</i> is the address of the FTP server and
|
||||
<i>username</i> is the user´s login on this FTP
|
||||
server. The login itself may contain an ´@´
|
||||
sign. Only cleartext authentication is currently
|
||||
supported.</p>
|
||||
|
||||
<h2>BUGS
|
||||
<a name="BUGS"></a>
|
||||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">Report all bugs
|
||||
<p style="margin-left:6%; margin-top: 1em">Report all bugs
|
||||
to <b>3proxy@3proxy.org</b></p>
|
||||
|
||||
<h2>SEE ALSO
|
||||
|
|
@ -210,7 +214,7 @@ to <b>3proxy@3proxy.org</b></p>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">3proxy(8),
|
||||
<p style="margin-left:6%; margin-top: 1em">3proxy(8),
|
||||
proxy(8), pop3p(8), socks(8), tcppm(8), udppm(8),
|
||||
syslogd(8), <br>
|
||||
https://3proxy.org/</p>
|
||||
|
|
@ -220,7 +224,7 @@ https://3proxy.org/</p>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">3proxy is
|
||||
<p style="margin-left:6%; margin-top: 1em">3proxy is
|
||||
designed by Vladimir 3APA3A Dubrovin
|
||||
(<i>3proxy@3proxy.org</i>)</p>
|
||||
<hr>
|
||||
|
|
|
|||
160
pop3p.md
160
pop3p.md
|
|
@ -1,4 +1,4 @@
|
|||
<!-- Creator : groff version 1.22.4 -->
|
||||
<!-- Creator : groff version 1.24.1 -->
|
||||
<html>
|
||||
<head>
|
||||
|
||||
|
|
@ -24,7 +24,7 @@
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>pop3p</b> -
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>pop3p</b> -
|
||||
POP3 proxy gateway service</p>
|
||||
|
||||
<h2>SYNOPSIS
|
||||
|
|
@ -32,7 +32,7 @@ POP3 proxy gateway service</p>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>pop3p</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>pop3p</b>
|
||||
[<b>-d</b>] [<b>-l</b>[[<i>@</i>]<i>logfile</i>]]
|
||||
[<b>-p</b><i>port</i>] [<b>-i</b><i>internal_ip</i>]
|
||||
[<b>-e</b><i>external_ip</i>]
|
||||
|
|
@ -43,7 +43,7 @@ POP3 proxy gateway service</p>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>pop3p</b> is
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>pop3p</b> is
|
||||
POP3 gateway service to allow internal users to access
|
||||
external POP3 servers.</p>
|
||||
|
||||
|
|
@ -55,128 +55,131 @@ external POP3 servers.</p>
|
|||
<table width="100%" border="0" rules="none" frame="void"
|
||||
cellspacing="0" cellpadding="0">
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p style="margin-top: 1em"><b>-I</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p style="margin-top: 1em">Inetd mode. Standalone service
|
||||
only.</p> </td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p><b>-d</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-d</b></p></td>
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Daemonise. Detach service from console and run in the
|
||||
background.</p> </td></tr>
|
||||
<p style="margin-top: 1em">Daemonize. Detach service from
|
||||
console and run in the background.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p><b>-t</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-t</b></p></td>
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Be silenT. Do not log start/stop/accept error
|
||||
records.</p> </td></tr>
|
||||
<p style="margin-top: 1em">Be silenT. Do not log
|
||||
start/stop/accept error records.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p><b>-u</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-u</b></p></td>
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Never look for username authentication.</p></td></tr>
|
||||
<p style="margin-top: 1em">Never look for username
|
||||
authentication.</p> </td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p><b>-e</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-e</b></p></td>
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>External address. IP address of interface proxy should
|
||||
initiate connections from. By default system will deside
|
||||
which address to use in accordance with routing table.</p></td></tr>
|
||||
<p style="margin-top: 1em">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.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p><b>-i</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-i</b></p></td>
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Internal address. IP address proxy accepts connections
|
||||
to. By default connection to any interface is accepted.
|
||||
It´s usually unsafe.</p></td></tr>
|
||||
<p style="margin-top: 1em">Internal address. IP address the
|
||||
proxy accepts connections to. By default, connections to any
|
||||
interface are accepted. It´s usually unsafe.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p><b>-p</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-p</b></p></td>
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Port. Port proxy listens for incoming connections.
|
||||
Default is 110.</p></td></tr>
|
||||
<p style="margin-top: 1em">Port. Port proxy listens for
|
||||
incoming connections. Default is 110.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p><b>-h</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-h</b></p></td>
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Default destination. It’s used if targed address
|
||||
is not specified by user.</p></td></tr>
|
||||
<p style="margin-top: 1em">Default destination. It’s
|
||||
used if the target address is not specified by the user.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p><b>-l</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-l</b></p></td>
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Log. By default logging is to stdout. If <i>logfile</i>
|
||||
is specified logging is to file. Under Unix, if
|
||||
´<i>@</i>´ preceeds <i>logfile</i>, syslog is
|
||||
used for logging.</p></td></tr>
|
||||
<p style="margin-top: 1em">Log. By default logging is to
|
||||
stdout. If <i>logfile</i> is specified logging is to file.
|
||||
Under Unix, if ´<i>@</i>´ precedes
|
||||
<i>logfile</i>, syslog is used for logging.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p><b>-S</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-S</b></p></td>
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Increase or decrease stack size. You may want to try
|
||||
something like -S8192 if you experience 3proxy crashes.</p></td></tr>
|
||||
<p style="margin-top: 1em">Increase or decrease stack size.
|
||||
You may want to try something like -S8192 if you experience
|
||||
3proxy crashes.</p></td></tr>
|
||||
</table>
|
||||
|
||||
<h2>CLIENTS
|
||||
|
|
@ -184,25 +187,26 @@ something like -S8192 if you experience 3proxy crashes.</p></td></tr>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">You can use any
|
||||
MUA (Mail User Agent) with POP3 support. Set client to use
|
||||
<i>internal_ip</i> and <i>port</i> as a POP3 server. Address
|
||||
of real POP3 server must be configured as a part of POP3
|
||||
username. Format for username is
|
||||
<p style="margin-left:6%; margin-top: 1em">You can use any
|
||||
MUA (Mail User Agent) with POP3 support. Set the client to
|
||||
use <i>internal_ip</i> and <i>port</i> as a POP3 server. The
|
||||
address of the real POP3 server must be configured as a part
|
||||
of the POP3 username. The format for the username is
|
||||
<i>username</i><b>@</b><i>server</i>, where <i>server</i> is
|
||||
address of POP3 server and <i>username</i> is user´s
|
||||
login on this POP3 server. Login itself may contain
|
||||
´@´ sign. Only cleartext authentication is
|
||||
supported, because challenge-response authentication (APOP,
|
||||
CRAM-MD5, etc) requires challenge from server before we know
|
||||
which server to connect.</p>
|
||||
the address of the POP3 server and <i>username</i> is the
|
||||
user´s login on this POP3 server. The login itself may
|
||||
contain an ´@´ sign. Only cleartext
|
||||
authentication is supported, because challenge-response
|
||||
authentication (APOP, CRAM-MD5, etc.) requires a challenge
|
||||
from the server before we know which server to connect
|
||||
to.</p>
|
||||
|
||||
<h2>BUGS
|
||||
<a name="BUGS"></a>
|
||||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">Report all bugs
|
||||
<p style="margin-left:6%; margin-top: 1em">Report all bugs
|
||||
to <b>3proxy@3proxy.org</b></p>
|
||||
|
||||
<h2>SEE ALSO
|
||||
|
|
@ -210,7 +214,7 @@ to <b>3proxy@3proxy.org</b></p>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">3proxy(8),
|
||||
<p style="margin-left:6%; margin-top: 1em">3proxy(8),
|
||||
ftppr(8), proxy(8), socks(8), tcppm(8), udppm(8),
|
||||
syslogd(8), <br>
|
||||
https://3proxy.org/</p>
|
||||
|
|
@ -220,7 +224,7 @@ https://3proxy.org/</p>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">3proxy is
|
||||
<p style="margin-left:6%; margin-top: 1em">3proxy is
|
||||
designed by Vladimir 3APA3A Dubrovin
|
||||
(<i>3proxy@3proxy.org</i>)</p>
|
||||
<hr>
|
||||
|
|
|
|||
159
proxy.md
159
proxy.md
|
|
@ -1,4 +1,4 @@
|
|||
<!-- Creator : groff version 1.22.4 -->
|
||||
<!-- Creator : groff version 1.24.1 -->
|
||||
<html>
|
||||
<head>
|
||||
|
||||
|
|
@ -24,7 +24,7 @@
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>proxy</b> -
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>proxy</b> -
|
||||
HTTP proxy gateway service</p>
|
||||
|
||||
<h2>SYNOPSIS
|
||||
|
|
@ -32,7 +32,7 @@ HTTP proxy gateway service</p>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>proxy</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>proxy</b>
|
||||
[<b>-d</b>][<b>-a</b>] [<b>-l</b>[[<i>@</i>]<i>logfile</i>]]
|
||||
[<b>-p</b><i>port</i>] [<b>-i</b><i>internal_ip</i>]
|
||||
[<b>-e</b><i>external_ip</i>]</p>
|
||||
|
|
@ -42,7 +42,7 @@ HTTP proxy gateway service</p>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>proxy</b> is
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>proxy</b> is
|
||||
HTTP gateway service with HTTPS and FTP over HTTPS
|
||||
support.</p>
|
||||
|
||||
|
|
@ -54,138 +54,143 @@ support.</p>
|
|||
<table width="100%" border="0" rules="none" frame="void"
|
||||
cellspacing="0" cellpadding="0">
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="4%">
|
||||
|
||||
|
||||
<p style="margin-top: 1em"><b>-I</b></p></td>
|
||||
<td width="7%"></td>
|
||||
<td width="78%">
|
||||
<td width="5%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p style="margin-top: 1em">Inetd mode. Standalone service
|
||||
only.</p> </td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="4%">
|
||||
|
||||
|
||||
<p><b>-d</b></p></td>
|
||||
<td width="7%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-d</b></p></td>
|
||||
<td width="5%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Daemonise. Detach service from console and run in the
|
||||
background.</p> </td></tr>
|
||||
<p style="margin-top: 1em">Daemonize. Detach service from
|
||||
console and run in the background.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="4%">
|
||||
|
||||
|
||||
<p><b>-t</b></p></td>
|
||||
<td width="7%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-t</b></p></td>
|
||||
<td width="5%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Be silenT. Do not log start/stop/accept error
|
||||
records.</p> </td></tr>
|
||||
<p style="margin-top: 1em">Be silenT. Do not log
|
||||
start/stop/accept error records.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="4%">
|
||||
|
||||
|
||||
<p><b>-u</b></p></td>
|
||||
<td width="7%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-u</b></p></td>
|
||||
<td width="5%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Never ask for username authentication</p></td></tr>
|
||||
<p style="margin-top: 1em">Never ask for username
|
||||
authentication</p> </td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="4%">
|
||||
|
||||
|
||||
<p><b>-e</b></p></td>
|
||||
<td width="7%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-e</b></p></td>
|
||||
<td width="5%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>External address. IP address of interface proxy should
|
||||
initiate connections from. By default system will deside
|
||||
which address to use in accordance with routing table.</p></td></tr>
|
||||
<p style="margin-top: 1em">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.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="4%">
|
||||
|
||||
|
||||
<p><b>-i</b></p></td>
|
||||
<td width="7%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-i</b></p></td>
|
||||
<td width="5%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Internal address. IP address proxy accepts connections
|
||||
to. By default connection to any interface is accepted.
|
||||
It´s usually unsafe.</p></td></tr>
|
||||
<p style="margin-top: 1em">Internal address. IP address the
|
||||
proxy accepts connections to. By default, connections to any
|
||||
interface are accepted. It´s usually unsafe.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="4%">
|
||||
|
||||
|
||||
<p><b>-a</b></p></td>
|
||||
<td width="7%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-a</b></p></td>
|
||||
<td width="5%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Anonymous. Hide information about client.</p></td></tr>
|
||||
<p style="margin-top: 1em">Anonymous. Hide information
|
||||
about client.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="4%">
|
||||
|
||||
|
||||
<p><b>-a1</b></p></td>
|
||||
<td width="7%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-a1</b></p></td>
|
||||
<td width="5%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Anonymous. Show fake information about client.</p></td></tr>
|
||||
<p style="margin-top: 1em">Anonymous. Show fake information
|
||||
about client.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="4%">
|
||||
|
||||
|
||||
<p><b>-p</b></p></td>
|
||||
<td width="7%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-p</b></p></td>
|
||||
<td width="5%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Port. Port proxy listens for incoming connections.
|
||||
Default is 3128.</p></td></tr>
|
||||
<p style="margin-top: 1em">Port. Port proxy listens for
|
||||
incoming connections. Default is 3128.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="4%">
|
||||
|
||||
|
||||
<p><b>-l</b></p></td>
|
||||
<td width="7%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-l</b></p></td>
|
||||
<td width="5%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Log. By default logging is to stdout. If <i>logfile</i>
|
||||
is specified logging is to file. Under Unix, if
|
||||
´<i>@</i>´ preceeds <i>logfile</i>, syslog is
|
||||
used for logging.</p></td></tr>
|
||||
<p style="margin-top: 1em">Log. By default logging is to
|
||||
stdout. If <i>logfile</i> is specified logging is to file.
|
||||
Under Unix, if ´<i>@</i>´ preceeds
|
||||
<i>logfile</i>, syslog is used for logging.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="4%">
|
||||
|
||||
|
||||
<p><b>-S</b></p></td>
|
||||
<td width="7%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-S</b></p></td>
|
||||
<td width="5%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Increase or decrease stack size. You may want to try
|
||||
something like -S8192 if you experience 3proxy crashes.</p></td></tr>
|
||||
<p style="margin-top: 1em">Increase or decrease stack size.
|
||||
You may want to try something like -S8192 if you experience
|
||||
3proxy crashes.</p></td></tr>
|
||||
</table>
|
||||
|
||||
<h2>CLIENTS
|
||||
|
|
@ -193,12 +198,12 @@ something like -S8192 if you experience 3proxy crashes.</p></td></tr>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">You should use
|
||||
client with HTTP proxy support or configure router to
|
||||
redirect HTTP traffic to proxy (transparent proxy).
|
||||
Configure client to connect to <i>internal_ip</i> and
|
||||
<i>port</i>. HTTPS support allows to use almost any TCP
|
||||
based protocol. If you need to limit clients, use
|
||||
<p style="margin-left:6%; margin-top: 1em">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 <i>internal_ip</i> and
|
||||
<i>port</i>. HTTPS support allows you to use almost any
|
||||
TCP-based protocol. If you need to limit clients, use
|
||||
<b>3proxy</b>(8) instead.</p>
|
||||
|
||||
<h2>BUGS
|
||||
|
|
@ -206,7 +211,7 @@ based protocol. If you need to limit clients, use
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">Report all bugs
|
||||
<p style="margin-left:6%; margin-top: 1em">Report all bugs
|
||||
to <b>3proxy@3proxy.org</b></p>
|
||||
|
||||
<h2>SEE ALSO
|
||||
|
|
@ -214,7 +219,7 @@ to <b>3proxy@3proxy.org</b></p>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">3proxy(8),
|
||||
<p style="margin-left:6%; margin-top: 1em">3proxy(8),
|
||||
ftppr(8), socks(8), pop3p(8), tcppm(8), udppm(8),
|
||||
syslogd(8), <br>
|
||||
https://3proxy.org/</p>
|
||||
|
|
@ -224,7 +229,7 @@ https://3proxy.org/</p>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">3proxy is
|
||||
<p style="margin-left:6%; margin-top: 1em">3proxy is
|
||||
designed by Vladimir 3APA3A Dubrovin
|
||||
(<i>3proxy@3proxy.org</i>)</p>
|
||||
<hr>
|
||||
|
|
|
|||
160
smtpp.md
160
smtpp.md
|
|
@ -1,4 +1,4 @@
|
|||
<!-- Creator : groff version 1.22.4 -->
|
||||
<!-- Creator : groff version 1.24.1 -->
|
||||
<html>
|
||||
<head>
|
||||
|
||||
|
|
@ -24,7 +24,7 @@
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>smtpp</b> -
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>smtpp</b> -
|
||||
SMTP proxy gateway service</p>
|
||||
|
||||
<h2>SYNOPSIS
|
||||
|
|
@ -32,7 +32,7 @@ SMTP proxy gateway service</p>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>smtpp</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>smtpp</b>
|
||||
[<b>-d</b>] [<b>-l</b>[[<i>@</i>]<i>logfile</i>]]
|
||||
[<b>-p</b><i>port</i>] [<b>-i</b><i>internal_ip</i>]
|
||||
[<b>-e</b><i>external_ip</i>]
|
||||
|
|
@ -43,7 +43,7 @@ SMTP proxy gateway service</p>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>smtpp</b> is
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>smtpp</b> is
|
||||
SMTP gateway service to allow internal users to access
|
||||
external SMTP servers.</p>
|
||||
|
||||
|
|
@ -55,128 +55,131 @@ external SMTP servers.</p>
|
|||
<table width="100%" border="0" rules="none" frame="void"
|
||||
cellspacing="0" cellpadding="0">
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p style="margin-top: 1em"><b>-I</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p style="margin-top: 1em">Inetd mode. Standalone service
|
||||
only.</p> </td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p><b>-d</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-d</b></p></td>
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Daemonise. Detach service from console and run in the
|
||||
background.</p> </td></tr>
|
||||
<p style="margin-top: 1em">Daemonize. Detach service from
|
||||
console and run in the background.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p><b>-t</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-t</b></p></td>
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Be silenT. Do not log start/stop/accept error
|
||||
records.</p> </td></tr>
|
||||
<p style="margin-top: 1em">Be silenT. Do not log
|
||||
start/stop/accept error records.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p><b>-u</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-u</b></p></td>
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Never look for username authentication.</p></td></tr>
|
||||
<p style="margin-top: 1em">Never look for username
|
||||
authentication.</p> </td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p><b>-e</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-e</b></p></td>
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>External address. IP address of interface proxy should
|
||||
initiate connections from. By default system will deside
|
||||
which address to use in accordance with routing table.</p></td></tr>
|
||||
<p style="margin-top: 1em">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.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p><b>-i</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-i</b></p></td>
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Internal address. IP address proxy accepts connections
|
||||
to. By default connection to any interface is accepted.
|
||||
It´s usually unsafe.</p></td></tr>
|
||||
<p style="margin-top: 1em">Internal address. IP address the
|
||||
proxy accepts connections to. By default, connections to any
|
||||
interface are accepted. It´s usually unsafe.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p><b>-p</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-p</b></p></td>
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Port. Port proxy listens for incoming connections.
|
||||
Default is 25.</p></td></tr>
|
||||
<p style="margin-top: 1em">Port. Port proxy listens for
|
||||
incoming connections. Default is 25.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p><b>-h</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-h</b></p></td>
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Default destination. It’s used if targed address
|
||||
is not specified by user.</p></td></tr>
|
||||
<p style="margin-top: 1em">Default destination. It’s
|
||||
used if the target address is not specified by the user.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p><b>-l</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-l</b></p></td>
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Log. By default logging is to stdout. If <i>logfile</i>
|
||||
is specified logging is to file. Under Unix, if
|
||||
´<i>@</i>´ preceeds <i>logfile</i>, syslog is
|
||||
used for logging.</p></td></tr>
|
||||
<p style="margin-top: 1em">Log. By default logging is to
|
||||
stdout. If <i>logfile</i> is specified logging is to file.
|
||||
Under Unix, if ´<i>@</i>´ precedes
|
||||
<i>logfile</i>, syslog is used for logging.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p><b>-S</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-S</b></p></td>
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Increase or decrease stack size. You may want to try
|
||||
something like -S8192 if you experience 3proxy crashes.</p></td></tr>
|
||||
<p style="margin-top: 1em">Increase or decrease stack size.
|
||||
You may want to try something like -S8192 if you experience
|
||||
3proxy crashes.</p></td></tr>
|
||||
</table>
|
||||
|
||||
<h2>CLIENTS
|
||||
|
|
@ -184,25 +187,26 @@ something like -S8192 if you experience 3proxy crashes.</p></td></tr>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">You can use any
|
||||
<p style="margin-left:6%; margin-top: 1em">You can use any
|
||||
MUA (Mail User Agent) with SMTP authentication support. Set
|
||||
client to use <i>internal_ip</i> and <i>port</i> as a SMTP
|
||||
server. Address of real SMTP server must be configured as a
|
||||
part of SMTP username. Format for username is
|
||||
<i>username</i><b>@</b><i>server</i>, where <i>server</i> is
|
||||
address of SMTP server and <i>username</i> is user´s
|
||||
login on this SMTP server. Login itself may contain
|
||||
´@´ sign. Only cleartext authentication is
|
||||
supported, because challenge-response authentication
|
||||
(CRAM-MD5, SPA, etc) requires challenge from server before
|
||||
we know which server to connect.</p>
|
||||
the client to use <i>internal_ip</i> and <i>port</i> as an
|
||||
SMTP server. The address of the real SMTP server must be
|
||||
configured as a part of the SMTP username. The format for
|
||||
the username is <i>username</i><b>@</b><i>server</i>, where
|
||||
<i>server</i> is the address of the SMTP server and
|
||||
<i>username</i> is the user´s login on this SMTP
|
||||
server. The login itself may contain an ´@´
|
||||
sign. Only cleartext authentication is supported, because
|
||||
challenge-response authentication (CRAM-MD5, SPA, etc.)
|
||||
requires a challenge from the server before we know which
|
||||
server to connect to.</p>
|
||||
|
||||
<h2>BUGS
|
||||
<a name="BUGS"></a>
|
||||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">Report all bugs
|
||||
<p style="margin-left:6%; margin-top: 1em">Report all bugs
|
||||
to <b>3proxy@3proxy.org</b></p>
|
||||
|
||||
<h2>SEE ALSO
|
||||
|
|
@ -210,7 +214,7 @@ to <b>3proxy@3proxy.org</b></p>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">3proxy(8),
|
||||
<p style="margin-left:6%; margin-top: 1em">3proxy(8),
|
||||
ftppr(8), proxy(8), socks(8), tcppm(8), udppm(8),
|
||||
syslogd(8), <br>
|
||||
https://3proxy.org/</p>
|
||||
|
|
@ -220,7 +224,7 @@ https://3proxy.org/</p>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">3proxy is
|
||||
<p style="margin-left:6%; margin-top: 1em">3proxy is
|
||||
designed by Vladimir 3APA3A Dubrovin
|
||||
(<i>3proxy@3proxy.org</i>)</p>
|
||||
<hr>
|
||||
|
|
|
|||
205
socks.md
205
socks.md
|
|
@ -1,4 +1,4 @@
|
|||
<!-- Creator : groff version 1.22.4 -->
|
||||
<!-- Creator : groff version 1.24.1 -->
|
||||
<html>
|
||||
<head>
|
||||
|
||||
|
|
@ -24,7 +24,7 @@
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>tlspr</b> -
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>tlspr</b> -
|
||||
SNI proxy gateway service</p>
|
||||
|
||||
<h2>SYNOPSIS
|
||||
|
|
@ -32,7 +32,7 @@ SNI proxy gateway service</p>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>tlspr</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>tlspr</b>
|
||||
[<b>-d</b>][<b>-a</b>] [<b>-l</b>[[<i>@</i>]<i>logfile</i>]]
|
||||
[<b>-p</b><i>listening_port</i>]
|
||||
[<b>-P</b><i>destination_port</i>]
|
||||
|
|
@ -45,10 +45,11 @@ SNI proxy gateway service</p>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>proxy</b> is
|
||||
SNI gateway service (destination host is taken from TLS
|
||||
handshake). Destination port must be specified via -P option
|
||||
(or it may be detected with Transparent plugin).</p>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>tlspr</b> 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
|
||||
plugin).</p>
|
||||
|
||||
<h2>OPTIONS
|
||||
<a name="OPTIONS"></a>
|
||||
|
|
@ -58,169 +59,175 @@ handshake). Destination port must be specified via -P option
|
|||
<table width="100%" border="0" rules="none" frame="void"
|
||||
cellspacing="0" cellpadding="0">
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="4%">
|
||||
|
||||
|
||||
<p style="margin-top: 1em"><b>-I</b></p></td>
|
||||
<td width="7%"></td>
|
||||
<td width="78%">
|
||||
<td width="5%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p style="margin-top: 1em">Inetd mode. Standalone service
|
||||
only.</p> </td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="4%">
|
||||
|
||||
|
||||
<p><b>-d</b></p></td>
|
||||
<td width="7%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-d</b></p></td>
|
||||
<td width="5%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Daemonise. Detach service from console and run in the
|
||||
background.</p> </td></tr>
|
||||
<p style="margin-top: 1em">Daemonize. Detach service from
|
||||
console and run in the background.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="4%">
|
||||
|
||||
|
||||
<p><b>-t</b></p></td>
|
||||
<td width="7%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-t</b></p></td>
|
||||
<td width="5%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Be silenT. Do not log start/stop/accept error
|
||||
records.</p> </td></tr>
|
||||
<p style="margin-top: 1em">Be silenT. Do not log
|
||||
start/stop/accept error records.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="4%">
|
||||
|
||||
|
||||
<p><b>-u</b></p></td>
|
||||
<td width="7%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-u</b></p></td>
|
||||
<td width="5%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Never ask for username authentication</p></td></tr>
|
||||
<p style="margin-top: 1em">Never ask for username
|
||||
authentication</p> </td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="4%">
|
||||
|
||||
|
||||
<p><b>-e</b></p></td>
|
||||
<td width="7%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-e</b></p></td>
|
||||
<td width="5%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>External address. IP address of interface proxy should
|
||||
initiate connections from. By default system will deside
|
||||
which address to use in accordance with routing table.</p></td></tr>
|
||||
<p style="margin-top: 1em">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.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="4%">
|
||||
|
||||
|
||||
<p><b>-i</b></p></td>
|
||||
<td width="7%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-i</b></p></td>
|
||||
<td width="5%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Internal address. IP address proxy accepts connections
|
||||
to. By default connection to any interface is accepted.
|
||||
It´s usually unsafe.</p></td></tr>
|
||||
<p style="margin-top: 1em">Internal address. IP address the
|
||||
proxy accepts connections to. By default, connections to any
|
||||
interface are accepted. It´s usually unsafe.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="4%">
|
||||
|
||||
|
||||
<p><b>-a</b></p></td>
|
||||
<td width="7%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-a</b></p></td>
|
||||
<td width="5%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Anonymous. Hide information about client.</p></td></tr>
|
||||
<p style="margin-top: 1em">Anonymous. Hide information
|
||||
about client.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="4%">
|
||||
|
||||
|
||||
<p><b>-a1</b></p></td>
|
||||
<td width="7%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-a1</b></p></td>
|
||||
<td width="5%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Anonymous. Show fake information about client.</p></td></tr>
|
||||
<p style="margin-top: 1em">Anonymous. Show fake information
|
||||
about client.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="4%">
|
||||
|
||||
|
||||
<p><b>-p</b></p></td>
|
||||
<td width="7%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-p</b></p></td>
|
||||
<td width="5%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>listening_port. Port proxy listens for incoming
|
||||
connections. Default is 1443.</p></td></tr>
|
||||
<p style="margin-top: 1em">listening_port. Port proxy
|
||||
listens for incoming connections. Default is 1443.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="4%">
|
||||
|
||||
|
||||
<p><b>-P</b></p></td>
|
||||
<td width="7%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-P</b></p></td>
|
||||
<td width="5%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>destination_port. Port to establish outgoing
|
||||
connections. One is required unless Transparent plugin is
|
||||
not used because TLS handshake does not contain port
|
||||
information. Default is 443.</p></td></tr>
|
||||
<p style="margin-top: 1em">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.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="4%">
|
||||
|
||||
|
||||
<p><b>-c</b></p></td>
|
||||
<td width="7%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-c</b></p></td>
|
||||
<td width="5%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>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 server send certificate (not compatible with TLS
|
||||
1.3), 4 - require mutual TLS, check server send certificate
|
||||
request and client sends certificate (not compatible with
|
||||
TLS 1.3)</p></td></tr>
|
||||
<p style="margin-top: 1em">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)</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="4%">
|
||||
|
||||
|
||||
<p><b>-l</b></p></td>
|
||||
<td width="7%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-l</b></p></td>
|
||||
<td width="5%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Log. By default logging is to stdout. If <i>logfile</i>
|
||||
is specified logging is to file. Under Unix, if
|
||||
´<i>@</i>´ preceeds <i>logfile</i>, syslog is
|
||||
used for logging.</p></td></tr>
|
||||
<p style="margin-top: 1em">Log. By default logging is to
|
||||
stdout. If <i>logfile</i> is specified logging is to file.
|
||||
Under Unix, if ´<i>@</i>´ precedes
|
||||
<i>logfile</i>, syslog is used for logging.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="4%">
|
||||
|
||||
|
||||
<p><b>-S</b></p></td>
|
||||
<td width="7%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-S</b></p></td>
|
||||
<td width="5%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Increase or decrease stack size. You may want to try
|
||||
something like -S8192 if you experience 3proxy crashes.</p></td></tr>
|
||||
<p style="margin-top: 1em">Increase or decrease stack size.
|
||||
You may want to try something like -S8192 if you experience
|
||||
3proxy crashes.</p></td></tr>
|
||||
</table>
|
||||
|
||||
<h2>CLIENTS
|
||||
|
|
@ -228,20 +235,18 @@ something like -S8192 if you experience 3proxy crashes.</p></td></tr>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">You should use
|
||||
client with HTTP proxy support or configure router to
|
||||
redirect HTTP traffic to proxy (transparent proxy).
|
||||
Configure client to connect to <i>internal_ip</i> and
|
||||
<i>port</i>. HTTPS support allows to use almost any TCP
|
||||
based protocol. If you need to limit clients, use
|
||||
<b>3proxy</b>(8) instead.</p>
|
||||
<p style="margin-left:6%; margin-top: 1em">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 <i>internal_ip</i> and <i>port</i>. If
|
||||
you need to limit clients, use <b>3proxy</b>(8) instead.</p>
|
||||
|
||||
<h2>BUGS
|
||||
<a name="BUGS"></a>
|
||||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">Report all bugs
|
||||
<p style="margin-left:6%; margin-top: 1em">Report all bugs
|
||||
to <b>3proxy@3proxy.org</b></p>
|
||||
|
||||
<h2>SEE ALSO
|
||||
|
|
@ -249,7 +254,7 @@ to <b>3proxy@3proxy.org</b></p>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">3proxy(8),
|
||||
<p style="margin-left:6%; margin-top: 1em">3proxy(8),
|
||||
ftppr(8), proxy(8), socks(8), pop3p(8), smtpp(8), tcppm(8),
|
||||
udppm(8), syslogd(8), <br>
|
||||
https://3proxy.org/</p>
|
||||
|
|
@ -259,7 +264,7 @@ https://3proxy.org/</p>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">3proxy is
|
||||
<p style="margin-left:6%; margin-top: 1em">3proxy is
|
||||
designed by Vladimir 3APA3A Dubrovin
|
||||
(<i>3proxy@3proxy.org</i>)</p>
|
||||
<hr>
|
||||
|
|
|
|||
122
tcppm.md
122
tcppm.md
|
|
@ -1,4 +1,4 @@
|
|||
<!-- Creator : groff version 1.22.4 -->
|
||||
<!-- Creator : groff version 1.24.1 -->
|
||||
<html>
|
||||
<head>
|
||||
|
||||
|
|
@ -25,7 +25,7 @@
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>tcppm</b> -
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>tcppm</b> -
|
||||
TCP port mapper</p>
|
||||
|
||||
<h2>SYNOPSIS
|
||||
|
|
@ -33,7 +33,7 @@ TCP port mapper</p>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>tcppm</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>tcppm</b>
|
||||
[<b>-d</b>] [<b>-l</b>[[<i>@</i>]<i>logfile</i>]]
|
||||
[<b>-i</b><i>internal_ip</i>] [<b>-e</b><i>external_ip</i>]
|
||||
<i>local_port remote_host remote_port</i></p>
|
||||
|
|
@ -44,7 +44,7 @@ TCP port mapper</p>
|
|||
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><i><b>tcppm</b></i>
|
||||
<p style="margin-left:6%; margin-top: 1em"><i><b>tcppm</b></i>
|
||||
forwards connections from local to remote TCP port</p>
|
||||
|
||||
<h2>OPTIONS
|
||||
|
|
@ -55,93 +55,95 @@ forwards connections from local to remote TCP port</p>
|
|||
<table width="100%" border="0" rules="none" frame="void"
|
||||
cellspacing="0" cellpadding="0">
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p style="margin-top: 1em"><b>-I</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p style="margin-top: 1em">Inetd mode. Standalone service
|
||||
only.</p> </td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p><b>-d</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-d</b></p></td>
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Daemonise. Detach service from console and run in the
|
||||
background.</p> </td></tr>
|
||||
<p style="margin-top: 1em">Daemonize. Detach service from
|
||||
console and run in the background.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p><b>-t</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-t</b></p></td>
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Be silenT. Do not log start/stop/accept error
|
||||
records.</p> </td></tr>
|
||||
<p style="margin-top: 1em">Be silenT. Do not log
|
||||
start/stop/accept error records.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p><b>-e</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-e</b></p></td>
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>External address. IP address of interface proxy should
|
||||
initiate connections from. By default system will deside
|
||||
which address to use in accordance with routing table.</p></td></tr>
|
||||
<p style="margin-top: 1em">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.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p><b>-i</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-i</b></p></td>
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Internal address. IP address proxy accepts connections
|
||||
to. By default connection to any interface is accepted.
|
||||
It´s usually unsafe.</p></td></tr>
|
||||
<p style="margin-top: 1em">Internal address. IP address the
|
||||
proxy accepts connections to. By default, connections to any
|
||||
interface are accepted. It´s usually unsafe.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p><b>-l</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-l</b></p></td>
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Log. By default logging is to stdout. If <i>logfile</i>
|
||||
is specified logging is to file. Under Unix, if
|
||||
´<i>@</i>´ preceeds <i>logfile</i>, syslog is
|
||||
used for logging.</p></td></tr>
|
||||
<p style="margin-top: 1em">Log. By default logging is to
|
||||
stdout. If <i>logfile</i> is specified logging is to file.
|
||||
Under Unix, if ´<i>@</i>´ precedes
|
||||
<i>logfile</i>, syslog is used for logging.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p><b>-S</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-S</b></p></td>
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Increase or decrease stack size. You may want to try
|
||||
something like -S8192 if you experience 3proxy crashes.</p></td></tr>
|
||||
<p style="margin-top: 1em">Increase or decrease stack size.
|
||||
You may want to try something like -S8192 if you experience
|
||||
3proxy crashes.</p></td></tr>
|
||||
</table>
|
||||
|
||||
<h2>ARGUMENTS
|
||||
|
|
@ -150,19 +152,19 @@ something like -S8192 if you experience 3proxy crashes.</p></td></tr>
|
|||
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><i>local_port</i></p>
|
||||
<p style="margin-left:6%; margin-top: 1em"><i>local_port</i></p>
|
||||
|
||||
<p style="margin-left:22%;">- port tcppm accepts
|
||||
connection</p>
|
||||
<p style="margin-left:15%;">- port tcppm accepts
|
||||
connections on</p>
|
||||
|
||||
<p style="margin-left:11%;"><i>remote_host</i></p>
|
||||
<p style="margin-left:6%;"><i>remote_host</i></p>
|
||||
|
||||
<p style="margin-left:22%;">- IP address of the host
|
||||
<p style="margin-left:15%;">- IP address of the host the
|
||||
connection is forwarded to</p>
|
||||
|
||||
<p style="margin-left:11%;"><i>remote_port</i></p>
|
||||
<p style="margin-left:6%;"><i>remote_port</i></p>
|
||||
|
||||
<p style="margin-left:22%;">- remote port connection is
|
||||
<p style="margin-left:15%;">- remote port the connection is
|
||||
forwarded to</p>
|
||||
|
||||
<h2>CLIENTS
|
||||
|
|
@ -170,10 +172,10 @@ forwarded to</p>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">Any TCP based
|
||||
<p style="margin-left:6%; margin-top: 1em">Any TCP-based
|
||||
application can be used as a client. Use <i>internal_ip</i>
|
||||
and <i>local_port</i> as a destination in client
|
||||
application. Connection is forwarded to
|
||||
and <i>local_port</i> as the destination in the client
|
||||
application. The connection is forwarded to
|
||||
<i>remote_host</i>:<i>remote_port</i></p>
|
||||
|
||||
<h2>BUGS
|
||||
|
|
@ -181,7 +183,7 @@ application. Connection is forwarded to
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">Report all bugs
|
||||
<p style="margin-left:6%; margin-top: 1em">Report all bugs
|
||||
to <b>3proxy@3proxy.org</b></p>
|
||||
|
||||
<h2>SEE ALSO
|
||||
|
|
@ -189,7 +191,7 @@ to <b>3proxy@3proxy.org</b></p>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">3proxy(8),
|
||||
<p style="margin-left:6%; margin-top: 1em">3proxy(8),
|
||||
proxy(8), ftppr(8), socks(8), pop3p(8), udppm(8),
|
||||
syslogd(8), <br>
|
||||
https://3proxy.org/</p>
|
||||
|
|
@ -199,7 +201,7 @@ https://3proxy.org/</p>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">3proxy is
|
||||
<p style="margin-left:6%; margin-top: 1em">3proxy is
|
||||
designed by Vladimir 3APA3A Dubrovin
|
||||
(<i>3proxy@3proxy.org</i>)</p>
|
||||
<hr>
|
||||
|
|
|
|||
205
tlspr.md
205
tlspr.md
|
|
@ -1,4 +1,4 @@
|
|||
<!-- Creator : groff version 1.22.4 -->
|
||||
<!-- Creator : groff version 1.24.1 -->
|
||||
<html>
|
||||
<head>
|
||||
|
||||
|
|
@ -24,7 +24,7 @@
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>tlspr</b> -
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>tlspr</b> -
|
||||
SNI proxy gateway service</p>
|
||||
|
||||
<h2>SYNOPSIS
|
||||
|
|
@ -32,7 +32,7 @@ SNI proxy gateway service</p>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>tlspr</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>tlspr</b>
|
||||
[<b>-d</b>][<b>-a</b>] [<b>-l</b>[[<i>@</i>]<i>logfile</i>]]
|
||||
[<b>-p</b><i>listening_port</i>]
|
||||
[<b>-P</b><i>destination_port</i>]
|
||||
|
|
@ -45,10 +45,11 @@ SNI proxy gateway service</p>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>proxy</b> is
|
||||
SNI gateway service (destination host is taken from TLS
|
||||
handshake). Destination port must be specified via -P option
|
||||
(or it may be detected with Transparent plugin).</p>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>tlspr</b> 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
|
||||
plugin).</p>
|
||||
|
||||
<h2>OPTIONS
|
||||
<a name="OPTIONS"></a>
|
||||
|
|
@ -58,169 +59,175 @@ handshake). Destination port must be specified via -P option
|
|||
<table width="100%" border="0" rules="none" frame="void"
|
||||
cellspacing="0" cellpadding="0">
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="4%">
|
||||
|
||||
|
||||
<p style="margin-top: 1em"><b>-I</b></p></td>
|
||||
<td width="7%"></td>
|
||||
<td width="78%">
|
||||
<td width="5%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p style="margin-top: 1em">Inetd mode. Standalone service
|
||||
only.</p> </td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="4%">
|
||||
|
||||
|
||||
<p><b>-d</b></p></td>
|
||||
<td width="7%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-d</b></p></td>
|
||||
<td width="5%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Daemonise. Detach service from console and run in the
|
||||
background.</p> </td></tr>
|
||||
<p style="margin-top: 1em">Daemonize. Detach service from
|
||||
console and run in the background.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="4%">
|
||||
|
||||
|
||||
<p><b>-t</b></p></td>
|
||||
<td width="7%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-t</b></p></td>
|
||||
<td width="5%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Be silenT. Do not log start/stop/accept error
|
||||
records.</p> </td></tr>
|
||||
<p style="margin-top: 1em">Be silenT. Do not log
|
||||
start/stop/accept error records.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="4%">
|
||||
|
||||
|
||||
<p><b>-u</b></p></td>
|
||||
<td width="7%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-u</b></p></td>
|
||||
<td width="5%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Never ask for username authentication</p></td></tr>
|
||||
<p style="margin-top: 1em">Never ask for username
|
||||
authentication</p> </td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="4%">
|
||||
|
||||
|
||||
<p><b>-e</b></p></td>
|
||||
<td width="7%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-e</b></p></td>
|
||||
<td width="5%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>External address. IP address of interface proxy should
|
||||
initiate connections from. By default system will deside
|
||||
which address to use in accordance with routing table.</p></td></tr>
|
||||
<p style="margin-top: 1em">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.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="4%">
|
||||
|
||||
|
||||
<p><b>-i</b></p></td>
|
||||
<td width="7%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-i</b></p></td>
|
||||
<td width="5%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Internal address. IP address proxy accepts connections
|
||||
to. By default connection to any interface is accepted.
|
||||
It´s usually unsafe.</p></td></tr>
|
||||
<p style="margin-top: 1em">Internal address. IP address the
|
||||
proxy accepts connections to. By default, connections to any
|
||||
interface are accepted. It´s usually unsafe.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="4%">
|
||||
|
||||
|
||||
<p><b>-a</b></p></td>
|
||||
<td width="7%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-a</b></p></td>
|
||||
<td width="5%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Anonymous. Hide information about client.</p></td></tr>
|
||||
<p style="margin-top: 1em">Anonymous. Hide information
|
||||
about client.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="4%">
|
||||
|
||||
|
||||
<p><b>-a1</b></p></td>
|
||||
<td width="7%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-a1</b></p></td>
|
||||
<td width="5%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Anonymous. Show fake information about client.</p></td></tr>
|
||||
<p style="margin-top: 1em">Anonymous. Show fake information
|
||||
about client.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="4%">
|
||||
|
||||
|
||||
<p><b>-p</b></p></td>
|
||||
<td width="7%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-p</b></p></td>
|
||||
<td width="5%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>listening_port. Port proxy listens for incoming
|
||||
connections. Default is 1443.</p></td></tr>
|
||||
<p style="margin-top: 1em">listening_port. Port proxy
|
||||
listens for incoming connections. Default is 1443.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="4%">
|
||||
|
||||
|
||||
<p><b>-P</b></p></td>
|
||||
<td width="7%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-P</b></p></td>
|
||||
<td width="5%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>destination_port. Port to establish outgoing
|
||||
connections. One is required unless Transparent plugin is
|
||||
not used because TLS handshake does not contain port
|
||||
information. Default is 443.</p></td></tr>
|
||||
<p style="margin-top: 1em">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.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="4%">
|
||||
|
||||
|
||||
<p><b>-c</b></p></td>
|
||||
<td width="7%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-c</b></p></td>
|
||||
<td width="5%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>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 server send certificate (not compatible with TLS
|
||||
1.3), 4 - require mutual TLS, check server send certificate
|
||||
request and client sends certificate (not compatible with
|
||||
TLS 1.3)</p></td></tr>
|
||||
<p style="margin-top: 1em">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)</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="4%">
|
||||
|
||||
|
||||
<p><b>-l</b></p></td>
|
||||
<td width="7%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-l</b></p></td>
|
||||
<td width="5%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Log. By default logging is to stdout. If <i>logfile</i>
|
||||
is specified logging is to file. Under Unix, if
|
||||
´<i>@</i>´ preceeds <i>logfile</i>, syslog is
|
||||
used for logging.</p></td></tr>
|
||||
<p style="margin-top: 1em">Log. By default logging is to
|
||||
stdout. If <i>logfile</i> is specified logging is to file.
|
||||
Under Unix, if ´<i>@</i>´ precedes
|
||||
<i>logfile</i>, syslog is used for logging.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="4%">
|
||||
|
||||
|
||||
<p><b>-S</b></p></td>
|
||||
<td width="7%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-S</b></p></td>
|
||||
<td width="5%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Increase or decrease stack size. You may want to try
|
||||
something like -S8192 if you experience 3proxy crashes.</p></td></tr>
|
||||
<p style="margin-top: 1em">Increase or decrease stack size.
|
||||
You may want to try something like -S8192 if you experience
|
||||
3proxy crashes.</p></td></tr>
|
||||
</table>
|
||||
|
||||
<h2>CLIENTS
|
||||
|
|
@ -228,20 +235,18 @@ something like -S8192 if you experience 3proxy crashes.</p></td></tr>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">You should use
|
||||
client with HTTP proxy support or configure router to
|
||||
redirect HTTP traffic to proxy (transparent proxy).
|
||||
Configure client to connect to <i>internal_ip</i> and
|
||||
<i>port</i>. HTTPS support allows to use almost any TCP
|
||||
based protocol. If you need to limit clients, use
|
||||
<b>3proxy</b>(8) instead.</p>
|
||||
<p style="margin-left:6%; margin-top: 1em">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 <i>internal_ip</i> and <i>port</i>. If
|
||||
you need to limit clients, use <b>3proxy</b>(8) instead.</p>
|
||||
|
||||
<h2>BUGS
|
||||
<a name="BUGS"></a>
|
||||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">Report all bugs
|
||||
<p style="margin-left:6%; margin-top: 1em">Report all bugs
|
||||
to <b>3proxy@3proxy.org</b></p>
|
||||
|
||||
<h2>SEE ALSO
|
||||
|
|
@ -249,7 +254,7 @@ to <b>3proxy@3proxy.org</b></p>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">3proxy(8),
|
||||
<p style="margin-left:6%; margin-top: 1em">3proxy(8),
|
||||
ftppr(8), proxy(8), socks(8), pop3p(8), smtpp(8), tcppm(8),
|
||||
udppm(8), syslogd(8), <br>
|
||||
https://3proxy.org/</p>
|
||||
|
|
@ -259,7 +264,7 @@ https://3proxy.org/</p>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">3proxy is
|
||||
<p style="margin-left:6%; margin-top: 1em">3proxy is
|
||||
designed by Vladimir 3APA3A Dubrovin
|
||||
(<i>3proxy@3proxy.org</i>)</p>
|
||||
<hr>
|
||||
|
|
|
|||
139
udppm.md
139
udppm.md
|
|
@ -1,4 +1,4 @@
|
|||
<!-- Creator : groff version 1.22.4 -->
|
||||
<!-- Creator : groff version 1.24.1 -->
|
||||
<html>
|
||||
<head>
|
||||
|
||||
|
|
@ -25,7 +25,7 @@
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>udppm</b> -
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>udppm</b> -
|
||||
UDP port mapper</p>
|
||||
|
||||
<h2>SYNOPSIS
|
||||
|
|
@ -33,7 +33,7 @@ UDP port mapper</p>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><b>pop3p</b>
|
||||
<p style="margin-left:6%; margin-top: 1em"><b>udppm</b>
|
||||
[<b>-ds</b>] [<b>-l</b>[[<i>@</i>]<i>logfile</i>]]
|
||||
[<b>-i</b><i>internal_ip</i>] [<b>-e</b><i>external_ip</i>]
|
||||
<i>local_port remote_host remote_port</i></p>
|
||||
|
|
@ -44,7 +44,7 @@ UDP port mapper</p>
|
|||
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><i><b>udppm</b></i>
|
||||
<p style="margin-left:6%; margin-top: 1em"><i><b>udppm</b></i>
|
||||
forwards datagrams from local to remote UDP port</p>
|
||||
|
||||
<h2>OPTIONS
|
||||
|
|
@ -55,108 +55,111 @@ forwards datagrams from local to remote UDP port</p>
|
|||
<table width="100%" border="0" rules="none" frame="void"
|
||||
cellspacing="0" cellpadding="0">
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p style="margin-top: 1em"><b>-I</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p style="margin-top: 1em">Inetd mode. Standalone service
|
||||
only.</p> </td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p><b>-d</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-d</b></p></td>
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Daemonise. Detach service from console and run in the
|
||||
background.</p> </td></tr>
|
||||
<p style="margin-top: 1em">Daemonize. Detach service from
|
||||
console and run in the background.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p><b>-t</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-t</b></p></td>
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Be silenT. Do not log start/stop/accept error
|
||||
records.</p> </td></tr>
|
||||
<p style="margin-top: 1em">Be silenT. Do not log
|
||||
start/stop/accept error records.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p><b>-e</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-e</b></p></td>
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>External address. IP address of interface proxy should
|
||||
initiate datagrams from. By default system will deside which
|
||||
address to use in accordance with routing table.</p></td></tr>
|
||||
<p style="margin-top: 1em">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.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p><b>-i</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-i</b></p></td>
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Internal address. IP address proxy accepts datagrams to.
|
||||
By default connection to any interface is accepted.
|
||||
It´s usually unsafe.</p></td></tr>
|
||||
<p style="margin-top: 1em">Internal address. IP address the
|
||||
proxy accepts datagrams to. By default, connections to any
|
||||
interface are accepted. It´s usually unsafe.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p><b>-l</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-l</b></p></td>
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Log. By default logging is to stdout. If <i>logfile</i>
|
||||
is specified logging is to file. Under Unix, if
|
||||
´<i>@</i>´ preceeds <i>logfile</i>, syslog is
|
||||
used for logging.</p></td></tr>
|
||||
<p style="margin-top: 1em">Log. By default logging is to
|
||||
stdout. If <i>logfile</i> is specified logging is to file.
|
||||
Under Unix, if ´<i>@</i>´ precedes
|
||||
<i>logfile</i>, syslog is used for logging.</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p><b>-s</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-s</b></p></td>
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Single packet. By default only one client can use udppm
|
||||
service, but if -s is specified only one packet will be
|
||||
forwarded between client and server. It allows to share
|
||||
service between multiple clients for single packet services
|
||||
(for example name lookups).</p></td></tr>
|
||||
<p style="margin-top: 1em">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).</p></td></tr>
|
||||
<tr valign="top" align="left">
|
||||
<td width="11%"></td>
|
||||
<td width="6%"></td>
|
||||
<td width="3%">
|
||||
|
||||
|
||||
<p><b>-S</b></p></td>
|
||||
<td width="8%"></td>
|
||||
<td width="78%">
|
||||
<p style="margin-top: 1em"><b>-S</b></p></td>
|
||||
<td width="6%"></td>
|
||||
<td width="85%">
|
||||
|
||||
|
||||
<p>Increase or decrease stack size. You may want to try
|
||||
something like -S8192 if you experience 3proxy crashes.</p></td></tr>
|
||||
<p style="margin-top: 1em">Increase or decrease stack size.
|
||||
You may want to try something like -S8192 if you experience
|
||||
3proxy crashes.</p></td></tr>
|
||||
</table>
|
||||
|
||||
<h2>ARGUMENTS
|
||||
|
|
@ -165,19 +168,19 @@ something like -S8192 if you experience 3proxy crashes.</p></td></tr>
|
|||
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em"><i>local_port</i></p>
|
||||
<p style="margin-left:6%; margin-top: 1em"><i>local_port</i></p>
|
||||
|
||||
<p style="margin-left:22%;">- port udppm accepts
|
||||
datagrams</p>
|
||||
<p style="margin-left:15%;">- port udppm accepts datagrams
|
||||
on</p>
|
||||
|
||||
<p style="margin-left:11%;"><i>remote_host</i></p>
|
||||
<p style="margin-left:6%;"><i>remote_host</i></p>
|
||||
|
||||
<p style="margin-left:22%;">- IP address of the host
|
||||
<p style="margin-left:15%;">- IP address of the host
|
||||
datagrams are forwarded to</p>
|
||||
|
||||
<p style="margin-left:11%;"><i>remote_port</i></p>
|
||||
<p style="margin-left:6%;"><i>remote_port</i></p>
|
||||
|
||||
<p style="margin-left:22%;">- remote port datagrams are
|
||||
<p style="margin-left:15%;">- remote port datagrams are
|
||||
forwarded to</p>
|
||||
|
||||
<h2>CLIENTS
|
||||
|
|
@ -185,9 +188,9 @@ forwarded to</p>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">Any UDP based
|
||||
<p style="margin-left:6%; margin-top: 1em">Any UDP-based
|
||||
application can be used as a client. Use <i>internal_ip</i>
|
||||
and <i>local_port</i> as a destination in client
|
||||
and <i>local_port</i> as the destination in the client
|
||||
application. All datagrams are forwarded to
|
||||
<i>remote_host</i>:<i>remote_port</i></p>
|
||||
|
||||
|
|
@ -196,7 +199,7 @@ application. All datagrams are forwarded to
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">Report all bugs
|
||||
<p style="margin-left:6%; margin-top: 1em">Report all bugs
|
||||
to <b>3proxy@3proxy.org</b></p>
|
||||
|
||||
<h2>SEE ALSO
|
||||
|
|
@ -204,7 +207,7 @@ to <b>3proxy@3proxy.org</b></p>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">3proxy(8),
|
||||
<p style="margin-left:6%; margin-top: 1em">3proxy(8),
|
||||
proxy(8), ftppr(8), socks(8), pop3p(8), udppm(8),
|
||||
syslogd(8), <br>
|
||||
https://3proxy.org/</p>
|
||||
|
|
@ -214,7 +217,7 @@ https://3proxy.org/</p>
|
|||
</h2>
|
||||
|
||||
|
||||
<p style="margin-left:11%; margin-top: 1em">3proxy is
|
||||
<p style="margin-left:6%; margin-top: 1em">3proxy is
|
||||
designed by Vladimir 3APA3A Dubrovin
|
||||
(<i>3proxy@3proxy.org</i>)</p>
|
||||
<hr>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue