When any device on the network (wired or wifi) is downloading or uploading the ping on my network skyrockets from 15 ms to 500+, frequently hitting 1500ms or timing out.
When running speed tests the ping to the router stays at 1ms, but pings to the modem skyrocket and sometimes time out. This seems to be an obvious bufferbloat problem.
Connection Speeds: 450Mbps Down, 20Mbps Up
There is built in QoS (fq_codel), but I've read that it stops interfering at some bandwidth threshold.
I escalated this thread in hopes of getting some official response on this.
Could be worth testing with "preferred activities":
And if you have a router in front of Nest Wifi that is not in bridge mode, meaning you run double NAT, that could be a problem here too.
Thanks, I do have preferred activities enabled which is why I probably haven't noticed this problem in any video calls thankfully, really wish Google expanded it's QoS options. To be kicked from an online game because someone is downloading or uploading a file is aggravating. I do remember google wifi working fine with our previous internet plan that was around half the speeds we currently have, kinda insane that I'm seriously considering downgrading our internet to deal with bad QoS.
No second router here
@olavrb, thanks for the help!
@Keegs, thanks for reaching out. I'm sorry to hear that you're having an issue with your Google Wifi. I'd love to know more about this and I have a few questions:
Looking forward to your response.
Two notes - 1) Once you pass a certain speed, the bloat shifts to the wifi. Which can be quite horrendous. I don't know if nests's wifi has the fixes we put into linux 4.18 and later for the the mt76, ath9k and ath10k chips (relevant paper: https://www.cs.kau.se/tohojo/airtime-fairness/ )
2) When I last looked nest was effectively applying fq_codel and a shaper to the link at speeds below 300Mbit but ran out of cpu to do it above that. IF the bloat is actually coming from the ISPs link at your 400mbit, you can put a 500mbit+ capable router in front of that, keeping your nests for wifi, and your network will get overall better. You can test this by testing wired. I do not know if I can recommend products that are 500+ capable here, but everybody knows I'm a huge fan of openwrt on a decent x86 box, and there are multiple commercial offerings nowadays with sqm that can run at these faster rates, well.
It is odd, and depressing, that sometimes a "faster" link behaves so much worse than one with well managed queues on it.
@dtaht, thanks for the help!
@Keegs, thanks for the response. What type of cable are you using from your ISP modem to your Google Wifi device? Also, could you try a 2 minute power cycle on your devices? Please try the following steps:
Just a note: I'm one of the original authors of fq_codel, cake, etc. I tried to point out over here, many moons ago:
some flaws in the config dump I was able to analyze, notably the side-effects of GRO are a PITA.I passed those observations over to the original author of the arl + fq_codel code, but I have no idea if you took them up, or this product is configured similarly.
If y'all could find a way to share your config and observed problems with me, perhaps I can help optimize your product(s). But please pass those observations along to whoever might care.It's also generally been my hope that y'all would jump on cake as the per-host FQ is awesome (IMHO).
Also the wifi code has been in the kernel for a while and should scale much better than shaping does:
Hope this helps!
@dtaht, we appreciate the help.
@Mussels, thanks for getting back to us and sorry for the delay.
Give these steps a try:
Keep us posted.
Just had this happen to me as well, after several years of never seeing this behaviour
While gaming and a different PC was updating, pings went from 25ms to 150ms, and stayed there until the downloads had finished
50Mb down 20Mb up
It is NOT POSSIBLE for me to bridge the modem/router so support have refused to help, despite DMZ for port forwards and IPv6 having everything function normally
If this continues i'll be ditching the google mesh, it's useless when they forcibly change settings for the worse and we can't roll them back or manually adjust them.