Kong pro firmware for IPQ806x (R7500, R7800, EA8500, ...)

Check https://git.kernel.org/pub/scm/linux/kernel/git/sforshee/wireless-regdb.git/tree/db.txt if 160Mhz is allowed for channel 100 according to your country setting. You can also look at the dmesg output to see if it complains about some invalid settings.

If nothing is wrong with the flash, then it should allow you to switch from any openwrt firmware, in case of breaking changes in major upgrades a warning would appear, that an upgrade without loosing settings is not possible, but it would still allow you to force a flash. If you see no such message and flashing fails it could be due to a bad filesystem, or corrupt upload through unstable wifi etc., if you are already uploading the firmware via cable check the sha256 sum, to make sure the downloaded firmware is complete.

If nothing helps you can backup your config and upload via tftp. To do this, press reset button, power on the device while still holding the reset button for 15s, after the 15s the power led should blink white indicating, that tftp server has been started on the router, then you can tftp to default router ip.

1 Like

No such message at all. It starts flashing and then restarts a couple of minutes later with no clue whatsoever there was an error during the process. It doesn't look any different than a normal reboot.

Anyway thanks, I think I'll try tftp.

hi @KONG
any ETA of when you will update your 23.05 NSS build to the latest 23.05 stable build?

I appreciate your work, thanks!

Make sure you don't enable software offloading under firewall tab, this would interfere with nss. I should probably remove that option in nss builds.

Unfortunately, some users (like me) who upgrade from non NSS builds to NSS build while preserving settings might still have software offloading enabled from the non NSS build. With the options removed from luci we're stuck with it turned on if we don't know how to ssh and use uci.

Can we somehow continue to display that option in the UI but only allow it to go from on to off? (and disable from off to on)

I found out it's still turned on by SSHing to the router and running:

uci show firewall | grep flow_offloading

It showed:


(1 means on, 0 means off)

I turned it off via:

uci set firewall.@defaults[0].flow_offloading='0'
uci set firewall.@defaults[0].flow_offloading_hw='0'
uci commit
/etc/init.d/firewall restart

On a related note: are there any other settings we should make sure are updated when moving from non-NSS to NSS builds? I would prefer to not have to reset everything.

That said, I do seem to be getting slower speeds with firewall.@defaults[0].flow_offloading='0' vs '1'. 600 mbps vs 1gbps on the NSS build. So I'm a bit confused about the best settings.

I have three R7800s, 1 router and 2 APs. I just updated to the latest KONG nss build. Before I realized you are not supposed to configure SQM thru the GUI, I setup the GUI with my answers for my internet provider.

I also understand the scripts and SQM is built in to these builds.

Question... How and where do I actually edit and configure the SQM scripts on this build?


I just updated my R7800 to the latest NSS build (r0+23573-4dd4465). So far so good. Thanks @KONG

1 Like

Kong is still active or not?

Looks like a new build as just gone up

Big thanks Kong

I use dns.adguard.com in my Android phone settings to block ads, and it worked seamlessly on DD-WRT.
However, with OpenWrt (KONG 23.05 NSS), I encounter an issue – no internet on my Android phone unless I disable the private DNS provider. Can you suggest any changes in OpenWrt options to resolve this? I'm a civil engineer, so for networking I prefer straightforward instructions with minimal programming and more GUI adjustments. I appreciate your help!

It's an R7800, connected via a LAN cable to the main router. I also use a WireGuard client, but removing the WireGuard interface doesn't fix the problem.

Edit: The issue only occurs with Kong build even on default settings. Tried the standard OpenWrt build 23.0.5 and I didn't face that issue: [Solved]My phone private DNS provider not working with Openwrt

Info regarding 22.03 builds. I'm soon going to stop providing 22.03 builds as 22.03 support is about to end. I tested upgrade from 22.03 to 23.05 without reset. I didn't face any issues. Make sure you save your config prior to upgrade, if something goes wrong you can roll back.

1 Like

Hi, I can't install KSMBD server, could You please rebuild your packages with the current kernel.

Collected errors:
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.15.148-1-d24432fe8923a07c0e0fad276e720c53) for kmod-fs-smbfs-common
 * pkg_hash_fetch_best_installation_candidate: Packages for kmod-fs-smbfs-common found, but incompatible with the architectures configured
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.15.148-1-d24432fe8923a07c0e0fad276e720c53) for kmod-fs-ksmbd
 * pkg_hash_fetch_best_installation_candidate: Packages for kmod-fs-ksmbd found, but incompatible with the architectures configured
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for ksmbd-server:
 *      kernel (= 5.15.148-1-d24432fe8923a07c0e0fad276e720c53)
 * opkg_install_cmd: Cannot install package ksmbd-server.

Did you run opkg update before trying to install? I just had a look at the package dir, they should be up to date.

Yes, I did.
Message from LuCI: The installed version of package kernel is not compatible, require 5.15.148-1-d24432fe… while 5.15.148-1-2d7f49c2… is installed.

Try again, the packages for the nss build were not up to date

Thank you for your quick reaction. This time, installation went smooth. But unfortunately, another problem occurred. 3.4.8-1 version of ksmbd-server has strange bug, shared files/directories are not visible in root folder of the share. Could you please compile 3.5.1 version? More about it https://github.com/openwrt/packages/pull/23095

I've discovered and reported that issue and you really need the newer version.

Building right now, as I have synced with latest 23.05 you will have to also flash the new build otherwise packages will not match.

New nss build is up.

1 Like

Now everything works like a charm, thanks.