is it possible to add prplMesh to the build ? my ISP router does not allow bridge more but supports prplMesh. so I am planning to use openwrt onhub as a mesh node if possible

tried compiling it with prplMesh but it gives .

ERROR: toolchain/kernel-headers failed to build.

Which version of master are you building with NSS or vanilla?

tplink onhub- latest openwrt vanilla , it was my first attempt to compile anything :slight_smile:
atleast I tried, lol, am waiting if someone experienced would make a build with easywrt included

@ACwifidude

Your builds work. Thanks much!

I have the Asus model (2 of them), the factory bin doesn't install. Tried several times. I had to use regular openwrt factory bin for Asus then sysupgrade to yours. Then it worked.

In client mode, I was having 100-160mb, 100% cpu 0 usage; now 330mb 60-75% on cpu 0, 50% on cpu 1 with irqbalance loading to cpu 1 only, hardware offloading enabled.

MasterNSS sysupgrade isn't available for the Asus model? Is it possible to build one. Much much appreciated. I'd love to try it and see if it's even better. (Nonetheless, I might not have a clear understanding of Master vs. MasterNSS for the Asus Onhub).

Thanks much.

Looks like I have a typo in my script to rename the files - all the ASUS builds on my github are all NSS. The files with the “ath10k” in the name use the ath10k driver. The ones without that in the name use the ath10k-ct driver.

I’d turn off the “hardware offloading” and “software offloading” in Luci- NSS hardware offloading is baked in and those checkboxes in luci do not work (actually they could theoretically cause more issues).

Do some testing with speed test or iperf3 with the router as the inbetween (the router should not be the client or the server) - you should see <5% CPU usage with any wired testing. Maxing out the CPU with max wifi testing.

1 Like

Did you scp the file onto the router?

I am struggling to install openwrt on Onhub.
After blinking purple and two beep sound, I pressed DM button. Reboot and then LED ring on Onhub(Asus) shows Green color. I think I need to zero the eMMC. I tried

root@OpenWrt:~# dd if=/dev/zero bs=512 seek=7552991 of=/dev/mmcblk0 count=33
33+0 records in
33+0 records out
root@OpenWrt:~# dd if=/dev/zero bs=1M of=/dev/mmcblk0
dd: error writing '/dev/mmcblk0': No space left on device
3689+0 records in
3688+0 records out

I think I failed. Do anyone help me? The way to be Openwrt user is so hard.

It didn't fail. That's the normal response when zero'ing the storage that way.
Next step is to scp (or winscp) the OpenWRT image to the OnHub, ssh into it, and expand the image to mmcblk0 using dd again.

Don't worry too much about the colours. A better test would be to ping 192.168.1.1 after the unit reboots after the DM button press after the 2 beeps.

Don't try to http into the IP address because there's no LUCI (httpd) setup there yet. When ping replies, then ssh into the unit and write the image to emmc.

if you are using tplink router you can try my build which includes luci and has wifi turned on by default.

Thanks. Following your recommendation, I see exactly what you mentioned:

Wired - Very low CPU usage, negligible.
Wireless - CPU 0 @ 85% , CPU 1 @ 5%-10%

I did turn on and off hard/software offloading just to try. No significant difference, so I leave them off.

I only use Client Mode to connect to my main AX router which has 1GB connection. 330MB is plenty good.

Thanks bud and thanks to everyone! Appreciate all your help and input.

Btw, the Asus onhub turns solid GREEN (not colors mentioned in the wiki) when it has successfully loaded firmware bin from USB. CTRL+D from USB keyboard is necessary to enter Dev Mode (Purple).

1 Like

@Mandupizza

I have the same Asus model x2.

1 was used with 1gb fiber connection - updated to the latest stock firmware before flashing openwrt
1 was never used since purchase, stock firmware perhaps from 5-6 years ago.

Neither needed to zero the eMMC.

df -h and cfdisk /dev/mmcblk0 to see the spaces you have.

You might need to install cfdisk opkg update && opkg install cfdisk

Here's mine:

root@OpenWrt:~# df -h
Filesystem                Size      Used Available Use% Mounted on
/dev/root                10.0M     10.0M         0 100% /rom
tmpfs                   484.7M    840.0K    483.9M   0% /tmp
/dev/mmcblk0p3            3.5G    281.6M      3.2G   8% /overlay
overlayfs:/overlay        3.5G    281.6M      3.2G   8% /
tmpfs                   512.0K         0    512.0K   0% /dev

Konus thank you. I had a heck of a night trying to figure out why I could not get it running again and then I decided to read every conversation and I got you yours and I decided to do the full write to free space and thanks to your advice I might get this thing running again. Thanks a lot :pray: :pray:

1 Like

I would like to thank everyone who worked on this project you are all geniuses and I learned a lot following your instructions here setting up my Google Onhub. If anyone has any problems setting it up there is a lot to be learned in this thread I recommend reading it in its entirety.

I have an ASUS SRT-AC1900 OnHub I'm trying to get OpenWrt working. Still haven't tried to flash it yet, but reading through the messages to learn as much as possible before trying.

My question is, could this OnHub be configured the way Network Chuck configured a Raspberry Pi 4? I was completely successful creating the project Chuck walks us through in this video:

my SUPER secure Raspberry Pi Router (wifi VPN travel router)

Just wondering if the OnHub could do the same thing, maybe without having to install another antenna dongle? The OnHub has several antennas but not sure how OpenWrt addresses that, Chuck sets it up as Radio1 and Radio2 in the OpenWrt setup. Does the OnHub have this kind of hardware already?

FYI, Your latest non-ct build is missing the kmod-ath and kmod-ath10k drivers.

Thanks. Took them down.

Thanks for everyone involved in this project, I am very glad I got my onhub up and running again

OnHub has 3 radios, so yes, you can do it. Not sure if that's the best use for an OnHub though. It's not as compact as the Raspberry Pi, and all its fancy hardware is not likely to make hotel WiFi suck any less. In any case, should you decide to try it, you may want to experiment with connecting different radios to hotel WiFi to see which works best. The result may vary depending on the hotel. Have fun.

1 Like

Wanna reply when you build again? Am interested in mesh working. Have a large apartment so can't be drilling holes through the floor for cables. Works on the non-ct snapshots but can only get about 150 down before cpu usage maxes out. Your builds don't have the performance issues the snapshots do.