Thanks. I found that build after looking around for a long time then literally the second after I asked there it was. My other question is does the setting, "software flow offloading" need to be enabled or is the functionality baked in and always on? In the web interface the hardware option can't be enabled or accessed without also having software offloading enabled. Is that supposed to be how it works?
Keep the software offloading button turned off. NSS is baked in and just works. 
1 Like
Build your own and switch to non-ct
@KONG updated nss build to 15615 and then tried to install curl from your package repo but it's not listed anymore.
Thank you.
1 Like
I recently switched over from Hnyman build to Kong NSS....curious on my startup script and if I still need it. Running scaling freq (ondemand) and irqbalance.
thxs
2 Likes
I see a new build with today's date 03/03/2021, any idea of what changed?
Changelog...
? Must be there..
If I'm looking at the right log, last entry is from 2019.
You're right.
Anyway there are a lot of changing right now in the master, but I think you are using the 19.07 branch?
Maybe he upgraded to 19.07.7 , if he was on 19.07.6?
Maybe you can check the manifest ...
Anyway, it takes 30 sec to flash, not a big deal.
Yea that's his personal log, for regular build changes just look at the OpenWrt github.
1 Like
I tried last build on my R7500v2 and followed the instructions on this post to setup my Getflix smart DNS (to stream US content from my location) but it didn't work, do anyone have same issue? This works in an older tp-link router with OpenWrt 18.06.9.
1 Like
For anyone curious, I tried Kong's 2021-03-03 and 2021-03-14 builds and could not make the smart DNS work, but they work fine in official build 19.07.7 just setting the "Custom DNS Servers" in the WAN interface, so I'll stay with this version for now.
Just updated my R7800 to the latest Kong build coming from the prior version, so Sysupgrade method.
All looks good and QoS seems to work even better. Kong does not publish a clear changelog, unless you consider the Manifest file to be informative.
On bufferbloat tests with DSL Reports and Waveform, Cake QoS seems to hold up even more nicely with A+ results across the board. There is no other firmware for the R7800 that I see these results with. The graphs on DSL Reports for example are flat as a pancake, even when running a "gigabit" test on my cable line.
Find the files here: http://desipro.de/openwrt/19.07/
Thanks Kong!
Updated this morning all working as it should for me on my r7800 only thing for some reason Ad block was missing so had to install
Yes, the latest build is now stripped down a bit, some prefer a leaner build and load the rest from the package repo. I also polished my dark material theme.
3 Likes
@KONG Speaking of repos, any chance you could add FRR (for BGP routing) into the repo (not the image)?
It will be included in the nss build, since package feed for 19 does not come with frr, but in trunk feed it is.
1 Like
Cheers for the info was thinking something had gone wrong when i did a update so also did a full install which was the same so was thinking you may had changed something
PS never got on with the dark theme as find some items hard to read so always swap to Bootstrap
@KONG For what it is worth, I loaded your 09/04 firmware with non-ct wireless drivers (I assume that was the main reason for an update since yesterday?), and instantly had a few IoT type devices and cameras drop off my network. Can't get them back on. Reloading 08/04 firmware and no issues at all.
I'm responding to a an answer from @KONG in another thread:
Can you share with me which build you are using (download location/build-/version number)?
I have around 12 WiFi devices connected mostly the same time and we're also working from home. I have a mix of macOS 10.15.7, Windows 10, iOS 14.4.x, Android 8, Chromecast 2, and some Shelly devices connected to either 2.4GHz or 5GHz (whichever is automatically selected by the client).
From what I see on unsuccessful reports on -ct there's mostly an Apple device involved. Or a range of Apple devices. If you're not seeing issues with the -ct driver/firmware, can I ask if you have Apple devices on your WiFi network?
Thanks in advance