@phinn you noticed a throughput difference between the two packet steering scripts? With my 1gb docsis cable lines - they both allowed max throughput. What I did notice was increased jitter with “all CPU” vs standard… leading me to believe that the new script was acting as intended, and minimizing latency.
Yea increased jitter makes sense given what its doing and if it doesn't need to spread things out to the cores it can hurt slightly. Same goes for irqbalance, which on this target mostly just spends time rescheduling interrupts. I found the difference to be very small on my tests. Enabling it is the main difference in performance.
A little background here -- I've been using OpenWrt for five years now, mostly on a GL-iNet GL-B1300. My connection is 1 Gb Verizon Fios. The B1300 was a little underpowered for that connection and when the front lights stopped working, I decided to upgrade. I used my old Eero 6 Pro for a while and got used to the consistent 600 Mbps download and upload speeds, but missed the flexibility of OpenWrt and figured the GL-iNet MT6000 would be a good replacement. It's mostly great -- I get better download speeds than the Eero, usually in the 700 Mbps range, but the upload speed is abysmal. I'm lucky if it's over 100 Mbps. I've done many searches and encountered people with the same problem, but have not found a solution yet.
- I'm always on a 5 GHz channel when I test.
- Packet steering is enabled for all CPUs.
- Steering flows (RPS) are at the suggested setting of 128.
- Hardware offloading is on (also tried software offloading).
- Irqbalance is on.
- I tried going back to the GL-iNet firmware (could this be a MediaTek thing?).
Nothing fixes the upload speeds (except swapping the Eero back in). I'm beginning to think this is something I'll have to live with. Thoughts?
Do you have a link to those benchmarks? Checking the wiki it just has the recommendations, but not the data or plots to back up the recommendation.
Do you tried Hardware Offloading off and SQM?
I've tried hardware and software offloading. I have not tried SQM, mainly because it is turned off on my Eero, which works fine. But I will go ahead and give it a shot.
No luck with SQM 
That sucks, you may have something else going on 
That is odd, I'm maxing out my 500/500 connection with my Flint 2. Have you checked the "stupid" things?
- Does the cable make a difference?
- What ethernet up link speed does the Flint 2 think it has?
- Try swapping the WAN and 2.5G LAN port and see if your WAN port is physically faulty.
- Try swapping the WAN and one of the 1G LAN ports?
Well this is interesting -- Since the Eero works fine, I ran an ethernet cable from the Eero to the MT6000 WAN port and now the MT6000 is getting full upload speeds. This is not a long-term solution, but it does seem to indicate that there are communication issues between the MT6000 and the Fios ONT box. Hopefully there is some setting I can change on the MT6000.
That is a step forward on the troubleshooting path. You have now isolated it to either the cable or the communication between the devices. It is unlikely that you have faulty hardware (apart from possibly the cable).
One thing to keep in mind is that 2.5G ethernet can be finicky, not all devices react well to the other end trying to negotiate that speed, or so I have heard (I haven't had any issues myself). So you could try reassigning which port is the WAN port on the Flint 2 to a 1 GB port. For this you likely need to make use of VLANs.
There should probably also be a way to cap the speed to 1G, preventing 2.5G from being attempted at all. Probably this is possible with ethtool manually as a test at least. Some reading of the manual page will be needed.
1 Like