summaryrefslogtreecommitdiff
path: root/opentracker.conf.sample
diff options
context:
space:
mode:
authorerdgeist <>2008-10-03 18:30:28 +0000
committererdgeist <>2008-10-03 18:30:28 +0000
commitcee13cbebb6cb47b0f4c09106e19e07d0c851d04 (patch)
treeaae64ef1390c4522ca42d167a120332f44b483fb /opentracker.conf.sample
parentfb50f0fadea918f4f707565335747e3f860d2d67 (diff)
Refine config syntax. Testing code...
Diffstat (limited to 'opentracker.conf.sample')
-rw-r--r--opentracker.conf.sample56
1 files changed, 28 insertions, 28 deletions
diff --git a/opentracker.conf.sample b/opentracker.conf.sample
index e034d23..d1fc5fb 100644
--- a/opentracker.conf.sample
+++ b/opentracker.conf.sample
@@ -1,26 +1,20 @@
1# opentracker config file 1# opentracker config file
2# 2#
3 3
4# I) Control directory where opentracker will chdir to. So all black/white 4# I) ip addresses for tcp connections, either bind to INADDR_ANY port 6969
5# list files may be put in that directory. (shell option -d)
6#
7# root_dir /usr/local/etc/opentracker
8#
9
10# II) ip addresses for tcp connections, either bind to INADDR_ANY port 6969
11# (when no shell option is present) 5# (when no shell option is present)
12# 6#
13# connect_tcp 0.0.0.0 7# listen.tcp 0.0.0.0
14# 8#
15# or specify them one by one (shell option -i 192.168.0.1 -p 6969) 9# or specify them one by one (shell option -i 192.168.0.1 -p 6969)
16# 10#
17# connect_tcp 192.168.0.1:6969 11# listen.tcp 192.168.0.1:6969
18# connect_tcp 192.168.0.2:6969 12# listen.tcp 192.168.0.2:6969
19# connect_tcp 192.168.0.3:6969 13# listen.tcp 192.168.0.3:6969
20 14
21# III) the same goes for udp connections (shell option -i 192.168.0.1 -P 6969) 15# II) the same goes for udp connections (shell option -i 192.168.0.1 -P 6969)
22# 16#
23# connect_udp 192.168.0.1:6969 17# listen.udp 192.168.0.1:6969
24# 18#
25# Note, that using 0.0.0.0 for udp sockets may yield surprising results. 19# Note, that using 0.0.0.0 for udp sockets may yield surprising results.
26# An answer packet sent on that socket will not necessarily have the 20# An answer packet sent on that socket will not necessarily have the
@@ -28,43 +22,49 @@
28# on that interface 22# on that interface
29# 23#
30 24
31# IV) If opentracker runs in a non-open mode, point it to files containing 25# III) If opentracker runs in a non-open mode, point it to files containing
32# all torrent hashes that it will serve (shell option -w) 26# all torrent hashes that it will serve (shell option -w)
33# 27#
34# whitelist_filename /path/to/whitelist 28# access.whitelist /path/to/whitelist
35# 29#
36# or, if opentracker was compiled to allow blacklisting (shell option -b) 30# or, if opentracker was compiled to allow blacklisting (shell option -b)
37# 31#
38# blacklist_filename ./blacklist 32# access.blacklist ./blacklist
39# 33#
40# It is pointless and hence not possible to compile black AND white 34# It is pointless and hence not possible to compile black AND white
41# listing, so choose one of those options. File format is straight 35# listing, so choose one of those options. File format is straight
42# forward: "<hex info hash>\n<hex info hash>\n..." 36# forward: "<hex info hash>\n<hex info hash>\n..."
43# 37#
44 38
45# V) opentracker can be told to answer to a "GET / HTTP"-request with a 39# IV) Sync between trackers running in a cluster is restricted to packets
46# redirect to another location (shell option -r)
47#
48# redirect_url https://project.tracker.local/
49
50# VI) Sync between trackers running in a cluster is restricted to packets
51# coming from trusted ip addresses. While source ip verification is far 40# coming from trusted ip addresses. While source ip verification is far
52# from perfect, the authors of opentracker trust in the correct 41# from perfect, the authors of opentracker trust in the correct
53# application of tunnels, filters and LAN setups (shell option -A) 42# application of tunnels, filters and LAN setups (shell option -A)
54# 43#
55# livesync_cluster_ip 192.168.0.4 44# livesync.cluster.node_ip 192.168.0.4
56# livesync_cluster_ip 192.168.0.5 45# livesync.cluster.node_ip 192.168.0.5
57# livesync_cluster_ip 192.168.0.6 46# livesync.cluster.node_ip 192.168.0.6
58# 47#
59# batchsync_cluster_ip 10.1.1.1 48# batchsync.cluster.admin_ip 10.1.1.1
60# 49#
61 50
62# VII) ip address to listen for outgoing and incoming live sync packets 51# V) ip address to listen for outgoing and incoming live sync packets
63# (shell option -i 192.168.0.1 -s 9696) 52# (shell option -i 192.168.0.1 -s 9696)
64# 53#
65# livesync_udp 192.168.0.1:9696 54# livesync.cluster.listen 192.168.0.1:9696
66# 55#
67# Note that two udp sockets will be opened. One on ip address 0.0.0.0 56# Note that two udp sockets will be opened. One on ip address 0.0.0.0
68# port 9696, that will join the multicast group 224.23.42.1 for incoming 57# port 9696, that will join the multicast group 224.23.42.1 for incoming
69# udp packets and one on ip address 192.168.0.1 port 9696 for outgoing 58# udp packets and one on ip address 192.168.0.1 port 9696 for outgoing
70# udp packets. 59# udp packets.
60
61# VI) Control directory where opentracker will chdir to. So all black/white
62# list files may be put in that directory. (shell option -d)
63#
64# tracker.rootdir /usr/local/etc/opentracker
65#
66
67# VII) opentracker can be told to answer to a "GET / HTTP"-request with a
68# redirect to another location (shell option -r)
69#
70# tracker.redirect_url https://your.tracker.local/