I have a DIR-878 and I don't have this problem! I'm using version 22.03-SNAPSHOT is very stable
Currently testing OpenWrt SNAPSHOT r19944, released approximately 3 days ago.
No issues with the 5 GHz WiFi yet.
In general,
I've had better luck with snapshots.
Encountered issues with all the 22.03.0 release candidates.
there was another update after this one for MT76
my newifi3 d2 with OpenWrt SNAPSHOT, r20011-265f402fbd no isssues on wifi 5 connection.
Thank you all, I switch to the shaphot version of 22.03
This is unrelated to this post however can anyone with an mt7621 device test this?
DIR-882 rev.A1
Installation did not encounter any issues. Internet connectivity appears okay.
Will keep an eye out for 5 GHz WiFi issues.
EDIT:
Another router.
DIR-878 rev. A1
No issues encountered for installation. Internet connectivity appears okay.
Thank you very much!
You're welcome.
Question: Does the patch have any impact regarding peer to peer traffic? e.g. QBitorrent?
It does not directly affect it but you may experience improved bidirectional data transfer speeds as this is what the p2p programs do.
Check out this iperf3 bidirectional speed test with hardware offloading.
Without the patch
[ 5][RX-S] 0.00-20.00 sec 353 MBytes 148 Mbits/sec receiver
[ 8][TX-S] 0.00-20.00 sec 1.79 GBytes 769 Mbits/sec 0 sender
With the patch
[ 5][RX-S] 0.00-20.00 sec 2.16 GBytes 926 Mbits/sec receiver
[ 8][TX-S] 0.00-20.00 sec 1.80 GBytes 775 Mbits/sec 0 sender
Thanks for the reply.
Does the patch rely/expect on software and hardware flow offloading to be enabled?
I ask, since I don't bother enabling either of them; ISP plan does not exceed 500 Mb/s.
No, enabling hardware offload is not necessary. However, I've seen much better performance when it is enabled. If you'd like to keep it off, it will still perform better with the patch. Though, I'd suggest you enable it.
Will test with software & hardware flow offloading enabled then.
For those interested,
Another release candidate 22.03.0-rc5 listed available for MT7621 routers.
Just advance warning:
I encountered 5 GHz WiFi errors with release candidates 1 to 4.
Currently testing arinc9's patch release, so unable to test release candidate 5.
i've tested this release using my 1T1R device, the performance still bad but at least now it performs better. No complaints with more than 1 stream devices, it just perform normally.
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-1.01 sec 256 KBytes 2.08 Mbits/sec
[ 4] 1.01-2.00 sec 0.00 Bytes 0.00 bits/sec
[ 4] 2.00-3.01 sec 1.00 MBytes 8.32 Mbits/sec
[ 4] 3.01-4.01 sec 1.12 MBytes 9.47 Mbits/sec
[ 4] 4.01-5.01 sec 1.50 MBytes 12.6 Mbits/sec
[ 4] 5.01-6.00 sec 640 KBytes 5.25 Mbits/sec
[ 4] 6.00-7.01 sec 1.00 MBytes 8.35 Mbits/sec
[ 4] 7.01-8.01 sec 384 KBytes 3.14 Mbits/sec
[ 4] 8.01-9.01 sec 896 KBytes 7.36 Mbits/sec
[ 4] 9.01-10.01 sec 128 KBytes 1.05 Mbits/sec
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-10.01 sec 6.88 MBytes 5.76 Mbits/sec sender
[ 4] 0.00-10.01 sec 6.73 MBytes 5.64 Mbits/sec receiver
iperf Done.
Thanks for the feedback madeizwar
I dont know if have relevance, but at least for me in my dir-882 A1, the latest snapshots and in the 22.03 rc5, the wifi 5 have problems, after a few minutes to 2 hours, the wifi 5 have no internet, then, and again, i dont know if have relevance, but the wifi hardware of the dir-882 A1 is the mt7615N, in both wifi radios, but the driver installed in the firmware is for the 7615/7615e, then, have this some revelance/importance for the bad wifi 5 performance?
The same thing happens to me too, I have tested several client devices and it happens with all of them.
For testing I also tried with my old DIR-860L and the same thing happens, exactly as they wrote here:
How is it possible that after a long time it is still not possible to understand the cause?
rakantoh and craz,
You can try the custom release by arinc9 and see if that helps.
His release should be using an older kernel and drivers...
Anything that can go wrong, will go wrong - Murphy's Law
These wifi drivers are just fairly complex things to get working right at every possible situation. One would have to have a driver with additional debugging features enabled, wait for the bug to appear and then try to figure out what has happened. I am not sure you want to go there though.