Your link is to the current Stable Release build 21.02.3, which still displayed multiple errors Address Not Found on the 5 GHz WiFi, after nine days of uptime. Which is a lot better than the two previous Stable releases.
With that said,
So far, I have had better results with Development Snapshot builds released in 2022.
Update,
Currently testing OpenWrt ̶2̶2̶.̶0̶3̶.̶0̶-̶r̶c̶2̶
Not sure what happened but first attempt to flash via D-Link recovery failed with router disconnecting in 10 seconds from PC used to install dlink_dir-882-a1-squashfs-factory.bin
Second attempt, shutting down the router and repeating the D-Link recovery process, worked fine.
Adblock and irqbalance appears to be working fine
but
As expected, due to FW4?, banip fails to work.
EDIT: Encountered error on 5 GHz WiFi, 1 day 8 hours into testing
Address Not Found
Android phone had no problems streaming videos. Stopped using phone (it went to sleep), approximately 8 minutes later, went to browse the internet and encountered error.
Back to using snapshots.
Update,
Testing OpenWrt 22.03.0-rc3
No issues encountered during installation.
Adblock and irqbalance appears to be working fine.
Did not bother testing out banip since OpenWrt 22 releases uses nftables.
Will update/edit uptime once in a while.
nftables can be uninstalled (even though it comes pre-installed and "default" in snapshot builds of 22.03+) and legacy fw3 iptables re-installed. Currently, the luci-app-banip and banip packages are not being offered as of 22.137+ . I ended up manually downloading the .ipk's from 21.02 packages and installing them manually with the opkg install command. Things are working under 22.137 as they did in 21.02 as long as you're still using iptables. I ran into this issue when trying to run an attended sysupgrade and found that the packages were no longer available for some reason - the developer is supposedly working on a new version for nftables.
Thanks for the workaround m0dul8r,
Not familiar with suggested process, so will skip it but others familiar/comfortable with it, should be happy.
Update OpenWrt 22.03.0-rc3,
Uptime: 6 days, 1 hr and counting...
Have not encountered the 5 GHz WiFi errors
Address Not Found
nor
Connected, no Internet
Update OpenWrt 22.03.0-rc3,
I goofed. Forgot to remove weekly scheduled reboot in Scheduled Tasks that I entered out of habit.
Needless to say, router rebooted after 7 days. 
̶W̶i̶l̶l̶ ̶r̶e̶s̶t̶a̶r̶t̶ ̶u̶p̶t̶i̶m̶e̶ ̶t̶e̶s̶t̶.̶
EDIT:
Since RC3 is no longer available for download, no use testing for uptime.
OpenWrt 22.03.0-rc3 seems a lot better than previous openwrt I had. One thing I would recommend to do is set the country code in wifi radio settings and then set the channel to upper 5ghz band e.g channel 140 which is specified for indoor and outdoor use. If you do not set country code this will not work. There are at least android apps that can scan for a good free channel. Point being a lot of these upper channels are avoided by other routers for various reasons. Also better to have multiple wifi or eth when changing wifi settings so you do not lock yourself out. It seems that OpenWrt 22.03.0-rc3 has a bug so it does not always boot up. Sometimes have to re-plug power several times before it comes up. Needless to say I am sticking with 22.03.0-rc3 though.
Thanks.
I have not encountered that bug but will keep an eye out for it.
It was removed from server (rc3 and rc2) so we have to downgrade now anyways?
Wonder why they removed the two release candidates.
takimata posted that there were bugs with the firewall not reloading properly. Perhaps that was the reason.
I'll go back to using the snapshots for now.
Testing OpenWrt SNAPSHOT r19781: dated Thu Jun 9,
Noticed that for the 2.4GHz wireless radio,
For Channel, no Auto selection anymore.
OpenWrt 22.03.0-rc4
In 1 day 2 hrs,
Encountered the 5 GHz WiFi error message
Address Not Found
Android phone had Firefox web browser open, phone went to sleep,
After a few minutes attempting to browse, resulted in error message.
Back to testing snapshots instead.
Testing OpenWrt SNAPSHOT r19791: dated Sun Jun 12,
Noticed that for the 2.4GHz wireless radio,
For Channel, the Auto selection still missing.
As far as I have understood if you build openwrt from sources you can select 5.15 kernel. It might take 6-12 months before releases with this new kernel roll out though. OpenWrt 22.03.0-rc4 fixed boot issue for me. ksmbd also started working. Can't say I have noticed anything yet that I could blame on the wifi.
Update,
OpenWrt SNAPSHOT r19903: dated Fri Jun 24,
No issues encountered during installation.
Adblock and irqbalance appears to be working fine.
For the 2.4GHz wireless,
In Channel, the Auto selection has returned.
For the 5GHz wireless,
Channels above 140 appears, after 5GHz is enabled.
I've also facing this issue with 5ghz MT7615E with OpenWrt 22.03.0-rc4 installed. The connection using single chain or vht-nss1 always dropped as shown in nperf speed test below. my device is EA7500 V2 being the router and AP.
Connecting to host 10.XXX.X.226, port 5201
[ 4] local 10.XXX.X.187 port 64823 connected to 10.XXX.X.226 port 5201
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-1.01 sec 640 KBytes 5.17 Mbits/sec
[ 4] 1.01-2.01 sec 0.00 Bytes 0.00 bits/sec
[ 4] 2.01-3.01 sec 512 KBytes 4.20 Mbits/sec
[ 4] 3.01-4.01 sec 128 KBytes 1.05 Mbits/sec
[ 4] 4.01-5.00 sec 512 KBytes 4.22 Mbits/sec
[ 4] 5.00-6.00 sec 512 KBytes 4.21 Mbits/sec
[ 4] 6.00-7.01 sec 384 KBytes 3.11 Mbits/sec
[ 4] 7.01-8.01 sec 768 KBytes 6.30 Mbits/sec
[ 4] 8.01-9.01 sec 0.00 Bytes 0.00 bits/sec
[ 4] 9.01-10.01 sec 128 KBytes 1.05 Mbits/sec
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-10.01 sec 3.50 MBytes 2.93 Mbits/sec sender
[ 4] 0.00-10.01 sec 3.31 MBytes 2.78 Mbits/sec receiver
iperf Done.
Compared to MT7612E with OpenWrt 19.07.9 on the same network (dumb AP with EA7500 V2 as the router)
Connecting to host 10.XXX.X.226, port 5201
[ 4] local 10.XXX.X.187 port 64883 connected to 10.XXX.X.226 port 5201
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-1.00 sec 6.00 MBytes 50.2 Mbits/sec
[ 4] 1.00-2.01 sec 6.50 MBytes 54.3 Mbits/sec
[ 4] 2.01-3.00 sec 6.38 MBytes 53.7 Mbits/sec
[ 4] 3.00-4.00 sec 6.50 MBytes 54.5 Mbits/sec
[ 4] 4.00-5.01 sec 6.62 MBytes 55.1 Mbits/sec
[ 4] 5.01-6.00 sec 5.00 MBytes 42.3 Mbits/sec
[ 4] 6.00-7.01 sec 5.75 MBytes 47.9 Mbits/sec
[ 4] 7.01-8.01 sec 5.38 MBytes 45.2 Mbits/sec
[ 4] 8.01-9.00 sec 5.88 MBytes 49.7 Mbits/sec
[ 4] 9.00-10.01 sec 6.12 MBytes 50.8 Mbits/sec
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-10.01 sec 60.1 MBytes 50.4 Mbits/sec sender
[ 4] 0.00-10.01 sec 60.1 MBytes 50.4 Mbits/sec receiver
iperf Done.
wondering if there's some possible improvement....
p.s. the connection in vht-nss2 is pretty fine before, i've try to pull around 160Mbps in same channel (161) and 20Mhz with intel 7265 card. The connection only drops when the client is single chain devices.
Please note that important updates were done to mt76 driver after 22.03rc4 release:
thanks for the information, i've wondering does the fix only done with DFS condition? I already set the channel fixed at 161 (and everything between 149-161), but yea i'll try to test the snapshots if my time allows it.
Regarding snapshots,
Noticed the following: mt76: update to the latest version
Fri, 24 Jun 2022 15:15:12 -0400 (21:15 +0200)
b6e865e2cc70 mt76: mt7615: fix throughput regression on DFS channels