Yours shows all the processing goes to the last core ie no irq balancing. May happen one bad day with more bandwidth too comlex sqm qdisc runs both ways on one core and drops occur...
nf_conntrack 1st field is what you count -> number of CT states (in hex)
dunno if 0021699a in softnet is RPS pushed to other CPU or software fragmentation
I was going to double-check again at my workplace with a different ISP and... Anydesk server connection lost too at my home place.
So packets are lost not only to my VPN
I double-checked it at work place, and suddenly it works. And I noticed that for some reason, uTorrent started working there. But at home, it's qBittorrent. I downloaded Transmission at home. And the problem went away!
I absolutely don't understand how this client can hack a router. But it can.
Thanks everyone for your help and support.
By the way, the QOS issue resolved itself. Transmission uses the entire bandwidth, but it doesn't jam other traffic.
Bittorrents of course can jam other traffic but these days the issue not that severe as it was when uTP appeared. Nowadays they use low priority congestion control algorithm for that. It backs down quite effectively.
Thanks for the help anyway. It took me 2 months to dig into the problem. I bought a new industrial mini PC to use as a router. I have been fighting for 2 months with the technical support of both my Isp and the server side . And all this is because of the crooked torrent client.
You'd be laughing but qbittorrent conciderably slows down my experience! I opened CNN website and it was loading like it's 1999. I used Appimage version.
EDIT: It's nothing critical, everything works fine but I can easily notice difference in loading typical websites. Video works just fine up to 4k.
I bet the problem that qbittorrent prefers TCP over UDP for downloading. At least this is what I see...
Most incoming connections are TCP (unlike Transmission) and, since they use in kernel congestion control like Cubic, they effectively compete with your other typical Internet connections just throttling them down by number. And, to make it worse, you had only one SQM bin...
But, unlike Transmission, qbittorrent correctly marks outgoing traffic as lower priority, so it gets to Bulk if you have correctly functioning SQM with several bins.
EDIT: I tried another, much lower end, PC in my LAN and it worked just fine. So SQM works as intended, no considerable drop in experience. IMO the problem is in preference of TCP over UDP, 100 connections can effectively throttle others coming to or from same PC.
P.S. don't blame me, I didn't even try to configure qbittorrent. I bet it can be fixed. I tested default settings over not so default setting of my OpenWrt router.
Iβm on Windows 11 Pro 25H2 26200.7171 and it was killing my surfing totally. I won't tell you the qBittorrent version - I've already deleted it completely.
It doesn't matter. The problem is in preference of TCP over UDP (uTP). Transmission uses UDP (uTP) whenever possible. And uTP, even if SQM/AQM doesn't exist, will always back down in presence of TCP connections managed almost universally by Cubic (including Windows).
You're too hasty. You can tune qbittorrent up. I checked it and it works (see advanced settings in very bottom). The problem was not in OpenWrt but in default settings of your Bittorrent client which allowed easy saturation of the connection between you and your router.