mirror of
https://github.com/3proxy/3proxy.git
synced 2026-11-22 15:59:41 +08:00
Update documentation
This commit is contained in:
1 parent
c6eddc69a1
commit
3d9d76fcf5
31 files changed
+1002
-1005
No files matched your search
+1
-1
@@ -1,2 +1,2 @@
|
||||
|
||||
<H2><A href="hotoe.html">See HowTo:</a></H2>
|
||||
<H2><A href="howtoe.html">See HowTo:</a></H2>
|
||||
+1
-1
@@ -1,2 +1,2 @@
|
||||
|
||||
<H2><A href="hotoe.html">См. HowTo</a></H2>
|
||||
<H2><A href="howtoe.html">См. HowTo</a></H2>
|
||||
+140
-140
@@ -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.
|
||||
+384
-385
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.
|
||||
|
||||
+17
-17
@@ -1,17 +1,17 @@
|
||||
<html><title>3proxy documentation</title><body><h2>3proxy documentation</h2>
|
||||
<a href="securityen.html">Security recommendations</a><br>
|
||||
<a href="highload.html">Optimizing 3proxy for high loads</a><br>
|
||||
<a href="howtoe.html">How To (English, very incomplete)</a><br>
|
||||
<a href="howtor.html">How To (Russian)</a><br>
|
||||
<h3>Man pages:</h>
|
||||
<br><A HREF="man8/3proxy.8.html">3proxy.8</A>
|
||||
<br><A HREF="man8/ftppr.8.html">ftppr.8</A>
|
||||
<br><A HREF="man8/pop3p.8.html">pop3p.8</A>
|
||||
<br><A HREF="man8/proxy.8.html">proxy.8</A>
|
||||
<br><A HREF="man8/smtpp.8.html">smtpp.8</A>
|
||||
<br><A HREF="man8/socks.8.html">socks.8</A>
|
||||
<br><A HREF="man8/tcppm.8.html">tcppm.8</A>
|
||||
<br><A HREF="man8/tlspr.8.html">tlspr.8</A>
|
||||
<br><A HREF="man8/udppm.8.html">udppm.8</A>
|
||||
<br><A HREF="man3/3proxy.cfg.3.html">3proxy.cfg.3</A>
|
||||
</body></html>
|
||||
<html><title>3proxy documentation</title><body><h2>3proxy documentation</h2>
|
||||
<a href="securityen.html">Security recommendations</a><br>
|
||||
<a href="highload.html">Optimizing 3proxy for high loads</a><br>
|
||||
<a href="howtoe.html">How To (English, very incomplete)</a><br>
|
||||
<a href="howtor.html">How To (Russian)</a><br>
|
||||
<h3>Man pages:</h3>
|
||||
<br><A HREF="man8/3proxy.8.html">3proxy.8</A>
|
||||
<br><A HREF="man8/ftppr.8.html">ftppr.8</A>
|
||||
<br><A HREF="man8/pop3p.8.html">pop3p.8</A>
|
||||
<br><A HREF="man8/proxy.8.html">proxy.8</A>
|
||||
<br><A HREF="man8/smtpp.8.html">smtpp.8</A>
|
||||
<br><A HREF="man8/socks.8.html">socks.8</A>
|
||||
<br><A HREF="man8/tcppm.8.html">tcppm.8</A>
|
||||
<br><A HREF="man8/tlspr.8.html">tlspr.8</A>
|
||||
<br><A HREF="man8/udppm.8.html">udppm.8</A>
|
||||
<br><A HREF="man3/3proxy.cfg.3.html">3proxy.cfg.3</A>
|
||||
</body></html>
|
||||
@@ -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>
|
||||
|
||||
@@ -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,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,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]".
|
||||
<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 into 3proxy 0.6 binary and source distribution
|
||||
<li>Plugin is included in the 3proxy 0.6 binary and source distribution
|
||||
</li></ul>
|
||||
|
||||
©Kirill Lopuchov
|
||||
© Kirill Lopuchov
|
||||
@@ -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,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)
|
||||
|
||||
@@ -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,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
|
||||
@@ -28,6 +28,6 @@ HTTP-запросов по порту TCP/80 будут видны параме
|
||||
<h4>Загрузить:</h4>
|
||||
<ul>
|
||||
<li>Плагин включен в дистрибутив 3proxy 0.8
|
||||
</ul>
|
||||
</li></ul>
|
||||
|
||||
© Vladimir Dubrovin, License: BSD style
|
||||
@@ -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>
|
||||
@@ -31,5 +31,5 @@ auth windows
|
||||
<h4>Загрузить:</h4>
|
||||
<ul>
|
||||
<li>Плагин включен в дистрибутив 3proxy 0.6
|
||||
</ul>
|
||||
</li></ul>
|
||||
|
||||
+24
-26
@@ -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>
|
||||
|
||||
+39
-39
@@ -3,26 +3,26 @@ KOI8-R
|
||||
Kirill Lopuchov, lopuchov at mail ru
|
||||
|
||||
<3proxy>
|
||||
Довольно часто перед системным администратором встает задача предоставить доступ к Internet-ресурсам группе пользователей (небольшой офис, Internet-кафе). Данную задачу можно решить, настроив на Internet-шлюзе proxy-сервер, службу NAT (трансляция сетевых адресов) или раздать каждому пользователю реальный IP адрес.
|
||||
Довольно часто перед системным администратором встает задача предоставить доступ к Internet-ресурсам группе пользователей (небольшой офис, Internet-кафе). Данную задачу можно решить, настроив на Internet-шлюзе proxy-сервер, службу NAT (трансляция сетевых адресов) или раздать каждому пользователю реальный IP адрес.
|
||||
|
||||
Давайте рассмотрим самый простой способ подключения - установку proxy-сервера. Традиционно для этих целей применяется популярный proxy Squid, но не всегда бывает необходимость в столь тяжеловатой программе :), да и в squid отсутствуют такие иногда необходимые вещи как SOCKS4/5-сервер, TCP/UP порт-маппинг. Поэтому вторым номером хочется представить вашему вниманию PROXY-сервер, под названием "3proxy" (http://3proxy.ru/), разработанный нашим программистом из г. Нижний Новгород. Одним из главных его достоинств является компактность и высокая переносимость. Код сервера написан так, что легко компилируется как для Win9x/2000/XP так и для Linux и FreeBSD.
|
||||
Давайте рассмотрим самый простой способ подключения - установку proxy-сервера. Традиционно для этих целей применяется популярный proxy Squid, но не всегда бывает необходимость в столь тяжеловатой программе :), да и в squid отсутствуют такие иногда необходимые вещи как SOCKS4/5-сервер, TCP/UP порт-маппинг. Поэтому вторым номером хочется представить вашему вниманию PROXY-сервер, под названием "3proxy" (http://3proxy.ru/), разработанный нашим программистом из г. Нижний Новгород. Одним из главных его достоинств является компактность и высокая переносимость. Код сервера написан так, что легко компилируется как для Win9x/2000/XP так и для Linux и FreeBSD.
|
||||
|
||||
Сервер поддерживает следующие возможности:
|
||||
Сервер поддерживает следующие возможности:
|
||||
|
||||
HTTP(S) proxy;
|
||||
FTP over HTTP proxy;
|
||||
SOCKS4/5 proxy;
|
||||
POP3 proxy;
|
||||
TCP & UDP маппинг портов;
|
||||
листы доступа к различным службам и адресам;
|
||||
ограничение пропускной способности канала каждого пользователя (чтобы пользователь не съел весь канал, качая кучу файлов в несколько потоков :) );
|
||||
ограничение трафика пользователя на день, неделю и месяц;
|
||||
авторизацию пользователей ко всем proxy-службам по имени и паролю или по ip адресам;
|
||||
ведение журналов через ODBC (по-моему, такого нет ни в одном proxy) и syslog и т. д.
|
||||
TCP & UDP маппинг портов;
|
||||
листы доступа к различным службам и адресам;
|
||||
ограничение пропускной способности канала каждого пользователя (чтобы пользователь не съел весь канал, качая кучу файлов в несколько потоков :) );
|
||||
ограничение трафика пользователя на день, неделю и месяц;
|
||||
авторизацию пользователей ко всем proxy-службам по имени и паролю или по ip адресам;
|
||||
ведение журналов через ODBC (по-моему, такого нет ни в одном proxy) и syslog и т. д.
|
||||
|
||||
К недостаткам можно отнести отсутствие кэширования информации :-|. Но в последнее время Inernet-контент становится все более динамичным (то есть не поддающийся кэшированию) и может быть для кого-то экономия в 25% трафика за счет его кэширования не будет столь критична. Для тех пользователей, кому она может оказаться критичной, автор предлагает использовать цепочку из 2-х серверов и в качестве кэша такие сервера как wwwoffle или им подобные, либо ждать появления поддержки кеша в 3proxy :)
|
||||
К недостаткам можно отнести отсутствие кэширования информации :-|. Но в последнее время Inernet-контент становится все более динамичным (то есть не поддающийся кэшированию) и может быть для кого-то экономия в 25% трафика за счет его кэширования не будет столь критична. Для тех пользователей, кому она может оказаться критичной, автор предлагает использовать цепочку из 2-х серверов и в качестве кэша такие сервера как wwwoffle или им подобные, либо ждать появления поддержки кеша в 3proxy :)
|
||||
|
||||
Установка
|
||||
Установка
|
||||
|
||||
# wget http://3proxy.ru/current/3proxy.tgz
|
||||
# tar -xvzf 3proxy.tgz
|
||||
@@ -35,64 +35,64 @@ TCP & UDP
|
||||
# touch /usr/local/3proxy/3proxy.cfg
|
||||
# chown -R nobody:nogroup /usr/local/3proxy
|
||||
|
||||
Далее приведу небольшой пример конфигурационного файла 3proxy.cfg с
|
||||
комментариями, более подробную информацию по конфигурированию можно
|
||||
найти файле 3proxy.cfg.sample или в
|
||||
Далее приведу небольшой пример конфигурационного файла 3proxy.cfg с
|
||||
комментариями, более подробную информацию по конфигурированию можно
|
||||
найти файле 3proxy.cfg.sample или в
|
||||
HowTo http://3proxy.ru/howtor.asp
|
||||
и FAQ http://3proxy.ru/faqr.asp
|
||||
и FAQ http://3proxy.ru/faqr.asp
|
||||
|
||||
-------------3proxy.cfg-------------
|
||||
# ВНИМАНИЕ !! не должны быть пробелов
|
||||
# перед любыми опциями конфигурации !!
|
||||
# ВНИМАНИЕ !! не должны быть пробелов
|
||||
# перед любыми опциями конфигурации !!
|
||||
|
||||
# ip-адрес DNS-сервера провайдера или локального
|
||||
# ip-адрес DNS-сервера провайдера или локального
|
||||
nserver 127.0.0.1
|
||||
timeouts 1 5 30 60 180 1800 15 60
|
||||
|
||||
# Создаем двух пользователей vasia, petia и vova
|
||||
# и назначаем им пароли 24555, 14656 и 45455 соответственно
|
||||
# Создаем двух пользователей vasia, petia и vova
|
||||
# и назначаем им пароли 24555, 14656 и 45455 соответственно
|
||||
users vasia:CL:24555
|
||||
users petia:CL:14656
|
||||
users vova:CL:45455
|
||||
|
||||
# Лог-файл со списком запросов пользователей
|
||||
# будет создаваться каждый день новый
|
||||
# Лог-файл со списком запросов пользователей
|
||||
# будет создаваться каждый день новый
|
||||
log /usr/local/3proxy/logs/3proxy.log D
|
||||
logformat "%d-%m-%Y %H:%M:%S %U %C:%c %R:%r %O %I %T"
|
||||
|
||||
# Внешний интерфейс,
|
||||
# через который будут уходить запросы от сервера
|
||||
# Внешний интерфейс,
|
||||
# через который будут уходить запросы от сервера
|
||||
external 10.1.1.1
|
||||
|
||||
# ip-адрес интерфейса, на котором будут приниматься
|
||||
# запросы от клиентов
|
||||
# ip-адрес интерфейса, на котором будут приниматься
|
||||
# запросы от клиентов
|
||||
internal 192.168.1.1
|
||||
|
||||
# Устанавливаем тип авторизации по имени и паролю
|
||||
# Устанавливаем тип авторизации по имени и паролю
|
||||
auth strong
|
||||
# Разрешаем доступ к портам 80,8080-8088
|
||||
# Разрешаем доступ к портам 80,8080-8088
|
||||
allow * * * 80,8080-8088
|
||||
# Расскоментировать секцию parent, если у вас есть прокси верхнего
|
||||
# уровня и заменить ip, порт, имя пользователя и пароль на свои значения
|
||||
# Расскоментировать секцию parent, если у вас есть прокси верхнего
|
||||
# уровня и заменить ip, порт, имя пользователя и пароль на свои значения
|
||||
# parent 1000 http 192.168.0.1 8080 username passwd
|
||||
# allow *
|
||||
# Запускаем службу HTTP-proxy на порту (3128) и
|
||||
# (-n) c отключенной NTLM-авторизацией)
|
||||
# Запускаем службу HTTP-proxy на порту (3128) и
|
||||
# (-n) c отключенной NTLM-авторизацией)
|
||||
proxy -p3128 -n
|
||||
|
||||
# Ограничиваем толшину канала для пользователей
|
||||
# vasia и petia в 20000 bps,
|
||||
# а для vova 10000 bps
|
||||
# Ограничиваем толшину канала для пользователей
|
||||
# vasia и petia в 20000 bps,
|
||||
# а для vova 10000 bps
|
||||
bandlimin 20000 vasia,petia
|
||||
bandlimin 10000 vova
|
||||
|
||||
# Запускаем сервер от пользователя nobody
|
||||
# (возможно в вашей ОС uid и gid пользователя nobody
|
||||
# будут другими. Для их определения воспользуйтесь коммандой id nobody)
|
||||
# Запускаем сервер от пользователя nobody
|
||||
# (возможно в вашей ОС uid и gid пользователя nobody
|
||||
# будут другими. Для их определения воспользуйтесь коммандой id nobody)
|
||||
setgid 65534
|
||||
setuid 65534
|
||||
------------------------------------
|
||||
|
||||
После того как мы создали конфигурационный файл сервера, запускаем 3proxy командой:
|
||||
После того как мы создали конфигурационный файл сервера, запускаем 3proxy командой:
|
||||
/usr/local/3proxy/3proxy /usr/local/3proxy/3proxy.cfg
|
||||
|
||||
+17
-17
@@ -2,9 +2,9 @@ KOI8-R
|
||||
|
||||
Kirill Lopuchov, lopuchov at mail ru
|
||||
|
||||
÷ÅÄÅÎÉÅ ÌÏÇÏ× ÓÅÒ×ÅÒÁ × SQL-ÂÁÚÅ ÉÍÅÅÔ Ó×ÏÉ ÐÒÉÅÍÕÝÅÓÔ×Á ÐÅÒÅÄ ÏÂÙÞÎÙÍÉ ÔÅËÓÔÏ×ÙÍÉ ÆÁÊÌÁÍÉ. 3proxy ÐÏÄÄÅÒÖÉ×ÁÅÔ ×ÅÄÅÎÉÅ ÌÏÇÏ× ÞÅÒÅÚ ODBC-ÍÅÎÅÄÖÅÒ × ÌÀÂÏÊ ÂÁÚÅ ÄÁÎÎÙÈ, ÉÍÅÀÝÉÈ ODBC-ÄÒÁÊ×ÅÒ. üÔÏÔ ÍÅÎÅÄÖÅÒ ÓÔÁÌ ÓÔÁÎÄÁÒÔÏÍ ÄÅ-ÆÁËÔÏ × ÓÒÅÄÅ Windows, ÞÅÇÏ, Ë ÓÏÖÁÌÅÎÉÀ, ÎÅ ÓËÁÖÅÛØ ÐÒÏ Unix. ðÏÜÔÏÍÕ ÄÁÌÅÅ ÒÁÓÓÍÏÔÒÉÍ ÎÁ ÐÒÉÍÅÒÅ FreeBSD ÎÁÓÔÒÏÊËÕ ×ÅÄÅÎÉÑ ÌÏÇÏ× × ÂÁÚÅ SQLite. üÔÁ ÂÁÚÁ ÄÁÎÎÙÈ ×ÙÂÒÁÎÁ × ËÁÞÅÓÔ×Å ÐÒÉÍÅÒÁ ÐÏÔÏÍÕ, ÞÔÏ ÏÎÁ ÐÒÏÓÔÁ × ÕÓÔÁÎÏ×ËÅ É ÎÁÓÔÒÏËÅ (× ÐÒÉÎÃÉÐÅ ÎÁÓÔÒÏÊËÁ ×ÅÄÅÎÉÑ ÌÏÇÏ× × ÌÀÂÏÊ ÄÒÕÇÏÊ ÂÁÚÅ mysql ÉÌÉ postgresql ÏÔÌÉÞÁÅÔÓÑ ÔÏÌØËÏ ÎÁÓÔÒÏÊËÏÊ ÅÇÏ odbc-ÄÒÁÊ×ÅÒÁ)
|
||||
Ведение логов сервера в SQL-базе имеет свои приемущества перед обычными текстовыми файлами. 3proxy поддерживает ведение логов через ODBC-менеджер в любой базе данных, имеющих ODBC-драйвер. Этот менеджер стал стандартом де-факто в среде Windows, чего, к сожалению, не скажешь про Unix. Поэтому далее рассмотрим на примере FreeBSD настройку ведения логов в базе SQLite. Эта база данных выбрана в качестве примера потому, что она проста в установке и настроке (в принципе настройка ведения логов в любой другой базе mysql или postgresql отличается только настройкой его odbc-драйвера)
|
||||
|
||||
õÓÔÁÎÁ×ÌÉ×ÁÅÍ SQLite
|
||||
Устанавливаем SQLite
|
||||
wget http://www.sqlite.org/sqlite-2.8.14.tar.gz
|
||||
tar -xvzf sqlite-2.8.14.tar.gz
|
||||
cd sqlite
|
||||
@@ -12,7 +12,7 @@ cd sqlite
|
||||
gmake
|
||||
gmake install
|
||||
|
||||
õÓÔÁÎÁ×ÌÉ×ÁÅÍ iODBC ÍÅÎÅÄÖÅÒ
|
||||
Устанавливаем iODBC менеджер
|
||||
wget http://www.iodbc.org/libiodbc-3.51.2.tar.gz
|
||||
tar -xvzf libiodbc-3.51.2.tar.gz
|
||||
cd libiodbc-3.51.2
|
||||
@@ -20,24 +20,24 @@ cd libiodbc-3.51.2
|
||||
make
|
||||
make install
|
||||
|
||||
õÓÔÁÎÁ×ÌÉ×ÁÅÍ odbc ÄÒÁÊ×ÅÒ SQLite
|
||||
Устанавливаем odbc драйвер SQLite
|
||||
wget http://www.ch-werner.de/sqliteodbc/sqliteodbc-0.62.tar.gz
|
||||
tar -xvzf sqliteodbc-0.62.tar.gz
|
||||
cd sqliteodbc-0.62
|
||||
|
||||
./configure
|
||||
åÓÌÉ Õ ×ÁÓ ÓËÒÉÐÔ configure ×ÙÄÁÌ ÏÛÉÂËÕ :
|
||||
Если у вас скрипт configure выдал ошибку :
|
||||
(configure: error: SQLite library too old)
|
||||
ÔÏ ÅÅ ÍÏÖÎÏ ÐÏÐÒÏÂÏ×ÁÔØ ÏÂÏÊÔÉ, ×ÓÔÁ×É× (SQLITE_COMPILE=1
|
||||
× ÓÔÒ. 5092 ÐÏÓÌÅ ÕÓÌÏ×ÉÑ if endif) × ÆÁÊÌÅ configure
|
||||
то ее можно попробовать обойти, вставив (SQLITE_COMPILE=1
|
||||
в стр. 5092 после условия if endif) в файле configure
|
||||
make
|
||||
make install
|
||||
|
||||
|
||||
äÁÌÅÅ ÎÁÓÔÒÁÉ×ÁÅÍ ÚÁÐÉÓÉ ÄÌÑ iODBC ÍÅÎÅÄÖÅÒÁ ×
|
||||
ÆÁÊÌÁÈ /etc/odbcinst.ini É /etc/odbc.ini
|
||||
Далее настраиваем записи для iODBC менеджера в
|
||||
файлах /etc/odbcinst.ini и /etc/odbc.ini
|
||||
|
||||
îÁÓÔÒÁÉ×ÁÅÍ odbc ÄÒÁÊ×ÅÒ
|
||||
Настраиваем odbc драйвер
|
||||
--------------/etc/odbcinst.ini-------------
|
||||
[ODBC Drivers]
|
||||
SQLite=Installed
|
||||
@@ -46,8 +46,8 @@ SQLite=Installed
|
||||
Driver=/usr/local/lib/libsqliteodbc.so
|
||||
---------------------------------------
|
||||
|
||||
óÏÚÄÁÅÍ DSN ÄÌÑ ÂÁÚÙ c ÉÍÅÎÅÍ "sqlite", ËÏÔÏÒÁÑ ÂÕÄÅÔ
|
||||
ÒÁÓÐÏÌÁÇÁÔØÓÑ × ËÁÔÁÌÏÇÅ: /usr/local/3proxy/logs.db
|
||||
Создаем DSN для базы c именем "sqlite", которая будет
|
||||
располагаться в каталоге: /usr/local/3proxy/logs.db
|
||||
|
||||
--------------/etc/odbc.ini----------------
|
||||
[ODBC Data Sources]
|
||||
@@ -61,8 +61,8 @@ Database=/usr/local/3proxy/logs.db
|
||||
Timeout=2000
|
||||
---------------------------------------
|
||||
|
||||
óÏÚÄÁÅÍ ÂÁÚÕ ÄÌÑ ÌÏÇÏ× É ÔÁÂÌÉÃÕ × ÆÏÒÍÁÔÅ (logformat
|
||||
ÓÍ. ÏÐÉÓÁÎÉÅ × 3proxy.cfg.sample )
|
||||
Создаем базу для логов и таблицу в формате (logformat
|
||||
см. описание в 3proxy.cfg.sample )
|
||||
|
||||
sqlite /usr/local/3proxy/logs.db
|
||||
|
||||
@@ -79,7 +79,7 @@ sqlite>create table log (
|
||||
...>);
|
||||
|
||||
|
||||
äÏÂÁ×ÌÑÅÍ ÓÌÅÄÕÀÝÉÅ ÚÁÐÉÓÉ × ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÊ ÆÁÊÌ 3proxy.cfg
|
||||
Добавляем следующие записи в конфигурационный файл 3proxy.cfg
|
||||
---------------3proxy.cfg-----------------
|
||||
log &sqlite
|
||||
|
||||
@@ -88,12 +88,12 @@ l_descr)
|
||||
values ('%d-%m-%Y', '%H:%M:%S', '%U', '%N', %I, %O, '%T')"
|
||||
------------------------------------------
|
||||
|
||||
CÏÂÒÁÔØ 3proxy c ÐÏÄÄÒÅÖËÏÊ iODBC, ÄÌÑ ÜÔÏÇÏ × Makefile.unix ÐÏÍÅÎÑÔØ
|
||||
Cобрать 3proxy c поддрежкой iODBC, для этого в Makefile.unix поменять
|
||||
|
||||
CFLAGS = -Wall -O2 -c -pthread -D_THREAD_SAFE -D_REENTRANT -DWITH_STD_MALLOC -I/usr/local/include
|
||||
LIBS = -L /usr/local/lib -lodbc
|
||||
|
||||
É ÄÁÔØ ËÏÍÁÎÄÙ
|
||||
и дать команды
|
||||
|
||||
make clean
|
||||
make -f Makefile.unix
|
||||
|
||||
+8
-8
@@ -1,6 +1,6 @@
|
||||
Eugene: Re: 3proxy 0.6 + iODBC + PostgreSQL 22.11.2007 19:04:23
|
||||
Наконец-то я разобрался и запустил.
|
||||
1. Я использовал пакет unixODBC.
|
||||
Наконец-то я разобрался и запустил.
|
||||
1. Я использовал пакет unixODBC.
|
||||
2. /etc/unixODBC/odbc.ini
|
||||
[proxy]
|
||||
Description = PostgreSQL ODBC driver
|
||||
@@ -12,7 +12,7 @@ ServerName = localhost
|
||||
Description = PostgreSQL ODBC driver
|
||||
Driver = /usr/local/lib/psqlodbcw.so
|
||||
Setup = /usr/lib/libodbcpsqlS.so
|
||||
4. Собирал вручную psqlodbc-08.02.0500, слитый с postgresql.org (получился psqlodbcw.so).
|
||||
4. Собирал вручную psqlodbc-08.02.0500, слитый с postgresql.org (получился psqlodbcw.so).
|
||||
5. 3proxy.conf
|
||||
log &proxy,logger,123
|
||||
logformat "LINSERT INTO logger (ldatetime,username,userip,trafin,trafout,service,host,port,
|
||||
@@ -20,9 +20,9 @@ url) VALUES ('%Y-%m-%d %H:%M:%S','%U','%C',
|
||||
'%I','%O','%N',
|
||||
'%n','%r','%T');"
|
||||
|
||||
То есть пароли и логины в odbc.ini прописывать не надо - система падает на драйвере ODBC.
|
||||
Использовать libiodbc тоже не надо - система падает на libiodbc.so.
|
||||
То есть пароли и логины в odbc.ini прописывать не надо - система падает на драйвере ODBC.
|
||||
Использовать libiodbc тоже не надо - система падает на libiodbc.so.
|
||||
|
||||
Все вышесказанное справедливо для unixODBC + psqlodbc производства postgresql.org, как с -DSAFESQL, так и без оного.
|
||||
С myodbc + unixODBC проблем не наблюдалось никаких.
|
||||
Шаманство, в общем ;)
|
||||
Все вышесказанное справедливо для unixODBC + psqlodbc производства postgresql.org, как с -DSAFESQL, так и без оного.
|
||||
С myodbc + unixODBC проблем не наблюдалось никаких.
|
||||
Шаманство, в общем ;)
|
||||
Reference in new issue
Block a user