FYI - if you want super fast torrents

[tp4tissue]

Forward ports 10000 through 65000...

no need to limit it to the single listening port specified in the client

This won't help your upload speed it seems, because that would rely on "other people" forwarding the same range

I didn't do this till today, it doubled my torrent speeds.

UPDATE:

According to network expert LssAnn, it's a bad idea... IDK why it makes my torrents faster, but it did. @ your own risk I guess.

[Tym]

But double 0.1kb/s is like 0.2kb/s

[daerid]

omgz torrents!!11

[tp4tissue]

omgz torrents!!11

just saying... I kept wondering why i couldn't connect to "some people" even on private trackers, well now i know..

[SpAmRaY]

But double 0.1kb/s is like 0.2kb/s

I feel you bro.

[MKULTRA]

Can this lead to any network vulnerabilities?

[tp4tissue]

Can this lead to any network vulnerabilities?

no. you're still behind the firewall. and it knows the difference between an attack and a torrent connection.

[webs0r]

Even with the firewall it doesn't make sense to take this approach - I'll explain...

Your torrent client makes connections to peers (outbound) and accepts connections (inbound) from peers.
The client should allow you to specify the port to which it listens for inbound connections.
It should register this port with your NAT router using UPNP so that your router knows to forward connections to your LAN IP from the internet.
This effectively achieves the port forward without you having to configure anything.

It won't accept inbound connections from multiple ports, simply as the torrent tracker will advertise your client with the inbound port you specify. They won't connect to anything else, and your client isn't listening on other ports. If you run a netstat -a you'll see the inbound connections all hooked up to the one port. You will have outbound connections on various ports, but those are the connections your computer has originated, a different matter.

If, for whatever reason, UPNP is disabled, or your client doesn't use UPNP, then port forwarding will help.
Also some clients have a "random" inbound port setting - you might need to be aware of this. If UPNP is working, this is fine. Otherwise, specify a port.
Also ensure your software firewall is allowing inbound traffic to your torrent client.

I don't recommend setting a huge port range forward for security reasons, especially when there is no gain.

On the "firewall will catch other stuff" that's not entirely true; e.g. there are windows services that will accept traffic on your LAN i.e. the firewall is open for these services and your computer will do stuff with that traffic. WAN traffic will be blocked by your router, but if you forward everything through.. up to you... for no gain..

[Photekq]

Better solution : get a seedbox.

[turtle]

Seed box?

[MKULTRA]

Seed box?

http://en.wikipedia.org/wiki/Seedbox

[pasph]

Direct downloads FTW

[tp4tissue]

Even with the firewall it doesn't make sense to take this approach - I'll explain...

Your torrent client makes connections to peers (outbound) and accepts connections (inbound) from peers.
The client should allow you to specify the port to which it listens for inbound connections.
It should register this port with your NAT router using UPNP so that your router knows to forward connections to your LAN IP from the internet.
This effectively achieves the port forward without you having to configure anything.

It won't accept inbound connections from multiple ports, simply as the torrent tracker will advertise your client with the inbound port you specify. They won't connect to anything else, and your client isn't listening on other ports. If you run a netstat -a you'll see the inbound connections all hooked up to the one port. You will have outbound connections on various ports, but those are the connections your computer has originated, a different matter.

If, for whatever reason, UPNP is disabled, or your client doesn't use UPNP, then port forwarding will help.
Also some clients have a "random" inbound port setting - you might need to be aware of this. If UPNP is working, this is fine. Otherwise, specify a port.
Also ensure your software firewall is allowing inbound traffic to your torrent client.

I don't recommend setting a huge port range forward for security reasons, especially when there is no gain.

On the "firewall will catch other stuff" that's not entirely true; e.g. there are windows services that will accept traffic on your LAN i.e. the firewall is open for these services and your computer will do stuff with that traffic. WAN traffic will be blocked by your router, but if you forward everything through.. up to you... for no gain..

Upnp and Natpmp are way less secure than manual port forwarding, because they can be exploited to do OTHER THINGS.

You're safer just manually forwarding 10000 to 65000

[eth0s]

Even with the firewall it doesn't make sense to take this approach - I'll explain...

