Find a good midrange 802.11ac WiFi Router for OpenWrt

Unfortunately, the ADSL hardware situation is not great. There are a few devices that can run OpenWrt, but I believe none of them are currently being sold. If you can find one, second hand, that would be a good way to go. However, you will most likely just have to find a new device that is still actively supported and accept that it has a closed firmware.

What country do you live in? It may help to identify what type of DSLAM you will be connecting to. ADSL modems that use a Broadcom chipset often provide the fastest and most reliable connection, but it depends on the DSLAM.

If you buy one of the TP-Link modems, make sure you get the latest hardware revision; they have a history of releasing new versions and abandoning the previous one, in terms of firmware updates. Last time I looked, the TP-Link modems all used TrendChip chipsets.

Personally, I would get the cheapest Draytek router I could find and put it in bridge mode. In my experience, Draytek do a better than average job of providing firmware updates.

Alternatively, if you don't mind double NAT, you can continue using your FritzBox and just connect your new AP to it.

On a separate note, if you are paranoid about products from Google and Amazon, you should probably be even more paranoid about products from companies like TP-Link, IMO.

If you go for the two device solution (adsl-modem + new router / aDSLrouter + new router) and you also want to be future proof, you might wanna check out devices that support Wifi 6 (ax). Wifi 6 promises enhanced stability and lower latency. On paper, Totolink x5000r seems a nice option if you look for "mid-range". In Germany, you can get it for as low as 60€, but since these ax devices are pretty "new", there is a risk of running into unknown bugs of course. I checked Github for bug reports and would advice to run the snapshot, rather than 21.02 stable.

That model has similar board layout as DIR-878, DIR-882, DIR-2640 ...
Reference

You can refer to the current discussion about 5GHz WiFi issues at GitHub

I ran into the 5 GHz bug mentioned at GiHub approximately four? days ago using a fairly recent snapshot release.
I stopped testing/using stable releases since I encountered 5 GHz WiFi issue in matter of hours compare to snapshot releases, which can last days before bug appears.

Keep in mind, common simple workaround is to release switch to 2.4GHz then switch back to 5GHz immediately. Simple enough to do with android phones and what not. However, rather annoying if users have to conduct the same procedure with their wireless connected media/streaming box(s) and/or smart tv(s)... :angry:

Thanks for the references.
But the issue reported is for mt7613/mt7615

Hostname OpenWrt
Model D-Link DIR-2660 A1
Architecture MediaTek MT7621 ver:1 eco:3
Target Platform ramips/mt7621
Firmware Version OpenWrt 21.02.2 r16495-bf0c965af0 / LuCI openwrt-21.02 branch git-22.046.85957-59c3392

So am i missing something here? is mt7621 equivalent to mt7613/mt7615?

Though, i do see a report for a different model with same chipset as DIR-2660
But strangely i dont see any issues in 5Ghz wifi for 4-5 of my connected clients since the last 3 weeks of uptime of my DIR-2660.
Is it that the issue is only faced at a specific configuration which i havent used yet?
I use Channel 48 (5240 Mhz) Width 80 MHz for my 5Ghz wifi.

Users who want to buy mediatek devices - just read this:

About mt76 - only mt7615 and mt7915 support is acceptable, as development is still active. For all other devices, mt76 is a piece of sh*t (random freezes, disconnections, bad performance and even worse support). If you are not interested in details - just check number of open issues for mt76 driver, how old are they and how responses look like.

OEM drivers is the opposite - ugly coding, but good performance and stability

MT7621 your CPU and Ethernet switch. There are no WiFi circuits on the MT7621 chip. A MT7621 based ac router will have a MT7612, MT7613, or MT7615 as its 5 GHz wifi chip.

1 Like

Thanks for this knowledge.. so as per this dmesg output do i have "MT7615e" wifi chip ?

