OpenWrt on MT7621/MT7615N devices with 5GHz problems

For those interested,
Release candidate 6 for MT7621/MT7615 routers available for download.
Click HERE

1 Like

Update: 22.03.0-rc6
D-Link DIR-878 rev. A1

Currently, 4 days, 2 hours of uptime and no screams of anguish from users at testing location. :upside_down_face:

EDIT: Uptime updated


unfortunately for me any version of this firwmare have bad wifi 5 performance, i will continue with stock firmware.

1 Like

Thanks for the feedback.

Just to confirm,
Issue was performance,
Connected, no internet or Address Not Found error(s)?

In my case, after a MINUTES, no hours, or maximum a one hour, the wifi 5 have very bad "performance", in other words, the internet is very slow, and after a while, nothing load, i must disconnect and reconnect to the wifi 5 to have again internet, this in both my phone and my pc, i comment that my wifi pc card is an intel 9260 wifi 5 160Mhz card, then my pc wifi card isn't the problem, anyway, in my phone persist the same, i dont know if in my device appears the message "connected, no internet", never watch if that message appears, but at least for me the problem is the same... if i have very slow/no internet in wifi 5, then is the same problem, with the stock firmware, at leasat the wifi 5 is very stable... other thing, with openwrt, some wifi 5 bands/channels dont works, if i select certain band/channel, the wifi 5 stop working, only works with certain bands/channels...

1 Like

Thanks for the feedback.

Running rc6 on EA8100. So far no issue and Wifi strength seems good! (21.02.03 was not too good).


if anyone is still having trouble with it saying connect & no internet
try temperately turning off "Enable SYN-flood protection"
under Firewall>General Settings
is seems to still suffer missing packets for a bit but then at lest fixes itself
just seeing if it's the same for others


I started having daily issues with 22.03.0-rc4 after I managed to install home assistant on the newifi d1 router. HA takes quite a bit of cpu resources to even run. Compiled 22.03.0-rc6 from git now 5 ghz still goes down if it is under heavy stress(mjpg_streamer for a 3d printer webcam takes alot of traffic). So I just cut the 12V power input cable and did a extremely shady job of stealing power for 120mm fan to cool the router. Sorry router but my patience is starting to end. So I am now testing if this is a over heating issue. I found out that I can bring the 5ghz wifi up again without rebooting by changing the bandwith 20mhz, 40mhz, 80mhz until it works again. Implication being that it would be possible to make a very simple script that wiggles the wifi back up whenever it fails effectively making the hole issue manageable. As I recall some people have had issues where it is impossible to connect to the router even if it is up, that is a different story.

BTW, I moved to compiling from sources in hopes of having move of a rolling release instead of resetting the setting every time. Getting configured is a fairly lengthy process.

Just got MIR3Gv1 today, plan to replace MIR3P this evening.
Current: MIR3P 19.07.10, wireguard, ksmbd, vsftpd, minidlna
New: MIR3G 22.03-RC6, wireguard, samba4, vsftpd, minidlna, 802.11s, DAWN
Will report back.

this is a bad idea.

Well, I had to swap to MIR3G because I cannot directly upgrade MIR3P from 19.07.10 past 21.02 without losing configuration.
Seems MIR3G is enough for my usage.
Plan to upgrade MIR3P too and switch it back in a few days.

Forgot to disable ipv6. I cannot remember last time when disabling it did not solve some issues.
I have always just used the first block of

uci set 'network.lan.ipv6=0'
uci set 'network.wan.ipv6=0'
uci set 'dhcp.lan.dhcpv6=disabled'
/etc/init.d/odhcpd disable
uci commit
/etc/init.d/network restart

In the year 2525... ipv6 will work out of the box...

ipv6 works well here :slight_smile:
can't wait until they kill ipv4
so many NAT problems just vanish

The issue this time was that the access point was up but I could not ssh neither my orangepi pc running armbian or rk3318 tv box also running armbian using the dhcp .lan name. So I connected eth to the rk3318 box and found wifi connected to the AP. Perhaps I am wrong about the ipv6 thing. I do find it little hard to believe that ipv6 would still have issues on fresh armbian releases. Perhaps it was the network restart that actually did the trick. So is this way of failing just another way wifi can fail on this device?

BTW, the rockchip rk3318 armbian support is at quite impressive stage these days. The situation with openwrt being designed to run on low resource systems is becoming increasingly strange when you can get a quadcore arm cpu, 4gb ram, 32gb emmc for less than 50 euro. Unfortunately these boxes only have one eth which is not ideal for theoretically running openwrt.

Yes I have had problems accessing SSH via the MT761N
but via another access point it works fine