Qualcommax NSS Build

I have a same issue, too.

First try to run below commands from SSH and see if nlbwmon will start working.

rmmod nf_conntrack_netlink
modprobe nf_conntrack_netlink

Then if it works put the below commands in the startup file (rc.local).

rmmod nf_conntrack_netlink 2>/dev/null
sleep 1
modprobe nf_conntrack_netlink

Just fork my repo. Dont bother with WSL

3 Likes

I got all two mx4300 on openwrt. Now I’m wondering how do I set up mesh now?

With wired backhaul. Best performance

2 Likes

Thanks for the effort.
Works great on the GL.iNet Slate AX, PPPoE over 700Mbit (mainline did 450), Wi-Fi Mesh crashes the radio randomly, WDS works without full transperency (no IPv6/multicast).
Wi-Fi offloading works well (low CPU usage), the upload is higher than mainline, download is about the same.
Build with upnp and librespeed added

The stock glinet firmware suffers from the same issues with mesh/WDS as well, I havent tried the experimental NSS FW.

OpenWrt mainline with batman is the most stable for home mesh setup on this hardware, otherwise the NSS build is better for wired backhaul.

1 Like


AW1000 build with 24.10-nss branch is failing. Anybody else having this issue?

1 Like

Is everyone using main-nss or 24.10-nss?

I think vnstat2 broke the flash on my AW1000. Luckily I enabled USB boot beforehand so I can still boot from a flash drive

Still not able to install dawn due to libubox conflict

ERROR: unable to select packages:
  libubox20251004-2025.10.04~c163d7ab-r1:
    conflicts: libubox20251103-2025.11.03~e357be61-r1[libubox=2025.10.04~c163d7ab-r1]

Seems to be related to https://github.com/openwrt/openwrt/issues/20582

Is there a fix for this other than building and flashing a new image?

Also @AgustinLorenzo I noticed your package repo https://openwrtdata.agustinls.com/ is down due to Preparing repo for unified version, any ETA for when it'll be back?

Fwiw, I managed to compile qosmio 24.10 by checking out an older hash version from a month ago. Your mileage may vary and always check the src and only trust what you want. Never just cut and paste code you don’t understand. Also, because feeds.config.default points to the head of openwrt.org repo, you are subject to anything upstream that may break your build. If you are brave, you can put known good hash in feeds.config.default lines.
You have been warned and don’t expect someone to solve your problem. Everyone here shares their experience and share what they know.

Do not continue If you are using main-nss branch, unless you want to build 24.10 branch with older hash.

Follow github qosmio repo quickstart instructions on 24.10-nss steps: right after step 1. Insert these steps before continuing step 2.

$ git show 164fc5a971 (I got this from my last known nss build version line on the router status screen OpenWrt 24.10-SNAPSHOT r29031-164fc5a971 / LuCI openwrt-24.10 branch 25.280.58391~b7e4a9c)

use the full hash line on the checkout

$ git checkout 164fc5a971281ec9261303a2b7fae868c61d03ff

If git show or checkout step failed, you are out of luck. I have no idea where your git source is from or how your branch is different.
Continue with qosmio quickstart step 2 if git checkout is successful..

IF you have already git the current HEAD and try to build and failed.
You might need to save your .config and wipe all toolchain and image build staging files by doing distclean

$ make distclean

Then $ git checkout 164fc5a971281ec9261303a2b7fae868c61d03ff and so on.
Warning: distclean will delete .config. If you didn’t save it.. you will need to build a new .config for your board(s)
Good Luck.

If you don’t understand any of these, get the official openwrt 24.10 (non-nss) version or use pre-built version like AgustinLorenzo (nss) version with some preinstalled packages on his github releases or wait for qosmio done all the code merge, patches, and clean up.

Been using NSS Mesh build (now unified) for a month and a half. Have 3 mx4300 nodes and have them set to reboot every night. The setup works in general, but the whole family notices brief drop outs all throughout the day (maybe 50 or so connected devices in the house). Is there some logs I can create to pinpoint what my issues are? My 10 year old netgear nighthawk 7000 on merlin was a lot more stable, but it's old, so was only getting 200-300mb/s and not taking advantage of my 1gb fiber connection. Are any of the mesh managing packages working with NSS? My setup is ATT Fiber modem in IP passthrough mode, node 1 acting as main router/gateway, other 2 nodes acting as dummy ap. Backhaul is using 802.11s on third radio for each node. I'm always using the latest builds, thanks for any insights.

