Sziasztok valaki le tudja írni hogyan is kel be üzemelni a torrent patcher vps re?
Erről lenne szó (http://www.elitepvpers.com/forum/metin2-pserver-guides-strategies/2670173-howto-full-original-patcher-work-100-a.html)
vps en fent van hozzá való µTorrent is van amivel meg tudom csinálni amit kel de nem tudom hogy pontosan tracker részbe mit is lenne jó meg adni mikkor elkészítem a torrentet (u torrentel)
aki jártas benne az ki tudna segíteni? ja és + jól jöne egy exe is hozzá mert az már nincs csatolva e pvp-n
Bármilyen open trackert beírhatsz oda, vagy csinálhatsz sajátot is ( /usr/ports/net/opentracker ).
ATAG nem tudod le írni hogy pontosan hogyan kel az egészet meg csinálni? meg persze a patcher részét is.
Az eredeti témában minden le van írva. Módosítod a TorrentPAtch.url nevű fájlt, beleírod a saját elérésed, a példában: patch.mrlibya.com/metin2torrent.config.xml
a metin2torrent.config.xml tartalma pedig (ez a régi dd-s, tehát tuti működik):
<torrent_config
port_range="6881~6891"
bandwidth_range="5:10:25:50:75:100:150:200:250:500:1000"
foreground_speed="0"
background_speed="10"
run_path="metin2client.bin"
max_uploads_per_session="16"
max_connections_per_session="100"
max_uploads_per_torrent="4"
max_connections_per_torrent="75"
seeding_duration="21600">
<foreground_patch torrent_url="http://ddmt2.net/patch/torrent/ddmt2_hu_common_8.torrent" />
<background_patch torrent_url="http://ddmt2.net/patch/torrent/ddmt2_hu_common_8.torrent" />
</torrent_config>
A torrent fájl meg értelemszerűen amit csináltál a patchről/kliensről pl uTorrenttel (bármilyen open trackerrel)
Naponta frissülő open tracker lista:
https://raw.githubusercontent.com/ngosang/trackerslist/master/trackers_all.txt
Ezek közül a top20:
https://raw.githubusercontent.com/ngosang/trackerslist/master/trackers_best.txt
úgy akarom az egészet hogy saját szerver seedeli amit kel tehát saját trackerel
Telepítsd az opentracker nevű okosságot (benne van portsban) aztán beállítod és kész :D
Nálam ez volt az opentracker.conf (/usr/local/etc/opentracker.conf):
[spoiler]# opentracker config file
#
# I) Address opentracker will listen on, using both, tcp AND udp family
# (note, that port 6969 is implicite if ommitted).
#
# If no listen option is given (here or on the command line), opentracker
# listens on 0.0.0.0:6969 tcp and udp.
#
# listen.tcp_udp 0.0.0.0
# listen.tcp_udp 192.168.0.1:80
# listen.tcp_udp 10.0.0.5:6969
#
# To only listen on tcp or udp family ports, list them this way:
#
# listen.tcp 0.0.0.0
# listen.udp 192.168.0.1:6969
#
# Note, that using 0.0.0.0 for udp sockets may yield surprising results.
# An answer packet sent on that socket will not necessarily have the
# source address that the requesting client may expect, but any address
# on that interface.
#
# II) If opentracker runs in a non-open mode, point it to files containing
# all torrent hashes that it will serve (shell option -w)
#
access.whitelist /home/atag/.opentr_whitelist
#
# or, if opentracker was compiled to allow blacklisting (shell option -b)
#
# access.blacklist ./blacklist
#
# It is pointless and hence not possible to compile black AND white
# listing, so choose one of those options at compile time. File format
# is straight forward: "<hex info hash>\n<hex info hash>\n..."
#
# If you do not want to grant anyone access to your stats, enable the
# WANT_RESTRICT_STATS option in Makefile and bless the ip addresses
# allowed to fetch stats here.
#
access.stats 78.24.185.25
#
# There is another way of hiding your stats. You can obfuscate the path
# to them. Normally it is located at /stats but you can configure it to
# appear anywhere on your tracker.
#
# access.stats_path stats
# III) Live sync uses udp multicast packets to keep a cluster of opentrackers
# synchronized. This option tells opentracker which port to listen for
# incoming live sync packets. The ip address tells opentracker, on which
# interface to join the multicast group, those packets will arrive.
# (shell option -i 192.168.0.1 -s 9696), port 9696 is default.
#
# livesync.cluster.listen 192.168.0.1:9696
#
# Note that two udp sockets will be opened. One on ip address 0.0.0.0
# port 9696, that will join the multicast group 224.0.42.23 for incoming
# udp packets and one on ip address 192.168.0.1 port 9696 for outgoing
# udp packets.
#
# As of now one and only one ip address must be given, if opentracker
# was built with the WANT_SYNC_LIVE feature.
#
# IV) Sync between trackers running in a cluster is restricted to packets
# coming from trusted ip addresses. While source ip verification is far
# from perfect, the authors of opentracker trust in the correct
# application of tunnels, filters and LAN setups (shell option -A).
#
# livesync.cluster.node_ip 192.168.0.4
# livesync.cluster.node_ip 192.168.0.5
# livesync.cluster.node_ip 192.168.0.6
#
# This is the admin ip address for old style (HTTP based) asynchronus
# tracker syncing.
#
# batchsync.cluster.admin_ip 10.1.1.1
#
# V) Control privilege drop behaviour.
# Put in the directory opentracker will chroot/chdir to. All black/white
# list files must be put in that directory (shell option -d).
#
#
# tracker.rootdir /usr/local/etc/opentracker
#
# Tell opentracker which user to setuid to.
#
# tracker.user nobody
#
# VI) opentracker can be told to answer to a "GET / HTTP"-request with a
# redirect to another location (shell option -r).
#
# tracker.redirect_url https://your.tracker.local/ [/spoiler]
a .opentr_whitelist pedig az engedélyezett torrentek info hashét kell csak hogy tartalmazza, pl:
[spoiler]77BDBFB4D2C21D02CEB184AE863BE80AA51AA026
31B4485E7365BF099DD87DA1A1A9943AC88D6C0D
180EE3EFAC9FEED4EC24ACEC77D03752F455F70C
89c741a262bd1db0b0391d0193f2d78c2b671770
86e18092f46e283b2a9f67d9221e6179e348c006[/spoiler]
Így más torrenteket el fog utasítani a tracker :)
Meg nézem ATAG uraság :) majd írok hogy mi a helyzet vele
Miért akarsz torrentet használni?
Idézetet írta: ATAG Dátum 2017-03-17, 14:29:47
Telepítsd az opentracker nevű okosságot (benne van portsban) aztán beállítod és kész :D
Nálam ez volt az opentracker.conf (/usr/local/etc/opentracker.conf):
[spoiler]# opentracker config file
#
# I) Address opentracker will listen on, using both, tcp AND udp family
# (note, that port 6969 is implicite if ommitted).
#
# If no listen option is given (here or on the command line), opentracker
# listens on 0.0.0.0:6969 tcp and udp.
#
# listen.tcp_udp 0.0.0.0
# listen.tcp_udp 192.168.0.1:80
# listen.tcp_udp 10.0.0.5:6969
#
# To only listen on tcp or udp family ports, list them this way:
#
# listen.tcp 0.0.0.0
# listen.udp 192.168.0.1:6969
#
# Note, that using 0.0.0.0 for udp sockets may yield surprising results.
# An answer packet sent on that socket will not necessarily have the
# source address that the requesting client may expect, but any address
# on that interface.
#
# II) If opentracker runs in a non-open mode, point it to files containing
# all torrent hashes that it will serve (shell option -w)
#
access.whitelist /home/atag/.opentr_whitelist
#
# or, if opentracker was compiled to allow blacklisting (shell option -b)
#
# access.blacklist ./blacklist
#
# It is pointless and hence not possible to compile black AND white
# listing, so choose one of those options at compile time. File format
# is straight forward: "<hex info hash>\n<hex info hash>\n..."
#
# If you do not want to grant anyone access to your stats, enable the
# WANT_RESTRICT_STATS option in Makefile and bless the ip addresses
# allowed to fetch stats here.
#
access.stats 78.24.185.25
#
# There is another way of hiding your stats. You can obfuscate the path
# to them. Normally it is located at /stats but you can configure it to
# appear anywhere on your tracker.
#
# access.stats_path stats
# III) Live sync uses udp multicast packets to keep a cluster of opentrackers
# synchronized. This option tells opentracker which port to listen for
# incoming live sync packets. The ip address tells opentracker, on which
# interface to join the multicast group, those packets will arrive.
# (shell option -i 192.168.0.1 -s 9696), port 9696 is default.
#
# livesync.cluster.listen 192.168.0.1:9696
#
# Note that two udp sockets will be opened. One on ip address 0.0.0.0
# port 9696, that will join the multicast group 224.0.42.23 for incoming
# udp packets and one on ip address 192.168.0.1 port 9696 for outgoing
# udp packets.
#
# As of now one and only one ip address must be given, if opentracker
# was built with the WANT_SYNC_LIVE feature.
#
# IV) Sync between trackers running in a cluster is restricted to packets
# coming from trusted ip addresses. While source ip verification is far
# from perfect, the authors of opentracker trust in the correct
# application of tunnels, filters and LAN setups (shell option -A).
#
# livesync.cluster.node_ip 192.168.0.4
# livesync.cluster.node_ip 192.168.0.5
# livesync.cluster.node_ip 192.168.0.6
#
# This is the admin ip address for old style (HTTP based) asynchronus
# tracker syncing.
#
# batchsync.cluster.admin_ip 10.1.1.1
#
# V) Control privilege drop behaviour.
# Put in the directory opentracker will chroot/chdir to. All black/white
# list files must be put in that directory (shell option -d).
#
#
# tracker.rootdir /usr/local/etc/opentracker
#
# Tell opentracker which user to setuid to.
#
# tracker.user nobody
#
# VI) opentracker can be told to answer to a "GET / HTTP"-request with a
# redirect to another location (shell option -r).
#
# tracker.redirect_url https://your.tracker.local/ [/spoiler]
a .opentr_whitelist pedig az engedélyezett torrentek info hashét kell csak hogy tartalmazza, pl:
[spoiler]77BDBFB4D2C21D02CEB184AE863BE80AA51AA026
31B4485E7365BF099DD87DA1A1A9943AC88D6C0D
180EE3EFAC9FEED4EC24ACEC77D03752F455F70C
89c741a262bd1db0b0391d0193f2d78c2b671770
86e18092f46e283b2a9f67d9221e6179e348c006[/spoiler]
Így más torrenteket el fog utasítani a tracker :)
ATAG eszt le tudod írni hogy csináljam meg jól? mert lassan kelleni fog :) 11 BSD van fent
nem tudnátok esetleg le írni lépeseket? mert még az exe sincs meg amit ír
1.Open metin2.bin in 7-zip Then You Will Have 26 file
2.open TorrentPatch.locale In Notepad++ (line: 22+23)
3.open TorrentPatch.url in Notepad++ Make You Patch URL
saját gépen lenen egyenlőre teszt céljából
Ha nem torrentes patchert akarsz akkor írj PM-et.