Your torrent client makes connections to peers (outbound) and accepts connections (inbound) from peers.
The client should allow you to specify the port to which it listens for inbound connections.
It should register this port with your NAT router using UPNP so that your router knows to forward connections to your LAN IP from the internet.
This effectively achieves the port forward without you having to configure anything.

It won't accept inbound connections from multiple ports, simply as the torrent tracker will advertise your client with the inbound port you specify. They won't connect to anything else, and your client isn't listening on other ports. If you run a netstat -a you'll see the inbound connections all hooked up to the one port. You will have outbound connections on various ports, but those are the connections your computer has originated, a different matter.

If, for whatever reason, UPNP is disabled, or your client doesn't use UPNP, then port forwarding will help.
Also some clients have a "random" inbound port setting - you might need to be aware of this. If UPNP is working, this is fine. Otherwise, specify a port.
Also ensure your software firewall is allowing inbound traffic to your torrent client.

I don't recommend setting a huge port range forward for security reasons, especially when there is no gain.

On the "firewall will catch other stuff" that's not entirely true; e.g. there are windows services that will accept traffic on your LAN i.e. the firewall is open for these services and your computer will do stuff with that traffic. WAN traffic will be blocked by your router, but if you forward everything through.. up to you... for no gain..

Upnp and Natpmp are way more insecure than manual port forwarding, because they can be exploited to do OTHER THINGS.

You're safer just manually forwarding 10000 to 65000

I just hope your parents don't get sued for copyright infringement.  The usual judgment after being sued is around $150K.  Check it out here: http://torrentfreak.com/200000-bittorrent-users-sued-in-the-united-states-110808/.  But then again, who worries about a $150K fine?

[tp4tissue]

Even with the firewall it doesn't make sense to take this approach - I'll explain...

Your torrent client makes connections to peers (outbound) and accepts connections (inbound) from peers.
The client should allow you to specify the port to which it listens for inbound connections.
It should register this port with your NAT router using UPNP so that your router knows to forward connections to your LAN IP from the internet.
This effectively achieves the port forward without you having to configure anything.

It won't accept inbound connections from multiple ports, simply as the torrent tracker will advertise your client with the inbound port you specify. They won't connect to anything else, and your client isn't listening on other ports. If you run a netstat -a you'll see the inbound connections all hooked up to the one port. You will have outbound connections on various ports, but those are the connections your computer has originated, a different matter.

If, for whatever reason, UPNP is disabled, or your client doesn't use UPNP, then port forwarding will help.
Also some clients have a "random" inbound port setting - you might need to be aware of this. If UPNP is working, this is fine. Otherwise, specify a port.
Also ensure your software firewall is allowing inbound traffic to your torrent client.

I don't recommend setting a huge port range forward for security reasons, especially when there is no gain.

On the "firewall will catch other stuff" that's not entirely true; e.g. there are windows services that will accept traffic on your LAN i.e. the firewall is open for these services and your computer will do stuff with that traffic. WAN traffic will be blocked by your router, but if you forward everything through.. up to you... for no gain..

Upnp and Natpmp are way more insecure than manual port forwarding, because they can be exploited to do OTHER THINGS.

You're safer just manually forwarding 10000 to 65000

I just hope your parents don't get sued for copyright infringement.  The usual judgment after being sued is around $150K.  Check it out here: http://torrentfreak.com/200000-bittorrent-users-sued-in-the-united-states-110808/.  But then again, who worries about a $150K fine?

achem... private trackers

[Photekq]

achem... private trackers

Show Image

Using private trackers won't save you unless you're using a seedbox.

Seriously people GET A SEEDBOX, download with SFTP.

[eth0s]

Even with the firewall it doesn't make sense to take this approach - I'll explain...

Your torrent client makes connections to peers (outbound) and accepts connections (inbound) from peers.
The client should allow you to specify the port to which it listens for inbound connections.
It should register this port with your NAT router using UPNP so that your router knows to forward connections to your LAN IP from the internet.
This effectively achieves the port forward without you having to configure anything.

