linux - Does bittorrent need a proxy?

07
2014-07
  • Aaron

    I want to use one of my Debian servers for a "torrent" machine.

    I have utorrent on my gaming machine which doesn't require a proxy. But it said on a tutorial that you need a proxy with bittorrent.

    Is that true?

  • Answers
  • drk.com.ar

    Requiring a proxy doesn't depend on the client software but on your network configuration. If your server is running behind a proxy, you will have to configure that in the torrent client software. If your server is behind NAT or firewall, you don't need to configure a proxy but there is an additional port configuration.


  • Related Question

    Why is bittorrent slow from my home computer?
  • Mr. Flibble

    For non-bittorrent files I can usually get 1MB/s down on my home network, and 10MB down on a professionally hosted computer.

    When I download a file using bittorrent I often get maxed out on the hosted machine, but only get 90kb/s on my home computer.

    I don't believe my upload speed has anything to do with it as the files have many seeders. My upload speed on the hosted computer is negligable.

    I can get other files (http/ftp) at 1MB/s at home. Just not bit-torrent. Apart from ISP throttling, which I'm told is not in effect, what would be causing this?

    At the moment the fastest way for me to download a file is to get it on the hosted computer and then download it to my home computer over http - which just doesn't strike me as the best thing to do.

    Edit: Using uTorrent. b=bit/ B=byte. Would my consumer router be the cause? Limiting number of connections perhaps?


  • Related Answers
  • OverloadUT

    The most common cause of this problem is having your BitTorrent software set up to have too many maximum connections. Most BT software (even the most recommended ones) have default settings that will make most home routers cry.

    In your BitTorrent client, find the area where you can set the maximums and set it WAY lower. Start with something like 50, let it run for a few hours, and then maybe try increasing it.

    The cause of this is the plain and simple fact that home routers are by and large not designed to handle so many concurrent connections. It just isn't normal outside the world of BitTorrent. This would completely explain why you are seeing different performance from a machine being hosted at a professional hosting company, which probably uses business-class routers.

  • chris

    You mention that your ISP isn't throttling, but it wouldn't hurt to verify that -you can do that here

  • joe

    Macha has a point about the "bytes vs bits", but if I assume you know this, there can be many other factors that lead to this problem.

    First, check to make sure there has not been a setting flipped in the configuration panel. Then double check.

    Also, make sure your port is open/routed to your network IP. I have seen this cause a drastic slowdown in performance.

    Also, could you please include what client are you using?

  • bobince

    I can get other files (http/ftp) at 1MB/s at home. Just not bit-torrent.

    Well then. You're being hit by protocol-based (DPI) throttling.

    Whilst the factors listed by OverloadUT are all true, they aren't the most common BitTorrent bottleneck. BitTorrent clients aren't completely stupid and don't in the typical case overload the router. They can, sure, but ISP throttling is by far the more likely explanation.

    Apart from ISP throttling, which I'm told is not in effect

    Ha! Yeah, sorry. Your ISP will tell you that. Because they're liars. Who are they? If you're in the UK or US they almost certainly have a “Fair Usage Policy” that states in small print you're not going to get any bandwidth if they don't feel like it.

    the fastest way for me to download a file is to get it on the hosted computer and then download it to my home computer over http - which just doesn't strike me as the best thing to do.

    Welcome to seedboxing. It's what everyone else does.

  • Macha

    Your ISP may be measuring your Internet speed in megabits while your client measures in kilobytes.

    1 megabit = 128 kilobytes

    @Chris: 1 megaBYTE = 1024 kilobytes. 1 megaBIT is 128.