Qualcommax NSS Build

nss-zk.qos is working fine for my WRX36, it is actually delivering better internet speed especially the bufferbloat is now consistently A+; it could be a bug causing what you experienced for AX3600.

@qosmio Yesterday I noticed that ksmbd crashes my router (nbg7815), I reported this on ksmbd github https://github.com/namjaejeon/ksmbd/issues/523 along with crash logs.
What got me interested is that Gemini says:

It looks like your Zyxel NBG7815 is hitting a critical failure in the Linux kernel. Both logs point to the exact same event: a Null Pointer Dereference (specifically a translation fault) occurring within the Qualcomm Crypto Engine (qce) driver while being called by the SMB server (ksmbd)

Qualcomm Crypto Engine (qce)? What do you think?

Edit: Qualcomm Crypto Engine is the problem because smb3 encryption = disabled in ksmbd prevents the crash

2 Likes

does anyone know if the ipq6000 is still working for the MR7350? I am looking into learning how to implement this.

I just compiled the vanilla version with snapshot, I am not sure how to implement the NSS at this time. - Or do I clone in another folder separate from the standard vanilla build? Thanks.

EDIT: made new directory, found how qosmia’s directory - and compiled the main. NSS complete Newb question… how would I tell if this is properly working on my MR7350?

mind you I only have a 300 down supposedly. I never got these speeds on Vanilla MR7350

Very simple method would be to run top or install htop, and while running top/htop via ssh run another Speedtest. If the CPU usage while running a test is reduced or very close to 0% compared to vanilla OpenWrt, then you have obtained NAT acceleration at the very minimum. iperf3 to another device on the network is another option for quick and dirty LAN throughput benchmarking.

You can also try to install luci-mod-status-nss and see if your LuCi status page shows the usage of the NSS cores.

An Important PR was merged, supposedly resolving the issues/crashes with older Ath11k firmware in STA mode.

3 Likes

Thanks! Any plans to switch to 2.12 firmware, since @qosmio has switched over for a while now?

Hi @qosmio, I recently switched ISPs and just came across your notes that VLAN Tagging is not working correctly with nss. How would you go about setting up Telekom ftth which requires VLAN 7 tags?

Docs:

Thanks in advance

Hi @Sinbios,

I tried firmware version 2.12 a few days ago, and I noticed that the WiFi speed is significantly lower, at least on my computer (Intel AX210) and my phone (Nubia Z70 Ultra). In fact, I noticed that the RX speed was stuck at 780 Mbit/s when in the previous version it reached 1440 Mbit/s in the same location.

I don't know if anyone saw something similar in their setup.

Regards, Agustin

2 Likes

My ISP uses VLAN tagging on the WAN and am having no issues with qosmio’s build. Have you tried it yet?

The only note I see is with the way it’s configured.

Follow these steps to tag your WAN with a VLAN:

  1. Network→Interfaces→Devices
  2. “add device configuration”
  3. device type = VLAN(802.1q)
  4. existing device = wan
  5. VLAN ID = 7 (or whatever it is, I’m going by the github link you provided)
  6. save

Now that you have a WAN tagged with a VLAN ID you can use it on the WAN interface when you switch it over to pppoe, just set the device to wan.7 (if your VLAN ID is different, wan will be wan.number).

Additionally, thanks to PR https://github.com/openwrt/openwrt/pull/21563 mentioned by sppmaster above, there is no longer a need to use ath11k firmware version 2.12, which was never officially released by Qualcomm.

2 Likes

Hi Agustin,

New to the scene here and i have to ask stupid questions hope you don’t mind. My ax9000 radio 3 doesn’t work like i can enable it but my devices wont’ connect. is that normal and by design of this build or what im i missing?

Hello there. I'm doing some baby steps in terms of updating qca-ssdk. I'm stuck at the error compiling the latest changes, and I really don't wanna ask Robi about every issue I can't solve myself.

So I'm wondering if someone could point me in the right direction to solve this error?

The plan is to update to win.nss.1.0.r31 then win.nss.1.10 after the 12.5 update is fixed.

Appreciate all the help I can get, and sorry for posting this in the NSS thread, but I know some of you are developing :slight_smile: