omgz torrents!!11
But double 0.1kb/s is like 0.2kb/s :(
Can this lead to any network vulnerabilities?
Seed box?http://en.wikipedia.org/wiki/Seedbox
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..
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
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 trackersUsing private trackers won't save you unless you're using a seedbox.Show Image(http://www.cute-factor.com/images/smilies/onion/04a97f13.gif)
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 trackersShow Image(http://www.cute-factor.com/images/smilies/onion/04a97f13.gif)
achem... private trackersUsing private trackers won't save you unless you're using a seedbox.Show Image(http://www.cute-factor.com/images/smilies/onion/04a97f13.gif)
Seriously people GET A SEEDBOX, download with SFTP.
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 trackersShow Image(http://www.cute-factor.com/images/smilies/onion/04a97f13.gif)
lol. Okay, your parents are totally safe. GL to them!
I AM TALKING ABOUT WINDOWS 3.1. DO YOU HAVE A COPY?
Nice! You got that hooked up to the Internet?
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 trackersShow Image(http://www.cute-factor.com/images/smilies/onion/04a97f13.gif)
lol. Okay, your parents are totally safe. GL to them!
what are you talking about?
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 trackersShow Image(http://www.cute-factor.com/images/smilies/onion/04a97f13.gif)
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.
C'mon guys...let's give this a break. We can talk about Windows 2000 instead!
i'm surprised no one has mentioned usenet yet.
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
i'm surprised no one has mentioned usenet yet.
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.
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?
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.
Handle it, yes, handle it at peak performance is another matter.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.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.
Mine can do 500 connections, it can do 1000, but runs best around 210.
I have a Netgear N600 (WNDR4000), it handles... um... a few servers, and computers...