Well everything was actually solved except i haven’t figured out the QoS stuff yet, speeds are lower than expected since I was maxing the CPU out on the Edgerouter X with smart queue on and getting about 250 Mb and 5-10 ms bufferbloat.
Now I have 225 Mb and 100-500 ms bufferbloat.
I tried the walkthrough on QoS from PCUNITE but I assume I missed something cause it had no effect, I’m probably missing the part where I mark the traffic.
I tried option 1 first, speeds were low, bufferbloat was too high, and I don’t really have room for the Arris in my lan closet.
Option 2 would be my next choice.
In my case I’ve had the arris unplugged for several days now and no issues.
So you removed the Ariss and connected the HAP directly to the ONT with ether1 as I suggested?
In this case, reset the default configuration from the system menu or type “/system reset-configuration” from the terminal. This should enable fasttrack on the bridge. You can now connect a laptop to any remaining ether port and run a few speed tests while monitoring the CPU cores from System/Resources/CPU.
Run cmd in Windows and type:
ping 8.8.8.8 -t
What is the average speed, ping and cpu usage? What is the speed you are paying for?
This is an important baseline, because fasttrack bypasses most of the firewall stack and once it is disabled for QOS, cpu will increase by at least 30%, and thus affect overall bandwidth. Furthermore, any rules we set for QOS must limit your WAN connection even further to be effective.
Once you have a baseline (best case scenario), we can experiment with queues. The first solution to bufferbloat is a simple queue. It’s a lazy hack, but it works with one major caveat: it’s resource intensive on a small HAP.
You must add a new queue type for SFQ in the terminal:
/queue type
add kind=sfq name=sfq-default sfq-perturb=10
The max limit of the queue must be less than the max speed with fasttrack.
You disable the default fasttrack rule from the firewall - don’t delete it, it’s useful for testing.
This should solve any bufferbloat issues quickly since it sets a hard limit for all your WAN bandwidth and it dynamically divides it equally among each client connected to the router as required (fair queuing).
You can change the in. interface in /ip firewall mangle or /ip firewall filter (clearly accessible in Winbox). You can also fasttrack the ports directly without marking the connections first - 1 step instead of 2, so it should save a little CPU - a dev would need to confirm if this is the case or not.