It won't accept inbound connections from multiple ports, simply as the torrent tracker will advertise your client with the inbound port you specify. They won't connect to anything else, and your client isn't listening on other ports. If you run a netstat -a you'll see the inbound connections all hooked up to the one port. You will have outbound connections on various ports, but those are the connections your computer has originated, a different matter.

If, for whatever reason, UPNP is disabled, or your client doesn't use UPNP, then port forwarding will help.
Also some clients have a "random" inbound port setting - you might need to be aware of this. If UPNP is working, this is fine. Otherwise, specify a port.
Also ensure your software firewall is allowing inbound traffic to your torrent client.

I don't recommend setting a huge port range forward for security reasons, especially when there is no gain.

On the "firewall will catch other stuff" that's not entirely true; e.g. there are windows services that will accept traffic on your LAN i.e. the firewall is open for these services and your computer will do stuff with that traffic. WAN traffic will be blocked by your router, but if you forward everything through.. up to you... for no gain..

Upnp and Natpmp are way more insecure than manual port forwarding, because they can be exploited to do OTHER THINGS.

You're safer just manually forwarding 10000 to 65000

I just hope your parents don't get sued for copyright infringement.  The usual judgment after being sued is around $150K.  Check it out here: http://torrentfreak.com/200000-bittorrent-users-sued-in-the-united-states-110808/.  But then again, who worries about a $150K fine?

achem... private trackers

Show Image

lol.  Okay, your parents are totally safe.  GL to them!

[tp4tissue]

achem... private trackers

Show Image

Using private trackers won't save you unless you're using a seedbox.

Seriously people GET A SEEDBOX, download with SFTP.

Nothing will SAVE you... should they decide to come down on you.

if you get a seed box for example.. they can track your payments to it..

Even if you go through the trouble to pay by anon methods like bitcoins or visa or over tor, that's not safe either, because they can easily pay a hacker to find you..

And that evidence that they pay a hacker for works the same way as the kind gained from a private detective..


It comes down to how bad they want to make an example of you.

[tp4tissue]

Even with the firewall it doesn't make sense to take this approach - I'll explain...

Your torrent client makes connections to peers (outbound) and accepts connections (inbound) from peers.
The client should allow you to specify the port to which it listens for inbound connections.
It should register this port with your NAT router using UPNP so that your router knows to forward connections to your LAN IP from the internet.
This effectively achieves the port forward without you having to configure anything.

It won't accept inbound connections from multiple ports, simply as the torrent tracker will advertise your client with the inbound port you specify. They won't connect to anything else, and your client isn't listening on other ports. If you run a netstat -a you'll see the inbound connections all hooked up to the one port. You will have outbound connections on various ports, but those are the connections your computer has originated, a different matter.

If, for whatever reason, UPNP is disabled, or your client doesn't use UPNP, then port forwarding will help.
Also some clients have a "random" inbound port setting - you might need to be aware of this. If UPNP is working, this is fine. Otherwise, specify a port.
Also ensure your software firewall is allowing inbound traffic to your torrent client.

I don't recommend setting a huge port range forward for security reasons, especially when there is no gain.

On the "firewall will catch other stuff" that's not entirely true; e.g. there are windows services that will accept traffic on your LAN i.e. the firewall is open for these services and your computer will do stuff with that traffic. WAN traffic will be blocked by your router, but if you forward everything through.. up to you... for no gain..

Upnp and Natpmp are way more insecure than manual port forwarding, because they can be exploited to do OTHER THINGS.

You're safer just manually forwarding 10000 to 65000

I just hope your parents don't get sued for copyright infringement.  The usual judgment after being sued is around $150K.  Check it out here: http://torrentfreak.com/200000-bittorrent-users-sued-in-the-united-states-110808/.  But then again, who worries about a $150K fine?

achem... private trackers

Show Image

lol.  Okay, your parents are totally safe.  GL to them!

what are you talking about?

[microsoft windows]

I AM TALKING ABOUT WINDOWS 3.1. DO YOU HAVE A COPY?

[tp4tissue]

I AM TALKING ABOUT WINDOWS 3.1. DO YOU HAVE A COPY?

YES.. on my Epson 75mhz pentium.  I've still got Megaman X installed on it and a controller using GAMEPORT

[microsoft windows]

