You mean as in this goes too deep as a starting point?
I know I have a LOT to learn and I'm fine with that; I see this as a long term project. I may not understand everything fully what I've read so far in this thread (now), but I've already picked up several useful bits. Usually when I've learned more, pieces that I didn't (fully) understand before, will fall into place later.
I have several objectives. One is getting a more secure router by amongst other things run a (more) recent and still supported kernel (instead of 3.4.103). Another is showing the power of Open Source and OpenWrt seems like the best project to do that with (when it comes to routers). My assumption is that I'd also need IPQ806x NSS drivers to get good performance, which I of course want (if possible).
If I can help get my router into a supported state with OpenWrt, that would be really cool
Not really. It doesn’t contain information on how to get an ipq806x router running OpenWrt. It assumes OpenWrt is already running properly before attempting NSS. So applying the knowledge in this thread on a router without OpenWrt running will likely be confusing.
I've been following this even though I'm from a different party called IPQ807x, and I have a doubt and maybe you guys can enlighten me.
Do all these offloading packages have support for nftables?
Since openwrt is migrating away from iptables for good, is there a way to make this work with nftables? I've seen most of the dependencies have to do with conntrack which is the same for iptables and nftables, but it also has some dependencies on iptables-mox-extra, that should be replaceable with nftables right?
Also, for the TC offloading, could there be a way in the future of adding cake offloading? Is this TC offloading currently transparent? Or is there a need to use a special nss tool?
I realize it's quite an old post, but I didn't see someone reporting who was running OEM firmware ... and I am. It's an Asus BRT-AC828 (unsupported by OpenWrt (currently)) running asuswrt (although that isn't relevant afaict).
Regarding the spinlock error when running br-lan in promisc mode.
I checked the boot log from the OEM firmware, it seems like the bridge (actually all interfaces) is set to promisc mode. So it's a default setting in OEM FW. But for some reason it doesn't work in the OpenWrt NSS implementation/port.
Everything that can be wired - I have it wired. Ex: Linux box, access points, etc
IoT = Amazon Smart thermostats, Alexa speakers, cameras, and other similar devices that only require an internet connection (these connect to the slower 2.4ghz only SSID). I went with mostly Amazon smart devices to stay under one smart device umbrella.
My iPhone, iPad, and other similar “fast” devices use the 5ghz only SSID. I have Apple devices to keep the family happy.
I keep my settings simple and run all the optimizations I have in post #2 of my build thread. I’ve found ath10k-ct has worked just fine with no significant disconnects or issues.
