|
|
发表于 2003-6-22 22:03:37
|
显示全部楼层
我的配置文件, 要按你的情况修改的
# $Id: socks.conf,v 1.28 2001/12/12 13:56:42 karls Exp $
#
# A sample socks.conf
# The configfile is divided into two parts; first misc. settings,
# then the routes. Objects in '[]' are optional.
#
#
# recommended order is:
# [debug]
# [logoutput]
# [resolveprotocol]
#
# routes:
# from to via
# [command]
# [extension]
# [protocol]
# [proxyprotocol]
debug: 1 # uncomment to enable debugging
#logoutput: stdout # users usually don't want to be bothered with that.
# What protocol should be used for resolving hostnames? It's important
# to set this right.
#resolveprotocol: udp # default
#resolveprotocol: tcp # set this if your socksserver only supports socksv4.
#resolveprotocol: fake # set this if your clients can't access nameserver,
# neither directly nor proxied.
#
# the routes
#
# specifying routes for accepting remote connections (via bind()) is
# difficult since we can't know what the "to:" address is
# until we actually get the connection Since we support letting
# the client accept connections both via the proxyserver and
# "directly" at the same time, we have two options though:
# a) specify a route for bind (only) first going via the proxyserver.
# This will also handle "direct" connections.
# b) specify a route for bind (only) first going "direct".
# This means clients will only be able to accept "direct"
# connections.
# we want to accept remote connections via the proxyserver.
#route {
# from: 0.0.0.0/0 to: 0.0.0.0/0 via: 10.1.1.1 port = 1080
# command: bind
#}
# we do not want to accept remote connections via the proxyserver.
#route {
# from: 0.0.0.0/0 to: 0.0.0.0/0 via: direct
# command: bind
#}
# if you don't route all local connections via direct, you should
# at least route nameserver connections via direct connections if you
# can. That can make for much better performance, depending on
# your setup. Make sure the nameserver line is the first.
#
# Assuming your nameserver runs on address 10.1.1.1, you can do it like this:
route {
from: 0.0.0.0/0 to: 202.116.64.2/32 port = domain via: direct
}
# have a route making all connections to loopback addresses be direct.
route {
from: 0.0.0.0/0 to: 127.0.0.0/8 via: direct
command: connect udpassociate # everything but bind, bind confuses us.
}
route {
from: 0.0.0.0/0 to: 192.168.0.0/16 via: direct
}
# clients going anywhere else go via server listening at
# IP address 10.1.1.1, port 1080. Note that unless you have
# specified a direct connection for DNS, or the socksserver is resolvable
# without network traffic, you can't give a hostname for the socksserver,
# you must give a IP address. (the reasons for that are logical enough,
# you would create a loop otherwise.)
route {
from: 0.0.0.0/0 to: 0.0.0.0/0 via: proxy2.zsu.edu.cn port = 1080
protocol: tcp udp # server supports tcp and udp.
proxyprotocol: socks_v5 # server supports socks v4 and v5.
method: none #username # we are willing to authenticate via
# method "none", not "username".
} |
|
IP卡
狗仔卡
楼主
显身卡