markwk
New Around Here
To keep the kiddos confined to their individual guest wifi networks (i.e. no roblox eating up all of our collective bandwidth) I had set the bandwidth limiter to 2 Mb/s upload and a slightly higher download for them. No limits for our "adult" wifi networks. This worked very well for the entire school year, up to now.
Around 11am while the kids were in school, my wife and I noticed our wired ethernet connections became suddenly very degraded. Our workstations are powerful, and we have a somewhat large network with our RT-AX86 as a hardwired mesh node. 2.5Gb/s everywhere, with a couple of dumb 2.5Gb/s switches along the way. Cat6a cabling throughout (new construction, did it all myself). This puzzled me for hours. Connecting directly to the AT&T residential gateway, the speeds were nominal, 985 Mb/s down and 960 Mb/s up. On our wired desktops, ~650 Mb/s down and 2.8 Mb/s up. Very consistent on each of our wall jack ethernet ports. So I knew it wasn't my cabling.
After awhile I capitulated and put our old RT-AC86 back into service at the WAN port. Voila, all of our hard-wired connections were back to symmetrical near-gigabit up and down.
So I ssh'd into the BE88U and poked around. No real errors from dmesg. ethtool on the ethernet links showed the expected 2500 Mb/s speeds. At this point I started thinking about throttling. Sure enough, tc qdisc revealed that the token bucket filter for the kids wifi networks had been applied to all links and vlans. Rather than override / revert the queuing disciplines manually (too much like work) I turned off their bandwidth limiter, rebooted, and now I'm back to full goodness.
I'll be entering a bug report!
Around 11am while the kids were in school, my wife and I noticed our wired ethernet connections became suddenly very degraded. Our workstations are powerful, and we have a somewhat large network with our RT-AX86 as a hardwired mesh node. 2.5Gb/s everywhere, with a couple of dumb 2.5Gb/s switches along the way. Cat6a cabling throughout (new construction, did it all myself). This puzzled me for hours. Connecting directly to the AT&T residential gateway, the speeds were nominal, 985 Mb/s down and 960 Mb/s up. On our wired desktops, ~650 Mb/s down and 2.8 Mb/s up. Very consistent on each of our wall jack ethernet ports. So I knew it wasn't my cabling.
After awhile I capitulated and put our old RT-AC86 back into service at the WAN port. Voila, all of our hard-wired connections were back to symmetrical near-gigabit up and down.
So I ssh'd into the BE88U and poked around. No real errors from dmesg. ethtool on the ethernet links showed the expected 2500 Mb/s speeds. At this point I started thinking about throttling. Sure enough, tc qdisc revealed that the token bucket filter for the kids wifi networks had been applied to all links and vlans. Rather than override / revert the queuing disciplines manually (too much like work) I turned off their bandwidth limiter, rebooted, and now I'm back to full goodness.
I'll be entering a bug report!
