uTorrent auto load trackers

hello every1, apologies if this has been covered before.

is it possible to automatically add trackers to torrents in utorrent

the list of trackers in the site news section work a charm, but its a pain
having to copy and paste them in to new torrents

i have rss and it all set up on my eeepc so i can leave it running 24/7 so its
pretty much all automatic, except for adding additional trackers

if this is possible i would make my "auto" dl'ing even more automatic

cheers

xander

check the

ive had a bit of a look, even tried ol friend google, but no luck, was hoping
some1 has achieved this before

you only need to have the extra trackers loaded for one of your active
torrents for it to work.

the extra trackers won't be `hosting` a given torrent (i.e. they won't be
scraping it and supplying you peers with available parts directly) - all they
do is hook you up to the swarm `cloud` so that the clients can exchange dht
and peer exchange (pex) data directly. it's from within this distributed
cloud that other dht enabled clients that have info on the torrent hash you
desire are located.

part of the dht process is to announce *all* the torrent hashes a client has
available, therefore adding extra peer swarm details per torrent is
uneccessary.

question?


say with lost and the huge peer swarms it attracts, would it be advisable to
not add 20 odd trackers and turn dht off to avoid the huge amount of ip's
hitting the isp and router?

like i feel that even 1000 peers on a less popular tracker is enough, is it not?

thank you in advance...

no - still not advisable to turn it off. you are sort of missing the point -
it's exactly this sort of situation that dht is designed to be a solution
to. 😉

dht `search` traffic is minimal. all that's being sent back and forth is
which torrent hashes are available - not the complete announce of the
segment bitfield available from each client.

if your client has hit it's upper limit on connected peers and dht users then
any further incoming connection attempts are sent a curt `denied` response,
which takes up minimal resources.
with dht off you are entirely dependent on the central tracker to handle all
the inter-peer hook-ups. when it gets overloaded (as regularly happens with
lost et al) and denies your connection or simply doesn't respond then your
client is left twiddling it's thumbs and doing nothing worthwhile except
marking time before it speculatively hits up the tracker address again ... and
again and again. i.e. increasing the tracker load even more, and making a bad
situation worse.

the point about adding, for example, 20 trackers is closer to the mark. you
only need a few most times - just enough to be able to find one peer
that has a dht table containing info about the torrent you want. that one
peer will then `bootstrap` you into the cloud of dht peers it knows
about. once you have that foot in the door of the dht cloud then all the
other attempted connections to the other trackers in the list are just a waste
of your time and theirs.

ahhhh true.

i thought this much.

however i think with lost the tracker that comes with it is overly peered in
the first place to the point we are told to wait 24 hours or so. rather than
waiting, remove the original tracker and find a good 2 or 3 that are a lot less
robust and keep dht eneabled.

admin : you already opened a thread why post it here again?

indeed

i have had no trouble with a dynamic ip and have always used upnp and have
not turned off dhcp and never have to add trackers from the list and ut is
alway kermit and dht always has at least 270 nodes

and as if by magic, he appears in a puff of smoke ... 🙂

ok - looks like we are talking about a few different things at cross purposes
here.

1) the external world facing ip assigned to your router by your isp (fixed,
dynamic - doesn't matter either way)

2) the internal lan ip of your pc (static, or dynamic, assigned by dhcp from
router - again, doesn't matter which)

3) dht doesn't care about static or dynamic ips - it will work with either.
if you are on a fixed isp ip then the dht cloud already knows about you from
prior sessions and one of your previous dht contacts will eventually "ping"
you and bootstrap you back into the cloud.
if you are on dynamic then you have to go and find a dht cloud member yourself
when you start the torrent app - this is where the tracker bit comes in. as
long as you have *one* tracker that passes you the ip of *one* remote dht
enabled client then you can "announce" your dht availability and bootstrap
yourself into the dht cloud from that.

all we need to do on the lan side of things is make sure the router knows what
ip your pc is using, and that it knows to forward bittorrent traffic to it.

the actual methods for doing this on the router side of things will vary from
model to model but the easiest way is to enable upnp - in both your torrent
client and on your router (possibly in windows too if you have the ms firewall
running).
upnp is an "automatic" port-mapper. the upnp enabled application looks on
your network for the upnp router and asks it directly to open whatever open
ports it needs and to forward traffic arriving on those open ports back to
it's host pc. job done, and dht will just work[tm] 😉

if you don't have or can't use upnp then you'll have to do the port opening
and forwarding on your router manually.
i'm guessing this is where a lot of the confusion arises - on most router
configs when you add a port forwarding rule you have to (rather obviously)
tell it where to forward the torrent traffic *to*.
some routers will have an option to forward to a host name rather than ip
which gets around the issue, but this is uncommon.
if your pc is given a dhcp dynamic ip then it may not necessarily be the one
the forwarding rule points to. this is easily remedied by making sure the pc
always gets assigned the same ip as the one mentioned in the router forward
rule.


the above verbiage is probably making the issue seem more complicated than
it really is. all we really need to do is follow down the chain of logic ...
is the world facing isp ip on the router reachable by torrent traffic
[yes/no] - does the router have forwarding rules in place to know where on
the lan to send that traffic on to [yes/no] - is the torrent pc on the
right lan ip address to be the recipient of that forwarded traffic [yes/no]
.


in summary - if you can't use upnp then just remember to make
sure the router port forwarding destination is pointing at whatever ip your
torrent pc is currently using.

did all that make any sort of useful sense to you ? 😉

whoa my thread got hijacked!!!! haha

the general consensus seams to be that my original request to automatically load
tracks cannot be done

thats a shame....

i put it out there for some1 to write a plugin for me!! haha