On 6/23/19 2:24 PM, Michael Butash wrote:
I find you're only as fast as your 1) home isp connection and 2)
torrent peer(s).
I know this. I've got 10 Mbits down and 1 up.
Sometimes your speed as only good as your isp, particularly depending
if your isp is hating on your torrenting. Comcast has been known to
rate limit torrents actively, thus net neutrality debates were born.
I find using CenturyLink, it is always oversubscribed in their local
peering, so things tend to be a bit slow at first, but otherwise
window up fast to max bandwidth if enough peers. Cox charges
bandwidth overages now, but their service (internet peering) is
generally better quality. I don't like random surprise overages after
watching some 4k movies, so I'm now with CL with no caps.
How fast is your Century Link service? Are you stuck with dsl or do
they offer something faster? I've heard that many ISPs are imposing
data caps now so they can screw people out of more money.
You should never, ever get torrents from your direct home IP. Just
don't - you are inviting problems. Get a reliable, trustworthy vpn
service. This influences again how fast you are downloading, make
sure your vpn gives you good speed too.
I got one of those threatening emails from AT&T saying I've been naughty
and listing the torrent in question. I use a VPN now and get no more
nasty emails from the isp.
Almost any residential service, dsl or cable are asynchronous transfer
rates, meaning faster to download than upload. Interesting thing with
cable particularly, uploading at capacity tends to influence your
downstream rates in bad ways. If you are maxing out your upstream to
seed, your downloads are likely affected in some way. It's a long
answer why, read up on docsis if interested. Limit your upstream
rates in your torrent client/server to a respectable number is the
short of this.
Torrents tend to create a _lot_ of packet per seconds and connections
- make sure your router/firewall can handle this. I've seen
torrenting kill enterprise firewalls in session/pps counts.
Connection counts affect memory, and might/will kill a cheapo router.
I see this occasionally with customer "incidents" when doing
network/security consulting, and finding someone doing something
stupid like installing a torrent client on their work computer as they
end up being a top-talker I find with simple source flow counts for
*abnormal* traffic. I've also had roommates kill my firewall doing
this, before I find, block, and threaten them with no internet access
ever again.
I used to have a roommate about 10 years ago who bogged down my internet
connection with his stupid online shoot em up games. I couldn't
download anything. I'd connect to the router and see that he was
downloading little but maxing out the upload speed. It must have been
something to do with that docsis issue you mentioned. I fixed the
problem by setting a limit on his upload speed so he only got half of
what was available. He complained when implementing this change kicked
him offline for a minute or so, but not after that
I don't find a lot of other optimization of clients are necessary. I
use a transmission-remote server and otherwise feed everything through
that as a server appliance from numerous clients on the lan (desktop,
laptop, phone, sometimes remote), and all torrent collection show up
as from an eu country via my vpn service. Above guidelines are quite
good for my purposes.
-mb
I use protonvpn. It's cheap and it works, and i don't get anymore nasty
emials from my ISP. Thanks for your reply and also thanks to everyone
else who replied.
---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
https://lists.phxlinux.org/mailman/listinfo/plug-discuss
