|
| 1 | +# opentracker config file |
| 2 | +# |
| 3 | + |
| 4 | +# I) Address opentracker will listen on, using both, tcp AND udp family |
| 5 | +# (note, that port 6969 is implicite if ommitted). |
| 6 | +# |
| 7 | +# If no listen option is given (here or on the command line), opentracker |
| 8 | +# listens on 0.0.0.0:6969 tcp and udp. |
| 9 | +# |
| 10 | +# The next variable determines if udp sockets are handled in the event |
| 11 | +# loop (set it to 0, the default) or are handled in blocking reads in |
| 12 | +# dedicated worker threads. You have to set this value before the |
| 13 | +# listen.tcp_udp or listen.udp statements before it takes effect, but you |
| 14 | +# can re-set it for each listen statement. Normally you should keep it at |
| 15 | +# the top of the config file. |
| 16 | +# |
| 17 | +# listen.udp.workers 4 |
| 18 | +# |
| 19 | +# listen.tcp_udp 0.0.0.0 |
| 20 | +# listen.tcp_udp 192.168.0.1:80 |
| 21 | +# listen.tcp_udp 10.0.0.5:6969 |
| 22 | +# |
| 23 | +# To only listen on tcp or udp family ports, list them this way: |
| 24 | +# |
| 25 | +# listen.tcp 0.0.0.0 |
| 26 | +# listen.udp 192.168.0.1:6969 |
| 27 | +# |
| 28 | +# Note, that using 0.0.0.0 for udp sockets may yield surprising results. |
| 29 | +# An answer packet sent on that socket will not necessarily have the |
| 30 | +# source address that the requesting client may expect, but any address |
| 31 | +# on that interface. |
| 32 | +# |
| 33 | + |
| 34 | +# II) If opentracker runs in a non-open mode, point it to files containing |
| 35 | +# all torrent hashes that it will serve (shell option -w) |
| 36 | +# |
| 37 | +# access.whitelist /path/to/whitelist |
| 38 | +# |
| 39 | +# or, if opentracker was compiled to allow blacklisting (shell option -b) |
| 40 | +# |
| 41 | +# access.blacklist ./blacklist |
| 42 | +# |
| 43 | +# It is pointless and hence not possible to compile black AND white |
| 44 | +# listing, so choose one of those options at compile time. File format |
| 45 | +# is straight forward: "<hex info hash>\n<hex info hash>\n..." |
| 46 | +# |
| 47 | +# If you do not want to grant anyone access to your stats, enable the |
| 48 | +# WANT_RESTRICT_STATS option in Makefile and bless the ip addresses |
| 49 | +# allowed to fetch stats here. |
| 50 | +# |
| 51 | +# access.stats 192.168.0.23 |
| 52 | +# |
| 53 | +# There is another way of hiding your stats. You can obfuscate the path |
| 54 | +# to them. Normally it is located at /stats but you can configure it to |
| 55 | +# appear anywhere on your tracker. |
| 56 | +# |
| 57 | +# access.stats_path stats |
| 58 | + |
| 59 | +# III) Live sync uses udp multicast packets to keep a cluster of opentrackers |
| 60 | +# synchronized. This option tells opentracker which port to listen for |
| 61 | +# incoming live sync packets. The ip address tells opentracker, on which |
| 62 | +# interface to join the multicast group, those packets will arrive. |
| 63 | +# (shell option -i 192.168.0.1 -s 9696), port 9696 is default. |
| 64 | +# |
| 65 | +# livesync.cluster.listen 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.0.42.23 for incoming |
| 69 | +# udp packets and one on ip address 192.168.0.1 port 9696 for outgoing |
| 70 | +# udp packets. |
| 71 | +# |
| 72 | +# As of now one and only one ip address must be given, if opentracker |
| 73 | +# was built with the WANT_SYNC_LIVE feature. |
| 74 | +# |
| 75 | + |
| 76 | +# IV) Sync between trackers running in a cluster is restricted to packets |
| 77 | +# coming from trusted ip addresses. While source ip verification is far |
| 78 | +# from perfect, the authors of opentracker trust in the correct |
| 79 | +# application of tunnels, filters and LAN setups (shell option -A). |
| 80 | +# |
| 81 | +# livesync.cluster.node_ip 192.168.0.4 |
| 82 | +# livesync.cluster.node_ip 192.168.0.5 |
| 83 | +# livesync.cluster.node_ip 192.168.0.6 |
| 84 | +# |
| 85 | +# This is the admin ip address for old style (HTTP based) asynchronus |
| 86 | +# tracker syncing. |
| 87 | +# |
| 88 | +# batchsync.cluster.admin_ip 10.1.1.1 |
| 89 | +# |
| 90 | + |
| 91 | +# V) Control privilege drop behaviour. |
| 92 | +# Put in the directory opentracker will chroot/chdir to. All black/white |
| 93 | +# list files must be put in that directory (shell option -d). |
| 94 | +# |
| 95 | +# |
| 96 | +# tracker.rootdir /usr/local/etc/opentracker |
| 97 | +# |
| 98 | +# Tell opentracker which user to setuid to. |
| 99 | +# |
| 100 | +# tracker.user nobody |
| 101 | +# |
| 102 | + |
| 103 | +# VI) opentracker can be told to answer to a "GET / HTTP"-request with a |
| 104 | +# redirect to another location (shell option -r). |
| 105 | +# |
| 106 | +# tracker.redirect_url https://your.tracker.local/ |
0 commit comments