asvio@MSI-7D25:~/01-NBG7815/nbg7815-nss$ scripts/diffconfig.sh | grep -E "ATH11K|NSS_|MAC80211|IPQ|-nss"
# CONFIG_ATH11K_DEBUGFS_HTT_STATS is not set
# CONFIG_ATH11K_DEBUGFS_STA is not set
# CONFIG_ATH11K_THERMAL is not set
CONFIG_NSS_DRV_IGS_ENABLE=y
CONFIG_NSS_DRV_SHAPER_ENABLE=y
CONFIG_PACKAGE_kmod-qca-nss-drv-igs=y
CONFIG_PACKAGE_kmod-qca-nss-drv-qdisc=y
CONFIG_PACKAGE_sqm-scripts-nss=y
asvio@MSI-7D25:~/01-NBG7815/nbg7815-nss$
You'll probably run into some warning/error with telephony's Makefile. Edit the Makefile the warning/error points you to and change "libpcre" to "libpcre2" and rerun the step that got you the warning.
Things should compile afterwards. It takes quite a while to compile like qosmio mentioned. Also, make sure you're not root when you run through qosmio's README
Compiled files will be somewhere in bin/targets from what I remember.
Let me know if you find how to add the "netem", "wireguard client", "adblock" and, "sqm" packages to the build. All I did was build whatever qosmio had on his github so I have no idea how to customize things.
@sppmaster, how do you choose which packages to add/etc? I'm new to OpenWrt and am just looking for something basic. Is there a list of packages that most users add or are recommended? Also, would qosmio's build already have those packages configured already?
fork repo, create a file in .github/workflows and run your own builds (all in github). here are sample workflow yaml files from some of Qosimo's forked repos. make changes to your liking.:
All the required packages are preselected so you are able to use the Internet.
Then simply add more packages (make menuconfig) that you might need when you have more experience and needs. It's simple to start.
This is the preferred approach as you let make defconfig automatically select dependencies while keeping your configuration small and repeatable.
Since the web interface will be the primary source people manage their devices, Look through mencuconfig for LuCI applications.
LuCI > Applications
Scroll around to see what you might need.
The base install I have in my example should provide for 95% of what most users use. Since you are new to building OpenWrt and jumping right into building from a fork... keep it simple. More things you add, the greater chance your build will fail to even compile. Familiarize yourself with everything and only then make changes.
i did already add nss for that target but no nss firmware will work on the mx5500. only the linksys provided nss firmware in the firmware works but this is very old and does not support ath11k. if you use any other firmware. ethernet will not work on the mx5500. but i dont know how the mx2000 works here since the mx2000 is shipped with the different nss firmware
my reply can only be that the nss 11.3 shipped with the linksys firmware is the only one which works on mr5500 and mx5500. no official 11.3 works and no official 11.x or 12.x works on this device. they all result in non working ethernet. so the nss firmware by linksys is customized. but 11.3 also has no ath11k support. no wifi acceleration is supported then
after update to newest commit of qosmio's qualcommax-6.x-nss-wifi-6.11 branch, i got kernel panic in several minutes( 30min to 2 hours,not always the same) after reboot.
and I have to change disable-gro=1 to make dnsmasq works.
@qosmio
The exact thing that is happening is when I added an interface using quectel_cellular. When the interface starts with simcard inserted, the modem auto restarts itself.
on mainline openwrt, udp has been acting strange for a couple of months now. i do not know if it's hanging but sometimes udp traffic (most oblivous was dns queries which was served from unbound running on the actual device) originating from the router becomes unresponsive, sometimes very high udp packet loss. i can't put my finger on what is the actual issue. so much so that I stopped using mainline openwrt as a routing platform about two months ago as it was unpredictable and unreliable. this was on a filogic 880 device. I am going to try this patch to see if there is improvement.
Again this has nothing to do with the nss stuff as I only use my ax3600 as dump APs.
been a while since i did some wifi throughput test.
currently building off branch: mx4300-6.11
NSS 12.2 + ATH11K 2.12 + 6.11 backports on AX3600
iperf3 test to a local pc on the lan. AX3600 @80MHz (no point for 160MHz as the ethernet port uplinks are 1Gbps)
D/L : 918Mbps (receiving)
U/L: 866Mbps (transmitting)
Everything looks great so far. Stable too.
@qosmio WG on the router is suddenly extremely slow while speed is normal when connecting from another device connected by ethernet. Could this be the UDP patch?
the line you have highlighted has a script with defaults that this user wants when the router boots up after flashing (runs the first time and sets things up accordingly). could be that, they want it to be an AccessPoint and want it to get an IP from upstream DHCP server because they may not be physically present near it to connect via LAN ports for flashing builds etc. it is equivalent of files under nss-setup/example (those are sophistication which you can worry about later once you get familiar with running successful builds and are able to flash without issues).
to specifically answer: you can remove the 2 lines and run the workflow and it would generate a .bin file which you can check under 'Releases' section.
@qosmio I'm not sure if I should ask it here, but, NSS-enabled builds on my WRX36 has WiFi issues when my main bridge is vlan filtering enabled. Phone throws authentication error even though password is correct. Even WPA3 owa throws errors. Open network works.
Tried hacking a veth based bridge to bridge solution, it works with 20mbps speeds