Torrents Resulting in WAN Packet Loss
-
@planedrop A search for "8311project" will lead you to the solution I used to rid myself of ATT HW.
-
@AndyRH Yeah I've heard of this, thanks for the reminder. I might go down this path just to see if it fixes the issue, if not I'll do a VPN, but this would be free so might as well give it a shot.
I don't really foresee the 6100 being the limit here though, sure it's a lot of pps and connections, but shouldn't be enough to slow it down I wouldn't think.
-
@planedrop said in Torrents Resulting in WAN Packet Loss:
I don't really foresee the 6100 being the limit here
I have a 7100, same CPU, and it is not troubled by my ~20 ISOs seeding. Last I looked I was running about 11k open states. My torrent client has a global max of 500.
-
@AndyRH OK yeah figured that was the case, in theory it should have more than enough oomph to handle something like this.
I'll look into bypassing the ONT and see if that makes a difference, otherwise I'll go with a VPN.
For reference, I was seeding 200 ISOs, in less than 1 month I'm already over 10TiB of uploads with it lol, so was definitely doing a lot of it but it still should be within the realm of possibility.
Considering it worked fine for a while, I am wondering if my ISP is just being awful and I'm on a "blacklist" so to speak.
-
Latency at >1s is pretty bad!
What sort of WAN connection do you have? Failing modem perhaps?
-
@stephenw10 Correct, but that was only during the torrents, otherwise latency is like 5ms.
Something about the torrenting in specific is making my ISP crap the bed basically, and I'm trying to get to the bottom of whether it's my ONT, just my provider in general, or something intentional from the provider.
(and initially posted here to make sure it wasn't pfSense possibly causing the issue, though I didn't think so)
-
Some connections/states limit perhaps? The graphs should show you that too.
-
@stephenw10 There was a lot of states, and state changes per second, during this time, but nothing that should be going over what it can handle.
For reference here is a photo, the spikes are during torrents being on, the rest is normal traffic.
-
Hmm. I mean 6000 states is nothing for pfSense but potentially could be an issue for something else in the route.
-
@stephenw10 Yeah that's what I'm thinking, maybe the ONT itself can't handle it or something along those lines.
I know many ISPs do throttle torrents, but you'd usually see that as the torrent traffic itself having higher latency and stuff, not just dropped packets on the entire connection, though it doesn't appear the later is unheard of.
Pretty confident at this point it isn't pfSense, so at least that's good. May also see if my ISP can get a tech out, after I test both VPNs and possibly direct fiber connectivity instead of the ONT.
