Feel free to download my builds from here. They are exactly the same builds made using dadogroove's instructions, but with LUCI SQM app already included.
2 Likes
I put up new builds yesterday. I tested it on my TP-Link OnHub and it worked just fine. The drivers are included. Sorry for that, I was messing around with the diffconfig file. I thought I tested those before uploading. Also, my builds do have SQM included but need to be set up for individual situations.
2 Likes
@dadogroove can you test adding easy mesh option for your build please.
I tried to follow instructions on their page but failed to build it
Thanks in advance 
1 Like
Iām trying to recover sunk costs. Google forced a factory reset at end of life and you got a nag message that could not be deleted if you didnāt remove it from your Google Home setup. So now Iām just tinkering with OpenWRT so itās not junk. Amazon will pay you $4 to recycle it. I never got the offer to upgrade to new hardware. So, Iām going to see if I can make it dance a little.
The Raspberry Pi project was quite cool. Full router and automatic VPN. I use it at home for streaming other countries video. No DNS leaks. Network Chuck got me interested. Curious if the OnHub CPU will run all the same Linux commands the same way. If I can get this working like the Pi, I can integrate it into my home video setup and travel with the Pi.
It would be a whole lot better if Google just let us use some legacy app to keep using it as a router. Not sure if OpenWRT can utilize all the fancy OnHub hardware. Hoping it will.
Can you make a video about installing openwrt on Onhubā¦.thereās no video in YouTube about that.Iām not a developer so most of things you guys talk about goes right above my headā¦.where I can find more easy step by step process so I also can install openwrt on my TP-Link onhubā¦this forum is my last hopeā¦..plz help
I think I have almost done but it is not working
Does anyone explain what I missed?
I followed final step(13)
ssh root@192.168.1.1 -C "dd if=/dev/zero bs=512 seek=7552991 of=/dev/mmcblk0 count=33 && \
dd if=/root/openwrt-ipq806x-chromium-asus_onhub-squashfs-factory.bin of=/dev/mmcblk0 bs=1M"
33+0 records in
33+0 records out
20+1 records in
20+1 records out
cfdisk /dev/mmcblk0 to see the spaces I have and it is the same as zuzu have (df -h is similar but little different).
Filesystem Size Used Available Use% Mounted on
/dev/root 4.3M 4.3M 0 100% /rom
tmpfs 484.7M 76.0K 484.6M 0% /tmp
/dev/sda3 3.5G 303.0M 3.2G 9% /overlay
overlayfs:/overlay 3.5G 303.0M 3.2G 9% /
tmpfs 512.0K 0 512.0K 0% /dev
I command "reboot" to reboot and then Onhub's ring start blinking purple and beep twice.
Is it correct?
If I press DM button, Onhub ring shows green color and I can't connect 192.168.1.1 (I checked no IP address for the router. -Undefined network ).
If I do not press DM button, Onhub reboots (turn off and blue ring) and shows red and orange colors repeatedly. The router is not connected to my computer.
anyone else having issue with Tx Rx rate dropping significantly randomly on WiFi ?
I think that you are almost there. You need to remove the USB stick after the reboot command so it can boot from the internal image that you transferred to it. I usually just pull the power plug after the transfer process completes.
ssh root@192.168.1.1 -C "dd if=/dev/zero bs=512 seek=7552991 of=/dev/mmcblk0 count=33 && \
dd if=/root/openwrt-ipq806x-chromium-asus_onhub-squashfs-factory.bin of=/dev/mmcblk0 bs=1M"
33+0 records in
33+0 records out
20+1 records in
20+1 records out
Then remove the USB stick and power it back up. After the purple blink, 2 beeps (do NOT push the DM button) and then the green LED. OWRT should be running from the internal eMMc.
So I feel pretty stupid now. I meant that @ACwifidude latest non-CT build was missing the drivers. His build has been working pretty good performance wise, the NSS definitely seems to improve stability and performance.
Curious about your builds now. Do yours also implement NSS? Is the Google Drive link from previous posts where your most up to date builds are?
I didn't watch the Network Chuck video in its entirety, but I don't think he's using any exotic features that OnHub doesn't support. Perhaps the only concern is that using VPN on the OnHub may slow down your connection because OnHub may not have enough horsepower to encrypt and decrypt your traffic at full speed. Other than that, it should work.
1 Like
Please look into your tplink onhub latest non-CT build, wifi does not show up !
Thanks
No worries. Yes, my builds have the NSS cores enabled. I have also added the necessary packages to use the bluetooth radio, but I have not had luck setting it up. I tried awhile ago but just haven't gotten back to it again. The google drive link will have the latest builds that I have made. There are also instructions to replicate the builds if you need to add other packages to them, especially kmods which can't be added after the builds due to adding the necessary packages for the NSS cores to function. Opkg will complain of an incompatible kernel. It is possible to add some packages if they do not have any dependencies too deep into the build structure.
Thanks, @dadogroove
As you said, the router is booting from the eMMC with green ring but network interface does not come up. After zeroing to eMMC before flashing, the router is booting from the eMMC and shows IP address.
I have last problem. I can't access 192.168.1.1 on web. I think it need to install luci
opkg update
opkg install luci
Installing luci (git-23.051.66410-a505bb1) to root...
Downloading https://downloads.openwrt.org/snapshots/packages/arm_cortex-a15_neon-vfpv4/luci/luci_git-23.051.66410-a505bb1_all.ipk
Installing libnl-tiny2023-04-02 (2023-04-02-11b7c5f0-1) to root...
Downloading https://downloads.openwrt.org/snapshots/packages/arm_cortex-a15_neon-vfpv4/base/libnl-tiny2023-04-02_2023-04-02-11b7c5f0-1_arm_cortex-a15_neon-vfpv4.ipk
Collected errors:
* pkg_hash_check_unresolved: cannot find dependency kernel (= 5.15.106-1-d514712ac7e2f4a0cb59d3777311f40c) for kmod-nf-reject
* pkg_hash_check_unresolved: cannot find dependency kernel (= 5.15.106-1-d514712ac7e2f4a0cb59d3777311f40c) for kmod-nf-reject6
* pkg_hash_check_unresolved: cannot find dependency kernel (= 5.15.106-1-d514712ac7e2f4a0cb59d3777311f40c) for kmod-nf-log
* pkg_hash_check_unresolved: cannot find dependency kernel (= 5.15.106-1-d514712ac7e2f4a0cb59d3777311f40c) for kmod-nf-log6
* pkg_hash_check_unresolved: cannot find dependency kernel (= 5.15.106-1-d514712ac7e2f4a0cb59d3777311f40c) for kmod-crypto-crc32c
* pkg_hash_check_unresolved: cannot find dependency kernel (= 5.15.106-1-d514712ac7e2f4a0cb59d3777311f40c) for kmod-nft-core
* pkg_hash_check_unresolved: cannot find dependency kernel (= 5.15.106-1-d514712ac7e2f4a0cb59d3777311f40c) for kmod-nf-flow
* pkg_hash_check_unresolved: cannot find dependency kernel (= 5.15.106-1-d514712ac7e2f4a0cb59d3777311f40c) for kmod-nf-ipt
* pkg_hash_check_unresolved: cannot find dependency kernel (= 5.15.106-1-d514712ac7e2f4a0cb59d3777311f40c) for kmod-ipt-core
* check_data_file_clashes: Package libnl-tiny2023-04-02 wants to install file /usr/lib/libnl-tiny.so
But that file is already provided by package * libnl-tiny2022-11-01
* opkg_install_cmd: Cannot install package luci.
I can install cfdisk but can't install luci. I have no idea to install luci.
Does anyone let me know how to install luci?
Thank you for your contribution. I already flashed with your build and it is running perfectly. But once I tried to install Wireguard via Luci, I got this warning message.
" * The installed version of package kernel is not compatible, require 5.15.106-1-d514712aā¦ while 5.15.105-1-5487c3f5ā¦ is installed."
Is there any way I can fix that and can install Wireguard? TIA
@dadogroove I am using your NSS build and tried to enable nss core via luci-sqm-script - after selecting fq_codel" as discipline , "nss-rk.qos does not show up !
I am using openwrt as wireless bridge using relayd.
You need to follow his instructions to add it. I do not include it in my builds because he updates it periodically and I feel it is up to people to keep those things up to date.
1 Like
All I can think of, is that the image that you flashed is older than the most recent master image. New master images are generated every day. The kernel hash changes every time a build is generated. If you install yesterday's master image and try to install luci from today's master software repo, you will get the kernel error.
You can't add Wireguard to an NSS build from LUCI. You have to either use a stock build or make your own NSS build with Wireguard included at build time. I'm not sure if the latter makes sense though, because using a VPN may negate the performance benefits of the NSS cores. It would be interesting to see if the NSS build with a VPN is any faster than the stock build with the same VPN, but I don't have time for such experiments.
1 Like
I agree, using wireguard or similar VPN via the router negates any speed increase from NSS. Unfortunately NSS doesnāt improve VPN speed any. You basically have the same speed as non-NSS builds. I include VPN options in my builds but donāt use them myself.
2 Likes
if I use my router as wireless bridge , should I use br-lan to enable nss cores ?
it seems it will only work for eht0/1
"Only works with eth0/eth1 and the fq_codel queue discipline."