Slow torrent uploads
-
Hi all - I have pfSense running on metal on a Q6600 with 2GB RAM and an Intel quad gigabit NIC. WANs are 2 x VDSL running PPPoE from pfSense in round-robin load balancing. A few services are set up in NAT to forward inbound traffic including Plex, FTP and torrents via a custom port range, I've not touched the default allow-all outbound rule. Inbound speeds are fine with all services topping out at ~ 150/35 Mb/s on a theoretical 160/40 Mb/s, as long as the protocol is multi-threaded. Torrent download speeds are absolutely fine, maxing out my connection when my favourite Linux ISOs are well seeded @ ~ 17MB/s. However, I'd like to do my bit to share with the Linux ISO community but my upload struggles to exceed 100kB/s or so when it's limited to 10MB/s in the application (Deluge). I've posted about this issue on /r/pfsense and a few others are reporting similar problems. My ISP operates no rate limiting (it's effectively illegal in the UK now, along with fair usage caps - thank you Ofcom) and the problem goes away if I bypass pfSense and revert to (one of) my ISP's standard kit. The rest of my network is hard wired gigabit where it matters, which I happily max out @ 110MB/s. In the past I've tried uTorrent, Azureus and a few of the other usual suspects but would prefer to stick with Deluge for now.
Posted in 'Firewalling' in the hope that it's the most appropriate forum.
Any ideas?!
Thanks
-
I'm also seeding Linux/Opensource torrents. About 125GiB worth over 70 torrents. My average upload rate is about 1MiB/s, which is about 14KiB/s per torrent. About 80% of my torrents are idle at any given time, of the 20% not idle, about 80% are uploading less than 40KiB/s.
A lot of people seed opensource torrents. If you don't download a torrent within the first week, you won't upload much. I typically download a torrent within 24 hours of it going live and I won't be uploading much more than 3MiB/s for a day or two. If I get on the train within 8 hours, I can typically cap my 100Mb/s connection for 2-6 hours before the army of leechers turn into seeders.
You may also want to make sure ports of forwarded, manually or via UPNP. This makes a huge difference in seeding performance.
-
Thanks for your input, I have the same issues regardless of type of torrent.
You mention port forwarding - which ports should be forwarded?
-
You mention port forwarding - which ports should be forwarded?
The one being used by your torrent app. if ti's set to randomize the port then reconfigure to use a specific port and then forward that port.
-
@KOM:
The one being used by your torrent app. if ti's set to randomize the port then reconfigure to use a specific port and then forward that port.
The inbound ports are mapped already, what would the outbound ports be mapped to?
-
Nothing. Outbound connections aren't blocked by the firewall usually.
-
OK, so still looking for a solution!
