Tag: kad
Running Multiple p2p Behind Router
by admin on Aug.03, 2008, under Tips & Hints
As a full time internet leecher i’ve developed a way to avoid p2ps to conflicting with each other, since some p2p networks, like torrents and emule (kademila) don’t have clients with port range features the best way to avoid them to conflicting is putting ‘em behind a router and configure to work with UPnP.
Doing this will make you fall into another problem, with so many p2ps running you must have a lot of upstream, since this is not my case, i had to avoid one p2p to leech the whole upstream that would make the other p2ps slower or even making ‘em to crash, since the upstream was used to much that other programs don’t even have bandwidth to keep their connections alive with the network, so i had to cap ‘em.
Using netlimiter i was able to cap emule and torrents at 5k/s/each with left some bandwidth free for PD. Since PD can’t be capped (if you cap it’s upstream you probably gonna get knocked out the network) i left it with some priority — other p2ps are full of leechers so it don’t worth having so much upstream for them.
Now the port scheme:
Torrent: 40000 , port range: 25000-25250 (you don’t need many ports on torrents on your home connection, if you open too many your ISP will probably kill the new ports making internet unable to work for other things)
Kad/Emule: 4662/4672 (UDP), port range: 25251-25500 (i don’t recall for sure, but the listening ports, 4662 and 4672, were supposed to be the default ports for this p2p network when it started)
PD: 27848 – this is the most sensitive of the p2ps, since not everyone has a japan-like connection you should watch this closely, pd tends to open lots and lots of ports, like 500 even 1000, when it couldn’t get any bandwidth or any good nodes, so if you don’t priorize it’s bandwidth , it’s mostly like that it either will die or it will flood with ports, so to have a long duration connection with pd you shouldn’t cap it at all.
Regular FTP/HTTP Downloaders: if you run one of those too and you are able to configure it’s port range, try to make a new range for it and don’t use many multiple connections or it will take the whole bandwidth – best choise if having a downloader that is able to cap itself, like flashget that way you can balance the bandwidth well. FTPs will be aways a problem if you have an overloaded or super-port-flooded connection since they require much more communications to start the download than a simple HTTP request.
An note about netlimiter: This program seems to be incompatible with some types of NICs you shouldn’t notice the incompatibility at all when you install and run it, but once you start getting tcpip.sys BSOD you will go nuts — so i recommend the old version , 1.3, which instead of crashing windows, it crash itself, so you just need to run a timer on the program and it will be restarted once it crashes. (To run old netlimiter without poping it up, use: netlimiter.exe /s)