Hi @Sinbios,

Now available, update to the latest version

Link: https://github.com/AgustinLorenzo/openwrt/releases/tag/ipq807x-nsswifi-2025-11-14-1945

I'll publish it in a few hours, but I've already set NSS FW 11.4 as the default and compiled all the kmods.

There is no longer a mesh and non-mesh version; it is now unified.

Regards, AgustĂ­n

2 Likes

Nice, thanks!

Hi boys,

This version include NSS offload for WiFi and full support for kmods and target specific

I am redo the repos over the latest commit from OpenWRT.

Changelog (include upstream of OpenWRT):

  • Updated kernel and NSS software to version 6.12.57.
  • The “99-qol-fixes” script is modified to be called “zzz_99-qol_fixes” to ensure that it is executed at the very end, and the generic “uci commit” command is changed to more specific contexts (uci commit wireless - uci commit pbuf).
  • The firmware for NSS is set to 11.4.0.6 by default to correct DHCP issues caused by the previous firmware (12.2) in some scenarios.
  • Added support for “full kmod and target specific packages.” Now my CI compiles all kmods and packages related to the target and publishes them at: https://openwrtdata.agustinls.com (based on Github Pages)
  • Related to the above, mwan3, sqm, and mesh11sd are no longer included by default as they can be installed without issues via LUCI or APK.
  • Package updates from upstream.
  • WARNING: Now I am only compiling for AX3600, AX6, AX9000, Buffalo WXR-5950AX12, Dynalink DL-WRX36, QNAP 301W, Netgear RAX120v2, SXR80, SXS80, WAX218, Arcadyan AW1000, Zyxel NBG7815, Linksys MX4200 (v1 and v2), MX4300, MX5300, MX8500 and Spectrum SAX1V1K devices.

Notes:

Sources:

BUILDED (UNIFIED): https://github.com/AgustinLorenzo/openwrt/releases/tag/ipq807x-nsswifi-2025-11-14-1945

NOTE: I am now only compiling for Xiaomi AX3600, AX6, AX9000, Buffalo WXR-5950AX12, Dynalink DL-WRX36, QNAP 301W, Netgear RAX120v2, SXR80, SXS80, WAX218, Arcadyan AW1000, Zyxel NBG7815, Linksys MX4200 (v1 and v2), MX4300, MX5300, MX8500 and Spectrum SAX1V1K devices, if someone has used my versions with other devices (and it is supported), let me know and I will add it.

13 Likes

Can you add LED and Fan support for nbg7815 from asvio's repo? His last commit was 4 months ago, seems abandoned.
Fan and LED commits:

1 Like

Qosmio, i’d like to ask if it would be possible to include this pull from openwrt github to your 24.10-nss repo ? Thanks.

Is anyone still experiencing crashes regarding spurious kick events on IPQ807x? I believe this recent commit addressed this issue:

I upgraded my 5 MX4300 units to Agustin’s latest build a couple of days ago (which has this change) and just experienced a crash very typical to that of the deadlock mentioned in the commit. I had disabled network logging since I had assumed this was fixed. Do patches like these require resetting OpenWrt’s configuration to be effective? I have since enabled network logging again to see what is causing the crashes.

1 Like

Hi, I installed the latest version of AgustínLorenzo on my Qhora-301w router. Everything went well until I tried to install Adblock. The apk command gave me unmet dependencies (I don't remember which ones now, but they were pretty critical). Then I had the bad idea of ​​running the installation command with the "force" parameter, thinking that Adblock would install ignoring the dependencies, but what happened was that it replaced many critical packages and made the Luci website unusable. After restarting, the network status LEDs don't light up and the router doesn't respond to pings. I also tried pressing the reset button for 30 seconds and stopping the router's boot process three times in a row. Does anyone have a guide for recovering this router using a USB-TTL adapter?