Nice! You got that hooked up to the Internet?

[tp4tissue]

Nice! You got that hooked up to the Internet?

sadly no.. it only has dialup modem.  well idk does net zero still work?

[microsoft windows]

If you can find an older ethernet card, you could probably get that thing on high speed internet. Just about any ISA (and some PCI) ethernet card should work in Windows 3.1. Just gotta install the driver, TCP/IP, the Microsoft Networking add-on (if you don't have it), and MSIE5 and you'll be ready for business!

[eth0s]

Even with the firewall it doesn't make sense to take this approach - I'll explain...

Your torrent client makes connections to peers (outbound) and accepts connections (inbound) from peers.
The client should allow you to specify the port to which it listens for inbound connections.
It should register this port with your NAT router using UPNP so that your router knows to forward connections to your LAN IP from the internet.
This effectively achieves the port forward without you having to configure anything.

It won't accept inbound connections from multiple ports, simply as the torrent tracker will advertise your client with the inbound port you specify. They won't connect to anything else, and your client isn't listening on other ports. If you run a netstat -a you'll see the inbound connections all hooked up to the one port. You will have outbound connections on various ports, but those are the connections your computer has originated, a different matter.

If, for whatever reason, UPNP is disabled, or your client doesn't use UPNP, then port forwarding will help.
Also some clients have a "random" inbound port setting - you might need to be aware of this. If UPNP is working, this is fine. Otherwise, specify a port.
Also ensure your software firewall is allowing inbound traffic to your torrent client.

I don't recommend setting a huge port range forward for security reasons, especially when there is no gain.

On the "firewall will catch other stuff" that's not entirely true; e.g. there are windows services that will accept traffic on your LAN i.e. the firewall is open for these services and your computer will do stuff with that traffic. WAN traffic will be blocked by your router, but if you forward everything through.. up to you... for no gain..

Upnp and Natpmp are way more insecure than manual port forwarding, because they can be exploited to do OTHER THINGS.

You're safer just manually forwarding 10000 to 65000

I just hope your parents don't get sued for copyright infringement.  The usual judgment after being sued is around $150K.  Check it out here: http://torrentfreak.com/200000-bittorrent-users-sued-in-the-united-states-110808/.  But then again, who worries about a $150K fine?

achem... private trackers

Show Image

lol.  Okay, your parents are totally safe.  GL to them!

what are you talking about?

I'm talking about your parents.  You live with your parents.  Your parents pay for your internet connection.  When the owners of the copyrights come for you, ultimately it will be your parents who get sued, and not you.  So you have nothing to worry about.  But I am worried about your parents' retirement savings, and their house.  Unless your parents are rich, of course, in which case, I'm not worried at all since they will be able to pay for your copyright infringement with a certified bank check, wired in from their secret tax-avoidance account in Switzerland.   

[tp4tissue]

Even with the firewall it doesn't make sense to take this approach - I'll explain...

Your torrent client makes connections to peers (outbound) and accepts connections (inbound) from peers.
The client should allow you to specify the port to which it listens for inbound connections.
It should register this port with your NAT router using UPNP so that your router knows to forward connections to your LAN IP from the internet.
This effectively achieves the port forward without you having to configure anything.

It won't accept inbound connections from multiple ports, simply as the torrent tracker will advertise your client with the inbound port you specify. They won't connect to anything else, and your client isn't listening on other ports. If you run a netstat -a you'll see the inbound connections all hooked up to the one port. You will have outbound connections on various ports, but those are the connections your computer has originated, a different matter.

If, for whatever reason, UPNP is disabled, or your client doesn't use UPNP, then port forwarding will help.
Also some clients have a "random" inbound port setting - you might need to be aware of this. If UPNP is working, this is fine. Otherwise, specify a port.
Also ensure your software firewall is allowing inbound traffic to your torrent client.

I don't recommend setting a huge port range forward for security reasons, especially when there is no gain.

On the "firewall will catch other stuff" that's not entirely true; e.g. there are windows services that will accept traffic on your LAN i.e. the firewall is open for these services and your computer will do stuff with that traffic. WAN traffic will be blocked by your router, but if you forward everything through.. up to you... for no gain..

Upnp and Natpmp are way more insecure than manual port forwarding, because they can be exploited to do OTHER THINGS.

You're safer just manually forwarding 10000 to 65000

I just hope your parents don't get sued for copyright infringement.  The usual judgment after being sued is around $150K.  Check it out here: http://torrentfreak.com/200000-bittorrent-users-sued-in-the-united-states-110808/.  But then again, who worries about a $150K fine?

achem... private trackers

Show Image

lol.  Okay, your parents are totally safe.  GL to them!

what are you talking about?

I'm talking about your parents.  You live with your parents.  Your parents pay for your internet connection.  When the owners of the copyrights come for you, ultimately it will be your parents who get sued, and not you.  So you have nothing to worry about.  But I am worried about your parents' retirement savings, and their house.  Unless your parents are rich, of course, in which case, I'm not worried at all since they will be able to pay for your copyright infringement with a certified bank check, wired in from their secret tax-avoidance account in Switzerland.   

eth0s, ur either very young, or just ignant', the world doesn't work that way.

[microsoft windows]

C'mon guys...let's give this a break. We can talk about Windows 2000 instead!

[JPG]

C'mon guys...let's give this a break. We can talk about Windows 2000 instead!

Want to talk about Millenium? I pretty much always used Windows, but after buying Millenium, damn I swore I would never pay again for it. Took me 10 years to brake that vow.

[badcop]

i'm surprised no one has mentioned usenet yet.

[tp4tissue]

i'm surprised no one has mentioned usenet yet.

usenet's good, but the whole $10 a month thing. I'm not a billionaire

[webs0r]

Upnp and Natpmp are way less secure than manual port forwarding, because they can be exploited to do OTHER THINGS.

You're safer just manually forwarding 10000 to 65000

So a malicious application could use UPNP to forward a port ...  fine, but your solution is to turn UPNP off, but then port forward almost EVERYTHING.
Unfortunately then its the user that is the problem! 

Seriously, if you want, turn UPNP off, it's not relevant to my point. But manually port forward the 1 port your torrent client needs. That's my point. Forwarding all ports is pointless because your torrent client is not listening to them.

i'm surprised no one has mentioned usenet yet.

First rule of fight club 

[IvanIvanovich]

Best thing to get fast torrent is to only one at a time and set max peers per torrent to something like 500. Of course it still depend on seeder upload speed, so if it isn't being utilized bandwidth because slow upload start other torrent. Most time I can max out my connection speed of 15mbps on single torrent and get it done as fast as is possible for my connection speed. BT only needs one port connect, as long as it can connect though you are good. Opening a bunch of ports don't help anything. Having more half open connections allowed does though.

[Leslieann]

Port forwarding... You just punched a huge hole in your HARDWARE firewall, and directed traffic to a SOFTWARE firewall. FAIL
Private torrents... Because obviously it's impossible for people with billions to get invited.  FAIL

Private torrent sites have been compromised many times. You want as many ports on your firewall closed as much as possible, and a hardware firewall does this far more securely than a software firewall. Far, far more securely when you take into considering that you are using that computer. Get one little trojan and your software firewall is worthless. Not to mention odds are that you are relying on Windows firewall, which in itself is almost useless. Xp's original firewall only worked in one direction even. While you may think no big deal, if you have a decent connection it is. I rub shoulders with black hat hackers... They have people running port scans 24/7 looking for people just like you. I even personally knew someone who did it for them. Open up a network scanning tool and see how many times you get ping'd.  You might be surprised. While they would prefer to hack a server, they aren't beyond hacking home systems, particularly those serving kiddie porn.


And yes, it will be whoever's name is on the internet service who gets pulled into court, but they will confiscate any computer in the house and it can be months before you see them again. Then you can settle for $3k out of court or however much the court decides to fine you should you lose. Now, if you worked in the industry, your fine would only be about $3 per infraction. Since I doubt you work for the record or movie industry though, you can expect the maximum fine of $150k per infringement. If you are under 18, your parents are screwed, if you are over and it's all in their name, they can dump it into you if they want.

And if you think that $150k sounds bad, you haven't seen the lawyer fees by the time you go through an appeal or two.

[tp4tissue]

Port forwarding... You just punched a huge hole in your HARDWARE firewall, and directed traffic to a SOFTWARE firewall. FAIL
Private torrents... Because obviously it's impossible for people with billions to get invited.  FAIL

Private torrent sites have been compromised many times. You want as many ports on your firewall closed as much as possible, and a hardware firewall does this far more securely than a software firewall. Far, far more securely when you take into considering that you are using that computer. Get one little trojan and your software firewall is worthless. Not to mention odds are that you are relying on Windows firewall, which in itself is almost useless. Xp's original firewall only worked in one direction even. While you may think no big deal, if you have a decent connection it is. I rub shoulders with black hat hackers... They have people running port scans 24/7 looking for people just like you. I even personally knew someone who did it for them. Open up a network scanning tool and see how many times you get ping'd.  You might be surprised. While they would prefer to hack a server, they aren't beyond hacking home systems, particularly those serving kiddie porn.


And yes, it will be whoever's name is on the internet service who gets pulled into court, but they will confiscate any computer in the house and it can be months before you see them again. Then you can settle for $3k out of court or however much the court decides to fine you should you lose. Now, if you worked in the industry, your fine would only be about $3 per infraction. Since I doubt you work for the record or movie industry though, you can expect the maximum fine of $150k per infringement. If you are under 18, your parents are screwed, if you are over and it's all in their name, they can dump it into you if they want.

And if you think that $150k sounds bad, you haven't seen the lawyer fees by the time you go through an appeal or two.

I know what you mean.. I've been meaning to build an auto purge device using thermite packs

[tp4tissue]

Did one of you ..... Grrrrrrrrr.... wait, nm

[Leslieann]

Best thing to get fast torrent is to only one at a time and set max peers per torrent to something like 500.

What kind of router are you using that is handling 500 connections?
Most start losing ground around 200, even some with 64 megs of ram or more.

[tp4tissue]

Best thing to get fast torrent is to only one at a time and set max peers per torrent to something like 500.

What kind of router are you using that is handling 500 connections?
Most start losing ground around 200, even some with 64 megs of ram or more.

routers can def handle more than 500,   depends on what speed everything is coming in at..

at basic home internet speeds like ours.. 500 is nothing.

[Leslieann]

Best thing to get fast torrent is to only one at a time and set max peers per torrent to something like 500.

What kind of router are you using that is handling 500 connections?
Most start losing ground around 200, even some with 64 megs of ram or more.

routers can def handle more than 500,   depends on what speed everything is coming in at..

at basic home internet speeds like ours.. 500 is nothing.

Handle it, yes, handle it at peak performance is another matter.
Mine can do 500 connections, it can do 1000, but runs best around 210. 

[tp4tissue]

Best thing to get fast torrent is to only one at a time and set max peers per torrent to something like 500.

What kind of router are you using that is handling 500 connections?
Most start losing ground around 200, even some with 64 megs of ram or more.

routers can def handle more than 500,   depends on what speed everything is coming in at..

at basic home internet speeds like ours.. 500 is nothing.

Handle it, yes, handle it at peak performance is another matter.
Mine can do 500 connections, it can do 1000, but runs best around 210. 

which router is a pro like urself using

seems like my router cpu is @ 1.3 queue with 8000,  guess I should lower the limit.

[Leslieann]

I have a Netgear N600 (WNDR4000), it handles... um... a few servers, and computers...

[Input Nirvana]

Call me old fashioned but I think if it can be transferred on the internet, it should be free.

Anyone know what's going on with the new (last February or so) 6 Strikes thingy? Any results, what's happening with that?

[tp4tissue]

I have a Netgear N600 (WNDR4000), it handles... um... a few servers, and computers...

I think everyone will be tempted when the AC68 comes out.. Dual core arm..

quoted to be 5x faster than the AC66. 

[IvanIvanovich]

I have a ZTE H368N. I don't know it's specs really as I can't find much info on the internet and I haven't ever opened it yet. All I know for technical detail it is MIPS based. It has a lot of good features, and it has been a performer and totally reliable. Definitely not bad for the $60 or so I paid for it.