Technology
This is the official technology community of Lemmy.ml for all news related to creation and use of technology, and to facilitate civil, meaningful discussion around it.
Ask in DM before posting product reviews or ads. All such posts otherwise are subject to removal.
Rules:
1: All Lemmy rules apply
2: Do not post low effort posts
3: NEVER post naziped*gore stuff
4: Always post article URLs or their archived version URLs as sources, NOT screenshots. Help the blind users.
5: personal rants of Big Tech CEOs like Elon Musk are unwelcome (does not include posts about their companies affecting wide range of people)
6: no advertisement posts unless verified as legitimate and non-exploitative/non-consumerist
7: crypto related posts, unless essential, are disallowed
view the rest of the comments
Someone should investigate deeply. My combo of a whitelist firewall on an OpenWRT variant and Graphene often has a bandwidth issue that is clearly software related only after watching something from YT. I can stop the apps manually and close everything related to browsing and the connection issue still exists. I can disconnect the internet from my router and the problem still persists. However, if I shutdown all 3 devices for a few minutes and bring them up fresh, the network connection is flawless. Something is running in memory, and I believe it is related to YT, but I lack the skills to break it down further. I like to run an AI server and it is simply useless if anything on the network has connected to YT since booting.
I've also noticed when family is watching YT premium (not something I use) and I am downloading a LLM from HF, the internet bandwidth of our network more than doubles on my wired connection. In between the streaming packets from YT the speed on the download jumps massively. If family is watching YT, I can actually download a LLM faster. That just seems odd to me that those are connected.
Maybe your ISP has some sort of agreement with yt?
Does that seem legitimate to you? There are many more implications below the surface with this. Yes, YT has little black boxes that cache content locally with ISPs that also means they are likely filtering all data. I don't like that part, but I can live with it.
The idea that something is running on my device that seems to be hidden, but where I can stop the behavior by flushing the memory; that is extremely alarming. If I understand it correctly they have direct memory access for streaming video through h.264. Whatever they are doing is causing me to drop connections and impacting my WiFi signal stability even when offline doing tasks unrelated to YT. As soon as I reboot the problem is gone. I distrust them so much now that I do a hard reboot any time I watch YT. (It improves battery life as well.) This is criminal behavior if my speculative analysis is correct and they are running stuff like this in the background. I'm running a combo where I control every aspect of my network. This should not be happening in my circumstance.
Sometimes, less is more.
I would recommend trimming all your custom configuration from your router/firewall, one change at a time, until you can no longer reproduce the issue.
Or go the other way around: set up a barebones configuration, confirm the issue is resolved, and begin adding one customization at a time until it breaks.
How do your bufferbloat tests look?
https://www.waveform.com/tools/bufferbloat
It sounds like you have a lot of stateful inspection configured. YouTube's heavy usage of QUIC (i.e. UDP transport) may not play well with your config.
And, incidentally, what does your hardware look like?
Frankly, even the most barebones router should be able to handle YouTube. I am running pfSense in an ESXi VM, with passthru Intel gigabit NICs, 2 GB reserved RAM, and 2 vCPU (shared, but with higher priority than other VMs) on a Dell desktop with a second-gen i7 that was shipped from the factory in 2012.
Yes, I am routing on decade-old hardware. And I have never seen anything like what you are describing.
YouTube should "just work."
I am going to assume that if you're running OpenWRT, then you are probably using a typical consumer router? Please correct me if I am wrong.
Have you by any chance tried backing up your OpenWRT config and going back to stock firmware?
I know, I know, OpenWRT is great. I have a consumer router that I flashed with it to use strictly as a wireless AP.
But consumer devices flashed with vanilla OpenWRT tend to have very, very little resources left over to handle fun configurations.
And I have a feeling some of the fun configuration might be contributing to your issues.
After further investigation, apparently one of my routers 2.4G antennae is either held low or more likely fried. Sometimes the firmware is switching the working antenna more rapidly, enough to cause server outputs to look stable but other times it sticks on transmit or receive and doesn't toggle. Gradio is apparently not robust enough to compensate for the inconsistent connection.
It sucks because the router is from PCWRT and the dude updates and maintains the router and supplies a simplified interface. I've used it for years. It looks like LUCY has come a long way since I used it last. I have a couple of the same routers as the PCWRT router I was going to flash with OpenWRT, but the documentation for flashing this model is terrible. I guess I am going to need to figure out something going forward now. ...so yeah, maybe not YT.
When your layer 1 problem turns into a layer 3 problem 😅