dmesg | grep -i mt76
[    0.000000] SoC Type: MediaTek MT7621 ver:1 eco:3
[    0.809979] mt7621_gpio 1e000600.gpio: registering 32 gpios
[    0.821283] mt7621_gpio 1e000600.gpio: registering 32 gpios
[    0.832538] mt7621_gpio 1e000600.gpio: registering 32 gpios
[    0.924779] mt7621-nand 1e003000.nand: Using programmed access timing: 31c07388
[    0.974146] mt7621-nand 1e003000.nand: ECC strength adjusted to 4 bits
[    0.987180] mt7621-nand 1e003000.nand: Using programmed access timing: 21005134
[    1.001754] mt7621-nand 1e003000.nand: Using programmed access timing: 21005134
[    1.673323] 9 fixed-partitions partitions found on MTD device mt7621-nand
[    1.686853] Creating 9 MTD partitions on "mt7621-nand":
[    2.303201] mt7621-pci 1e140000.pcie: Parsing DT failed
[    2.527062] mt7621-pci-phy 1e149000.pcie-phy: PHY for 0xbe149000 (dual port = 1)
[    2.542019] mt7621-pci-phy 1e14a000.pcie-phy: PHY for 0xbe14a000 (dual port = 0)
[    2.656631] mt7621-pci-phy 1e149000.pcie-phy: Xtal is 40MHz
[    2.667753] mt7621-pci-phy 1e14a000.pcie-phy: Xtal is 40MHz
[    2.778653] mt7621-pci 1e140000.pcie: pcie2 no card, disable it (RST & CLK)
[    2.792527] mt7621-pci 1e140000.pcie: PCIE0 enabled
[    2.802257] mt7621-pci 1e140000.pcie: PCIE1 enabled
[    2.811989] mt7621-pci 1e140000.pcie: PCI coherence region base: 0x60000000, mask/settings: 0xf0000002
[    2.830719] mt7621-pci 1e140000.pcie: PCI host bridge to bus 0000:00
[   23.668108] mt7621-pci 1e140000.pcie: bus=1 slot=0 irq=23
[   23.690203] mt7615e 0000:01:00.0: enabling device (0000 -> 0002)
[   23.720205] mt7621-pci 1e140000.pcie: bus=2 slot=1 irq=24
[   23.734495] mt7615e 0000:01:00.0: HW/SW Version: 0x8a108a10, Build Time: 20180518100604a
[   23.742449] mt7615e 0000:02:00.0: enabling device (0000 -> 0002)
[   23.870488] mt7615e 0000:02:00.0: HW/SW Version: 0x8a108a10, Build Time: 20180518100604a
[   24.084220] mt7615e 0000:01:00.0: N9 Firmware Version: _reserved_, Build Time: 20200814163649
[   24.084280] mt7615e 0000:02:00.0: N9 Firmware Version: _reserved_, Build Time: 20200814163649
[   24.168403] mt7615e 0000:01:00.0: CR4 Firmware Version: _reserved_, Build Time: 20190121161307
[   24.168565] mt7615e 0000:02:00.0: CR4 Firmware Version: _reserved_, Build Time: 20190121161307

Yes you do.

The hardware data page for the D-Link DIR-2660 A1 shows MT7615N -

1 Like

The driver for the 21.02.2 kernel lists MT7615e -

BusyBox v1.33.2 (2022-02-16 20:29:10 UTC) built-in shell (ash)

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 OpenWrt 21.02.2, r16495-bf0c965af0
 -----------------------------------------------------
root@OpenWrt:~# opkg list | grep MT7615
kmod-mt76-connac - 5.4.179+2021-12-03-678071ef-4 - MediaTek MT7615/MT79xx wireless driver common code
kmod-mt76-sdio - 5.4.179+2021-12-03-678071ef-4 - MediaTek MT7615/MT79xx SDIO driver common code
kmod-mt7615-common - 5.4.179+2021-12-03-678071ef-4 - MediaTek MT7615 wireless driver common code
kmod-mt7615-firmware - 5.4.179+2021-12-03-678071ef-4 - MediaTek MT7615e firmware
kmod-mt7615e - 5.4.179+2021-12-03-678071ef-4 - MediaTek MT7615e wireless driver
kmod-mt7921-common - 5.4.179+2021-12-03-678071ef-4 - MediaTek MT7615 wireless driver common code
root@OpenWrt:~#

@tmomas might be able to explain the differences in what's listed on the hardware data page, and what 21.02.2 is using.

The dataentry is based on the git commit which shows MT7615N.

1 Like

Is that actually true? I thought "modem-mode" was removed but pass through is still there, so "all" one needs to do is not to configure the fritzbox itself with the correct PPPoE credentials (preferable no credentials at all) and click the "Angeschlossene Netzwerkgeräte dürfen zusätzlich ihre eigene Internetverbindung aufbauen (nicht empfohlen)". box... Which should result in working PPPoE passthrough. But that only helps if the OP actually uses PPPoE .

True, but if your ISP uses PPPoE you really do not need a true bridged-modem configuration, it should be enough to enable PPPoE pass trough while not configuring user and password for the router itself (this was reported as working for users of recent FritzBox's as of last year). You still will need to deal with potential VLAN issues.

I would probably try that first because:
a) newer DSL routers put emphasis on the VDSL2 part and the ADSL part is not that relevant anymore so sees few updates
b) you have that device already so testing should be quick and easy, once you have a new OpenWrt router... (such a setup also allows to place the "modem" as close to the socket (TAE?) as possible to reduce additional extension cords, and to place the router optimally for the WiFi coverage, you will need an ethernet cable between modem and router though :wink: )

But maybe you could tell us which ISP and country we are talking about here?