Ipq806x NSS build (Netgear R7800 / TP-Link C2600 / Linksys EA8500)

Hi, thanks for the effort on these builds. Is there any chance that the Google OnHub devices (IPQ8064, an Asus and TP-Link variant but they're pretty similar) could be added into this build system sometime in the future, once time permits?

It's only recently a supported device, it hasn't had support for a stable release yet, but over in the thread for building up support for this device others have got the NSS modules out of your repository working on the master branch OpenWRT with a modified device tree (see dadogroove's google drive link in the post below what I linked, for details on what he, and in turn I did). I've been running builds from it, including one just yesterday, for a bit now and it seems to work well enough - greatly increased performance, maybe one or two reboots in the week or two that I've been running it, which doesn't seem out of line with what some people have reported on other routers using the master branch builds.

Totally willing to test builds - I've got a couple Onhubs so I'm not afraid of screwing up my current setup, and they're really difficult to hard brick, so some testing won't do any harm.

Anyone running on master that is getting random kernel panics while using CT driver with CT firmware? Seems like that the crash logs always refer to paging at a NULL pointer somewhere.

5.15 branch is stable to me.
these features are enabled.


@ACwifidude - Just want to express my sincerest gratitude for all the work you put in to this project over the last several years. I have transitioned all the devices I support over to IPQ807x (Dynalink DL-WRX36), and have moved on from the trusty R7800s. If you ever want a new challenge, could sure use your knowledge over that way. :wink: Cheers my friend.


How is that router going, is it 100% supported?

It’s running great. Everything standard works out of the box. NSS isn’t supported officially (just like R7800), but I’m sure in time a community build will pop up (there’s already work being done on the Xiaomi ax3600 - which is same general hardware). Even without NSS, gigabit wan-lan is achievable. Wifi performance is great as well, but needs NSS for gigabit.

Here’s the support thread for anyone curious…


How does the speed and range of your new device compare to the NSS enabled r7800?

ipq807x is looking good and NSS is starting to take off with that platform. I’ve been watching ipq807x with interest now that it is in master. Waiting to see which devices have good range, good multi-gig support, etc. I’d assume the speed gets a 200mbps jump just going from AC to AX. If the range is good and performance is better across the board, it is tempting!


@ACwifidude Range in my home is improved - definitely - but integrity also seems improved. 2.4ghz is significantly improved and since AX also operates on that band, it really opens up the options. Dynalink has a 2.5gb WAN port, but only gigabit LAN. I’m honestly amazed at how stable it is considering the relative “youth” of the platform with OpenWRT. Much like your NSS builds, for my relatively easy needs it’s completely set and forget. Has a large heat sink, so temps stay nice and low (50-55C).

For $79.99 on us Amazon, it’s a steal.


At risk of an OT tangent, I'll offer my contrary opinion. I don't doubt some are getting good results with the DL-WRX36, but I've concluded OpenWrt support may need to bake a bit longer in the oven to get the best AP performance out of the impressive Dynalink DL-WRX36 hardware specs.

I have a DL-WRX36 and Belkin RT3200 set up as dumb AP's running current snapshots - one on each of two floors in our home (and also tested swapping them out in the same location). I have found DL-WRX36 5GHz WiFi throughput lacking compared to the RT3200 under identical conditions and connecting to Intel ax200 2x2 clients, especially at intermediate to longer ranges.

On balance, I don't feel like I've gained much to date compared to Wave 2 WiFi 5 after migrating to 802.11ax capable AP's.


Oh for sure it still needs maturation. The current IRQ situation needs to be resolved for example. But the right minds are working on it all… and I’m a big believer that it’s going to end up great as it progresses! I haven’t tried the belkin/ linksys to compare to, but I’d imagine as ipq807x progresses it will surpass it simply due to hardware alone.

And yes - I do apologize for any off topic tangents we went off on as well.

1 Like

intel ax200 - r7800 (voxel)
intel ax200 - xiaomi ax6000
I got a 44% benefit from switching to ax.

r7800 NSS will test later


Hi, basic question here as a EA8500 user. I'm looking to update to this ACWifidude's latest 22.03 build from Kong's build based off of 22.052.

What's the best flash sequence to accomplish this? Do I flash factory image or go straight to sysupgrade? Also, do I need to flash any image multiple times (I recall needing to do that before for a prior upgrade). Sorry for the noob questions, trying to avoid headaches later. Thanks.

I use the Serial connection + TFTP on a Windows 10 PC:

Install OpenWRT:
1. PC-Lan set "static IP address"
2. connect EA8500-serial to PC, and use Putty to control
3. connect EA8500-Lan1 to PC-Lan port.
4. disable all PC-virus protections and firewalls
5. prepare TFTP64, copy used factory-code to TFTP64 folder, rename it to openwrt-factory.bin

6. after EA8500 power-on, in Putty press "Enter" immediately, should get:

Updating boot_count ... done

Hit any key to stop autoboot:  0
Write Reg: 0x00000660: Oldval = 0x00140020 Newval = 0x0014007e
Write Reg: 0x0000066c: Oldval = 0x0014005c Newval = 0x0014007d
Write Reg: 0x00000678: Oldval = 0x0014005a Newval = 0x0014007b
...... ......

(IPQ) #

7. then start TFTP64, and fine settings

8. copy and paste the following Putty commands for bank-1 flash:

setenv image openwrt-factory.bin
setenv ipaddr
setenv serverip
run flashimg

(for bank1, flashimg)

9. after succeeded, copy and paste the following Putty commands for bank-2 flash:

setenv image openwrt-factory.bin
setenv ipaddr
setenv serverip
run flashimg2

(for bank-2, flashimg2)


once openwrt is working, upgrade it using sysupgrade.bin code in Luci.

once the device bricked, go back use Serial + TFTP again to repair it.

1 Like

So I need to go thru the serial connection deal all over again even though I'm already on version 22.052? It was torture for me the first time lol.

No don't need it

I don’t have an EA8500, so I don’t know if there is anything special to flashing it.

As long as the partitioning scheme is the same, regardless of router, I have always been successful by sftp-ing the new firmware to the /tmp directory (usually as firm.bin) and then flashing by ssh-ing to the router and running a sysupgrade -i -v /tmp/firm.bin . Never had an issue even when playing with caldata or joining partitions.

sysupgrade -n (not retaining configuration) should do the job quite fine.

I tested NSS Builds on r7800;)
I connected the router through the ports lan, wan to two port nas (2x1gbe). smb3 multichannel enabled.
The best was the build stable (ath10k-ct)
Another test where the sending speed is more than a gigabit

10 meters to the router and between them a reinforced concrete wall (7-10 cm)

stable ath10k worse on reception (56vs122)

Master all were worse.

r7800 Voxel V1.0.2.100SF

I was in a bit of a hurry and forgot to test with one port;)What is the main use case.

May be this is a test with a gigabit connection.

Openwrt stepped over gigabit, so IMHO you can install and try;)


Rebased the 22.03 and master builds today. I'm personally running today's master on my AP's and today's 22.03 on my main router (all r7800's). Seems to be running well (not doing it for any particular reason, just trying them out).

I'll take a look at the onhub with the next build for master. Found that the build system needed another perl package for building openssl packages that wasn't listed on the wiki. Easy fix and master updates are back!


great to hear! Will try out the new master builds!
edit: Running three r7800's with the new master now: solid performance so far! Let's hope for the best on stability too!
edit 2: all are up for 24hours now, so this is promising :slight_smile: Performance is still solid.