summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--opentracker.conf.sample70
1 files changed, 70 insertions, 0 deletions
diff --git a/opentracker.conf.sample b/opentracker.conf.sample
new file mode 100644
index 0000000..e034d23
--- /dev/null
+++ b/opentracker.conf.sample
@@ -0,0 +1,70 @@
1# opentracker config file
2#
3
4# I) Control directory where opentracker will chdir to. So all black/white
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)
12#
13# connect_tcp 0.0.0.0
14#
15# or specify them one by one (shell option -i 192.168.0.1 -p 6969)
16#
17# connect_tcp 192.168.0.1:6969
18# connect_tcp 192.168.0.2:6969
19# connect_tcp 192.168.0.3:6969
20
21# III) the same goes for udp connections (shell option -i 192.168.0.1 -P 6969)
22#
23# connect_udp 192.168.0.1:6969
24#
25# 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
27# source address that the requesting client may expect, but any address
28# on that interface
29#
30
31# IV) If opentracker runs in a non-open mode, point it to files containing
32# all torrent hashes that it will serve (shell option -w)
33#
34# whitelist_filename /path/to/whitelist
35#
36# or, if opentracker was compiled to allow blacklisting (shell option -b)
37#
38# blacklist_filename ./blacklist
39#
40# It is pointless and hence not possible to compile black AND white
41# listing, so choose one of those options. File format is straight
42# forward: "<hex info hash>\n<hex info hash>\n..."
43#
44
45# V) opentracker can be told to answer to a "GET / HTTP"-request with a
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
52# from perfect, the authors of opentracker trust in the correct
53# application of tunnels, filters and LAN setups (shell option -A)
54#
55# livesync_cluster_ip 192.168.0.4
56# livesync_cluster_ip 192.168.0.5
57# livesync_cluster_ip 192.168.0.6
58#
59# batchsync_cluster_ip 10.1.1.1
60#
61
62# VII) ip address to listen for outgoing and incoming live sync packets
63# (shell option -i 192.168.0.1 -s 9696)
64#
65# livesync_udp 192.168.0.1:9696
66#
67# 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
69# udp packets and one on ip address 192.168.0.1 port 9696 for outgoing
70# udp packets.