3proxy.cfg - 3proxy configuration file
Common structure:
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.
Comments:
Any string beginning with space character or '#' character is comment. It's ignored.
Quotation:
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.
File inclusion:
You can include file by using $FILENAME macro (replace FILENAME with a path to file, for example $/usr/local/etc/3proxy/conf.incl or $"c:\Program Files\3proxy\include.cfg" Quotation is required in last example because path contains space character. For included file
Next commands start gateway services:
proxy [options]
socks [options]
pop3p [options]
ftppr [options]
admin [options]
dnspr [options]
tcppm [options]
udppm [options]
Descriptions:
proxy - HTTP/HTTPS proxy (default port 3128)
socks - SOCKS 4/4.5/5 proxy (default port 1080)
pop3p - POP3 proxy (default port 110)
ftppr - FTP proxy (default port 21)
admin - Web interface (default port 80)
dnspr - caching DNS proxy (default port 53)
tcppm - TCP portmapper
udppm - UDP portmapper
Options:
-pNUMBER change default server port to NUMBER
-n disable NTLM authentication (required if passwords are stored in Unix crypt format.
-s (for admin) - allow only secure operations (currently only traffic counters view without ability to reset).
-a (for proxy) - anonymous proxy (no information about client reported)
-a1 (for proxy) - anonymous proxy (random client information reported)
Also, all options mentioned for proxy(8) socks(8) pop3p(8) tcppm(8) udppm(8) ftppr(8) are also supported.
Portmapping services listen at SRCPORT and connect to DSTADDR:DSTPORT HTTP and SOCKS proxies are standard.
POP3 proxy must be configured as POP3 server and requires username in the form of: pop3username@pop3server. If POP3 proxy access must be authenticated, you can specify username as proxy_username:proxy_password:POP3_username@pop3server
DNS proxy resolves any types of records but only hostnames are cached. It requires nserver/nscache to be configured.
FTP proxy can be used as FTP server in any FTP client or configured as FTP proxy on a client with FTP proxy support. Username format is one of
FTPuser@FTPServer
FTPuser:FTPpassword@FTPserver
proxyuser:proxypassword:FTPuser:FTPpassword@FTPserver
config
Path to configuration file to use on 3proxy restart or to save configuration.
writable
ReOpens configuration file for write access via Web interface, and re-reads it. Usually should be first command on config file but in combination with "config" it can be used anywhere to open alternate config file. Think twice before using it.
end
End of configuration
log [[@|&]logfile] [
sets logfile for all gateways
@ - (for Unix) use syslog, filename is used as ident name
& - use ODBC, filename consists of comma-delimited datasource,username,password (username and password are optional)
LOGTYPE is one of:
M - Monthly
W - Weekly (starting from Sunday)
D - Daily
H - Hourly
if logfile is not specified logging goes to stdout. You can specify individual logging options for gateway by using -l option in gateway configuration.
"log" command supports same format specifications for filename template as "logformat" (if filename contains '%' sign it's believed to be template). As with "logformat" filename must begin with 'L' or 'G' to specify Local or Grinwitch time zone for all time-based format specificators.
rotate
logformat
Format for log record. First symbol in format must be L (local time) or G (absolute Grinwitch time). It can be preceeded with -XXX+Y where XXX is list of characters to be filtered in user input (any non-printable characters are filtered too in this case) and Y is replacement character. For example, "-,%+ L" in the beginning of logformat means comma and percent are replaced with space and all time based elemnts are in local time zone.
You can use:
%y - Year in 2 digit format
%Y - Year in 4 digit format
%m - Month number
%o - Month abbriviature
%d - Day
%H - Hour
%M - Minute
%S - Second
%t - Timstamp (in seconds since 01-Jan-1970)
%. - milliseconds
%z - timeZone (from Grinvitch)
%D - request duration (in milliseconds)
%b - average send rate per request (in Bytes per second) this speed is typically below connection speed shown by download manager.
%B - average receive rate per request (in Bytes per second) this speed is typically below connection speed shown by download manager.
%U - Username
%N - service Name
%p - service Port
%E - Error code
%C - Client IP
%c - Client port
%R - Remote IP
%r - Remote port
%e - External IP used to establish connection
%Q - Requested IP
%q - Requested port
%n - requested hostname
%I - bytes In
%O - bytes Out
%h - Hops (redirections) count
%T - service specific Text
%N1-N2T - (N1 and N2 are positive numbers) - log only fields from N1 thorugh N2 of service specific text
in case of ODBC logging logformat specifies SQL statement, for exmample:
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')"
logdump
Immediately creates additional log records if given amount of incoming/outgoing traffic is achieved for connection, without waiting for connection to finish. It may be useful to prevent information about long-lasting downloads on server shutdown.
archiver
Archiver to use for log files.
timeouts
Sets timeout values
BYTE_SHORT - short timeout for single byte, is usually used for receiving single byte from stream.
BYTE_LONG - long timeout for single byte, is usually used for receiving first byte in frame (for example first byte in socks request).
STRING_SHORT - short timeout, for character string within stream (for example to wait between 2 HTTP headers)
STRING_LONG - long timeout, for first string in stream (for example to wait for HTTP request).
CONNECTION_SHORT - inactivity timeout for short connections (HTTP, POP3, etc).
CONNECTION_LONG - inactivity timeout for long connection (SOCKS, portmappers, etc).
DNS - timeout for DNS request before requesting next server
CHAIN - timeout for reading data from chained connection
nserver
Nameserver to use for name resolutions. If none spcified system or name server fails system routines for name resolution will be used. It's better to specify nserver because gethostbyname() may be thread unsafe.
nscache
Cache
nsrecord
fakeresolve 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+.
dialer
Execute progname if external name can't be resolved. Hint: if you use nscache, dialer may not work, because names will be resolved through cache. In this case you can use something like http://dial.right.now/ from browser to set up connection.
internal
sets ip address of internal interface. This IP address will be used to bind gateways. Alternatively you can use -i option for individual gateways
external
sets ip address of external interface. This IP address will be source address for all connections made by proxy. Alternatively you can use -e option to specify individual address for gateway.
maxconn
sets maximum number of simulationeous connections to each services started after this command. Default is 100.
service
(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.
daemon
Should be specified to close 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 place it in the beginning of the configuration file.
auth
Type of user authorization. Currently supported:
none - no authentication or authorization required. Note: is auth is none any ip based limitation, redirection, etc will not work. This is default authentication type
iponly - authentication by access control list with username ignored. Appropriate for most cases
username - authentication by username without checking for any password with authorization by ACLs. Usefule for e.g. SOCKSv4 proxy.
nbname - authentication by NetBIOS name with authorization by ACLs. Messanger service should be started on user's machine. Note, that Windows 95/98 hosts do not have messanger service by default, WinPopup program need to be started. NB: there is no any password check, name may be spoofed. Think about it as about ident for Windows. Q: Will ident authorization be implemented? A: Yes, as soon as it will be required by someone.
strong - username/password authentication required. It will work with SOCKSv5, FTP, POP3 and HTTP proxy.
cache - cached authentication, may be used with 'authcache'.
Plugins may add additional authentication types.
It's possible to use few authentication types in the same commands. E.g.
auth iponly strong
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.
authcache
Cache authentication information to given amount of time (cachetime) in seconds. Cahtype is one of:
ip - after successful authentication all connections during caching time from same IP are assigned to the same user, username is not requested.
ip,user username is requested and all connections from the same IP are assigned to the same user without actual authentication.
user - same as above, but IP is not checked.
user,password - both username and password are checked against cached ones.
Use auth type 'cache' for cached authentication
allow
deny
Access control entries. All lists are comma-separated, no 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) 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
allow *
If access list is not empty last item in access list is assumed to be
deny *
You may want explicitly add "deny *" to the end of access list to prevent HTTP proxy from requesting user's password. Access lists are checked after user have requested any resource. If you want 3proxy to reject connections from specific addresses immediately without any conditions you should either bind proxy to appropriate interface only or to use ip filters.
Operation is one of:
CONNECT - establish outgoing TCP connection
BIND - bind TCP port for listening
UDPASSOC - make UDP association
ICMPASSOC - make ICMP association (for future use)
HTTP_GET - HTTP GET request
HTTP_PUT - HTTP PUT request
HTTP_POST - HTTP POST request
HTTP_HEAD - HTTP HEAD request
HTTP_CONNECT - HTTP CONNECT request
HTTP_OTHER - over HTTP request
HTTP - matches any HTTP request except HTTP_CONNECT
HTTPS - same as HTTP_CONNECT
FTP_GET - FTP get request
FTP_PUT - FTP put request
FTP_LIST - FTP list request
FTP_DATA - FTP data connection. Note: FTP_DATA requires access to dynamic non-ptivileged (1024-65535) ports on remote side.
FTP - matches any FTP/FTP Data request
ADMIN - access to administration interface
type is one of:
tcp - simply redirect connection. TCP is always last in chain.
http - redirect to HTTP proxy. HTTP is always last chain.
pop3 - redirect to POP3 proxy (only local redirection is supported, can not be used for chaining)
ftp - redirect to FTP proxy (only local redirection is supported, can not be used for chaining)
connect - parent is HTTP CONNECT method proxy
connect+ - parent is HTTP CONNECT proxy with name resolution
socks4 - parent is SOCKSv4 proxy
socks4+ - parent is SOCKSv4 proxy with name resolution (SOCKSv4a)
socks5 - parent is SOCKSv5 proxy
socks5+ - parent is SOCKSv5 proxy with name resolution
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+).
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 need it.
admin - redirect request to local 'admin' service (with -s parameter).
Use "+" proxy only with "fakeresolve" option
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 IP is changed. If both IP and port are zero - it's a special case of local redirection, it works only with socks proxy. In case of local redirection request is redirected to different service, ftp locally redirects to ftppr pop3 locally redirects to pop3p httplocally redurects to proxy admin locally redirects to admin -s service.
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 redirected (HTTP, FTP or POP3) after 'parent' command. It means, additional 'allow' command is required for redirected requests, for example:
allow * * * 80
parent 1000 http 0.0.0.0 0
allow * * * 80 HTTP_GET,HTTP_POST
socks
redirects all SOCKS requests with target port 80 to local HTTP proxy, local HTTP proxy parses requests and allows only GET and POST requests.
parent 1000 http 1.2.3.4 0
Changes external address for given connection to 1.2.3.4 (an equivalent to -e1.2.3.4)
Optional username and password are used to authenticate on parent proxy. Username of '*' means username must be supplied by user.
nolog
allow * * 192.168.1.1
nolog
weight
allow * * 192.168.1.1
weight 100
Weight may be used for different purposes.
bandlimin
nobandlimin
nobandlimout
bandlim sets bandwith limitation filter to
bandlimin 57600 * 192.168.10.16
bandlimin 57600 * 192.168.10.17
bandlimin 57600 * 192.168.10.18
bandlimin 57600 * 192.168.10.19
and every of you clients will have 56K channel.
counter
countin
nocountin
countout
nocountout
counter, countin, nocountin, countout, noucountout 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 no traffic information on this counter is saved in file (that is if proxy restarted all information is loosed) overwise it should be unique sequential number. Type specifies a type of counter. Type is one of:
D - counter is resetted daily
W - counter is resetted weekly
M - counter is resetted monthely
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:
The rest of parameters is identical to bandlim/nobandlim.
users username[:pwtype:password] ...
pwtype is one of:
none (empty) - use system authentication
CL - password is cleartext
CR - password is crypt-style password
NT - password is NT password (in hex)
example:
users test1:CL:password1 "test2:CR:$1$lFDGlder$pLRb4cU2D7GAT58YQvY49."
users test3:NT:BD7DFBF29A93F93C63CB84790DA00E63
system
execute system command
pidfile
write pid of current process to file. It can be used to manipulate 3proxy with signals under Unix. Currently next signals are available:
monitor
If file monitored changes in modification time or size, 3proxy reloads configuration within one minute. Any number of files may be monitored.
setuid
calls setuid(uid), uid must be numeric. Unix only. Warning: under some Linux kernels setuid() works onle for current thread. It makes it impossible to suid for all threads.
setgid
calls setgid(gid), gid must be numeric. Unix only.
chroot
calls chroot(path). Unix only.
plugin
Loads specified library and calls given export function with given arguments, as
int functions_to_call(struct pluginlink * pl, int argc, char * argv[]);
function_to_call must return 0 in case of success, value > 0 to indicate error.
filtermaxsize
If Content-length (or another data length) is greater than given value, no data filtering will be performed thorugh filtering plugins to avoid data corruption and/or Content-Length chaging. Default is 1MB (1048576).
---------------------------------
例子:
#后台进程
daemon
#DNS服务器
nserver 8.8.8.8
#DNS缓存
nscache 65536
#超时
timeouts 1 5 30 60 180 1800 15 60
#日志
log /var/log/3proxy.log
logformat "- +_L%t.%. %N.%p %E %U %C:%c %R:%r %O %I %h %T"
rotate 30
#用户 CL明文密码
users user1:CL:pwd user2:CL:pwd
#权限控制参数
#allow
#deny
#开启socks和http代理,指定监听端口和出口IP
auth iponly strong
allow user1,user2
allow * 192.168.0.0/16 *
socks -p1080 -e192.168.1.1
socks -p1081 -e192.168.1.2
proxy -p8080 -e192.168.1.1
proxy -p8081 -e192.168.1.2
flush
#开启HTTP代理,端口3128,轮换出口IP
auth iponly
allow *
parent 500 http 192.168.1.2 0
parent 500 http 192.168.1.1 0
proxy -p3128
flush
#开启上层代理,HTTP端口1234,轮换上层socks5代理
auth iponly
allow *
parent 500 socks5 192.168.1.1 7777
parent 500 socks5 192.168.1.1 7070
parent 500 connect 192.168.1.1 3128
proxy -p1234
flush