Qualcommax NSS Build

Please can someone point me in the right direction to install a NSS build for the dl-wrx32? I'm currently on 23.05.2 ipq807x/generic build of openwrt. I would like to run the sqm nss package and have just downloaded sqm-scripts-nss_20230217c-1_all.ipk. Not sure if this is still required and what the process is so all help would be highly appreciated.

I've decided to return to the old working method with loading the 10G FW (wrapped with mbn header for U-Boot) from U-boot.

Edit
What I noticed is that the 10G_1 port sometimes will start only at router reboot with cable connected to it. If the cable is disconnected and then reconnected it will not start again each time (sometimes a link cannot be established and reboot is necessery).
But that is a minor pain comparing to not working at all.
Probably more skillful user could figure it out.

While creating the nsshtb qdisc, I encountered an error about adding the tc filter. After searching for a long time, I found the same error on 806x, but no solution.

Can anyone help me?

I"ve built (20240229) with ATH11K_NSS_MESH_SUPPORT, nss-drv-wifi-meshmgr and Firmware 11.4
Maybe smb can test mesh (working or not) and performance on ax3600, ax6?

1 Like

Just a word of caution, if anyone is testing this NSS 11.4 + NSS MESH version make sure you build without qca-nss-drv-qdisc/NSS SQM scripts

qca-nss-drv-qdisc will cause a flood of messages and cause the system to hang.

There were a significant number of changes between NHSS.QSDK.11.4 to NHSS.QSDK.12.0.5 in nss_qdisc

 nss_qdisc/Makefile           |  18
 nss_qdisc/nss_bf.c           |  52
 nss_qdisc/nss_blackhole.c    |  12
 nss_qdisc/nss_codel.c        |  11
 nss_qdisc/nss_fifo.c         |  12
 nss_qdisc/nss_htb.c          |  52
 nss_qdisc/nss_ppe.c          |   4
 nss_qdisc/nss_prio.c         |  11
 nss_qdisc/nss_qdisc.c        | 364
 nss_qdisc/nss_qdisc.h        |  57
 nss_qdisc/nss_qdisc_htable.c | 239
 nss_qdisc/nss_qdisc_htable.h |  37
 nss_qdisc/nss_qdisc_stats.c  | 687
 nss_qdisc/nss_qdisc_stats.h  |  28
 nss_qdisc/nss_tbl.c          |  14
 nss_qdisc/nss_wred.c         |  12
 nss_qdisc/nss_wrr.c          |  52
 17 files changed, 1242 insertions(+), 420 deletions(-)
1 Like

Question for everyone.

Has anyone recently tried to reload the ath11k module? The only way to fully load an updated ath11k module was to reboot, as this was a common issue from this post.

I just noticed I am able to reload it now.

/etc/init.d/wpad stop
/sbin/wifi down
rmmod ath11k_ahb
rmmod ath11k
rmmod mac80211
rmmod cfg80211
sleep 1
modprobe ath11k_ahb
/etc/init.d/wpad start
/sbin/wifi up

Tried it 3 times, and all 3 times it came up.

➤ dmesg --color=always|grep -E "c000000.wifi|ath11k|remoteproc"
[Fri Mar  1 12:21:36 2024] remoteproc remoteproc0: releasing cd00000.q6v5_wcss
[Fri Mar  1 12:21:39 2024] remoteproc remoteproc0: cd00000.q6v5_wcss is available
[Fri Mar  1 12:21:46 2024] ath11k c000000.wifi: ipq8074 hw2.0
[Fri Mar  1 12:21:46 2024] ath11k c000000.wifi: FW memory mode: 0
[Fri Mar  1 12:21:46 2024] remoteproc remoteproc0: powering up cd00000.q6v5_wcss
[Fri Mar  1 12:21:46 2024] remoteproc remoteproc0: Booting fw image IPQ8074/q6_fw.mdt, size 668
[Fri Mar  1 12:21:47 2024] remoteproc remoteproc0: remote processor cd00000.q6v5_wcss is now up
[Fri Mar  1 12:21:47 2024] ath11k c000000.wifi: chip_id 0x0 chip_family 0x0 board_id 0xff soc_id 0xffffffff
[Fri Mar  1 12:21:47 2024] ath11k c000000.wifi: fw_version 0x290104a5 fw_build_timestamp 2023-08-02 20:32 fw_build_id WLAN.HK.2.9.0.1-01890-QCAHKSWPL_SILICONZ-1
[Fri Mar  1 12:21:47 2024] ath11k c000000.wifi: htt event 48 not handled
[Fri Mar  1 12:21:47 2024] ath11k c000000.wifi: nss init soc nss if_num 203 userpd_id 0
[Fri Mar  1 12:22:57 2024] remoteproc remoteproc0: stopped remote processor cd00000.q6v5_wcss
[Fri Mar  1 12:22:58 2024] ath11k c000000.wifi: ipq8074 hw2.0
[Fri Mar  1 12:22:58 2024] ath11k c000000.wifi: FW memory mode: 0
[Fri Mar  1 12:22:58 2024] remoteproc remoteproc0: powering up cd00000.q6v5_wcss
[Fri Mar  1 12:22:58 2024] remoteproc remoteproc0: Booting fw image IPQ8074/q6_fw.mdt, size 668
[Fri Mar  1 12:22:59 2024] remoteproc remoteproc0: remote processor cd00000.q6v5_wcss is now up
[Fri Mar  1 12:22:59 2024] ath11k c000000.wifi: chip_id 0x0 chip_family 0x0 board_id 0xff soc_id 0xffffffff
[Fri Mar  1 12:22:59 2024] ath11k c000000.wifi: fw_version 0x290104a5 fw_build_timestamp 2023-08-02 20:32 fw_build_id WLAN.HK.2.9.0.1-01890-QCAHKSWPL_SILICONZ-1
[Fri Mar  1 12:22:59 2024] ath11k c000000.wifi: htt event 48 not handled
[Fri Mar  1 12:24:13 2024] remoteproc remoteproc0: stopped remote processor cd00000.q6v5_wcss
[Fri Mar  1 12:24:14 2024] ath11k c000000.wifi: ipq8074 hw2.0
[Fri Mar  1 12:24:14 2024] ath11k c000000.wifi: FW memory mode: 0
[Fri Mar  1 12:24:14 2024] remoteproc remoteproc0: powering up cd00000.q6v5_wcss
[Fri Mar  1 12:24:14 2024] remoteproc remoteproc0: Booting fw image IPQ8074/q6_fw.mdt, size 668
[Fri Mar  1 12:24:15 2024] remoteproc remoteproc0: remote processor cd00000.q6v5_wcss is now up
[Fri Mar  1 12:24:15 2024] ath11k c000000.wifi: chip_id 0x0 chip_family 0x0 board_id 0xff soc_id 0xffffffff
[Fri Mar  1 12:24:15 2024] ath11k c000000.wifi: fw_version 0x290104a5 fw_build_timestamp 2023-08-02 20:32 fw_build_id WLAN.HK.2.9.0.1-01890-QCAHKSWPL_SILICONZ-1
[Fri Mar  1 12:24:15 2024] ath11k c000000.wifi: htt event 48 not handled
[Fri Mar  1 12:25:27 2024] remoteproc remoteproc0: stopped remote processor cd00000.q6v5_wcss
[Fri Mar  1 12:25:28 2024] ath11k c000000.wifi: ipq8074 hw2.0
[Fri Mar  1 12:25:28 2024] ath11k c000000.wifi: FW memory mode: 0
[Fri Mar  1 12:25:28 2024] remoteproc remoteproc0: powering up cd00000.q6v5_wcss
[Fri Mar  1 12:25:28 2024] remoteproc remoteproc0: Booting fw image IPQ8074/q6_fw.mdt, size 668
[Fri Mar  1 12:25:28 2024] remoteproc remoteproc0: remote processor cd00000.q6v5_wcss is now up

I don't see anything in upstream if there was a change made to remoteproc or specific to q6v5. @robimarko / @Ansuel any insight?

Sweet, should make it easy to enable/disable NSS on the fly, and other module load params without reboots :slight_smile:

2 Likes

I've compiled @qosmio repo + wireguard, nss offload enabled, nss qdisc enabled, IoT + vlans on connection fiber, home usage stats for 24hr window https://imgur.com/a/UAjXy5l
The line with pause is moment of switch firmware between bitthef's and qosimo - so there are 6 days with old firmware and one with new - memory consumption is a bit higher, but no OOM in 24h.

also check removal and load ath11k - also no issues on ax3600

1 Like

Hello. Ax3600 here. Seems on this build nss works ok (in the previous one it didn't like some other guy mentioned above, it had huge cpu usage on speedtest). Performance seems ok. Ram seems to be good too, still have 90MB after 8 hours.
Anyway it has the old bug with playing games through wifi, it randomly timeouts every X time. This was fixed on recent builds. So this makes it non-usable in my case :frowning:

Fri Mar  1 21:59:49 2024 kern.warn kernel: [34584.882594] ath11k c000000.wifi: peer ast idx 134 can't be found
Fri Mar  1 21:59:49 2024 kern.warn kernel: [34585.013845] ath11k c000000.wifi: peer ast idx 134 can't be found
Fri Mar  1 21:59:49 2024 kern.warn kernel: [34585.415980] ath11k c000000.wifi: peer ast idx 134 can't be found
Fri Mar  1 21:59:49 2024 kern.warn kernel: [34585.422177] ath11k c000000.wifi: peer ast idx 134 can't be found
Fri Mar  1 21:59:49 2024 kern.warn kernel: [34585.525795] ath11k c000000.wifi: peer ast idx 134 can't be found
Fri Mar  1 21:59:49 2024 kern.warn kernel: [34585.596033] ath11k c000000.wifi: peer ast idx 134 can't be found
Fri Mar  1 21:59:50 2024 kern.warn kernel: [34585.670336] ath11k c000000.wifi: peer ast idx 134 can't be found
Fri Mar  1 21:59:50 2024 kern.warn kernel: [34585.687786] ath11k c000000.wifi: peer ast idx 134 can't be found
Fri Mar  1 21:59:50 2024 kern.warn kernel: [34585.733609] ath11k c000000.wifi: peer ast idx 134 can't be found
Fri Mar  1 21:59:54 2024 kern.warn kernel: [34590.162863] ath11k_warn: 26 callbacks suppressed
Fri Mar  1 21:59:54 2024 kern.warn kernel: [34590.162914] ath11k c000000.wifi: peer ast idx 134 can't be found
Fri Mar  1 21:59:54 2024 kern.warn kernel: [34590.186344] ath11k c000000.wifi: peer ast idx 134 can't be found
Fri Mar  1 21:59:54 2024 kern.warn kernel: [34590.289281] ath11k c000000.wifi: peer ast idx 134 can't be found
Fri Mar  1 21:59:55 2024 kern.warn kernel: [34590.636812] ath11k c000000.wifi: peer ast idx 134 can't be found
Fri Mar  1 21:59:55 2024 kern.warn kernel: [34590.711913] ath11k c000000.wifi: peer ast idx 134 can't be found
Fri Mar  1 21:59:55 2024 kern.warn kernel: [34590.747719] ath11k c000000.wifi: peer ast idx 134 can't be found
Fri Mar  1 21:59:55 2024 kern.warn kernel: [34591.411890] ath11k c000000.wifi: peer ast idx 134 can't be found
Fri Mar  1 21:59:55 2024 kern.warn kernel: [34591.567793] ath11k c000000.wifi: peer ast idx 134 can't be found

Your ugly hack looks really beautiful to me :slight_smile:

For temperatures I use an addon package but your output looks more refined.

3 Likes

@qosmio , exactly every 2 days uptime, my connected devices to 5 GHz cannot connect anymore, I had to reboot the router to make it work again, I checked the log it happens like this. The connection problem starts right after the hostapd: WPA group handshake. I don't know what it is doing the hostapd try to handshake all of the devices.

What happened to my device is that it connects just for a second to the Wifi then disconnects again and it repeats until I reboot the router.

Here's the log, my router is AX3600

Also randomly crashing modules for oom errors (but no router reboot) with the following log.
Pbuf is set to 512mb

Sat Mar  2 23:38:05 2024 kern.warn kernel: [10942.327329] CPU: 2 PID: 11225 Comm: utpl Not tainted 6.1.79 #0
Sat Mar  2 23:38:05 2024 kern.warn kernel: [10942.337561] Hardware name: Xiaomi AX3600 (DT)
Sat Mar  2 23:38:05 2024 kern.warn kernel: [10942.343201] Call trace:
Sat Mar  2 23:38:05 2024 kern.warn kernel: [10942.347631]  dump_backtrace.part.0+0xc0/0xd0
Sat Mar  2 23:38:05 2024 kern.warn kernel: [10942.349885]  show_stack+0x18/0x30
Sat Mar  2 23:38:05 2024 kern.warn kernel: [10942.354396]  dump_stack_lvl+0x6c/0x88
Sat Mar  2 23:38:05 2024 kern.warn kernel: [10942.357607]  dump_stack+0x18/0x34
Sat Mar  2 23:38:05 2024 kern.warn kernel: [10942.361254]  dump_header+0x44/0x1a0
Sat Mar  2 23:38:05 2024 kern.warn kernel: [10942.364550]  oom_kill_process+0x270/0x274
Sat Mar  2 23:38:05 2024 kern.warn kernel: [10942.367853]  out_of_memory+0xd0/0x30c
Sat Mar  2 23:38:05 2024 kern.warn kernel: [10942.372017]  __alloc_pages_slowpath.constprop.0+0x6b4/0xa30
Sat Mar  2 23:38:05 2024 kern.warn kernel: [10942.375667]  __alloc_pages+0x214/0x260
Sat Mar  2 23:38:05 2024 kern.warn kernel: [10942.381046]  __folio_alloc+0x14/0x20
Sat Mar  2 23:38:05 2024 kern.warn kernel: [10942.384865]  alloc_zeroed_user_highpage_movable+0x24/0x30
Sat Mar  2 23:38:05 2024 kern.warn kernel: [10942.388610]  __handle_mm_fault+0x38c/0xa1c
Sat Mar  2 23:38:05 2024 kern.warn kernel: [10942.393896]  handle_mm_fault+0x1dc/0x260
Sat Mar  2 23:38:05 2024 kern.warn kernel: [10942.397889]  do_page_fault+0x13c/0x310
Sat Mar  2 23:38:05 2024 kern.warn kernel: [10942.401965]  do_translation_fault+0x88/0x94
Sat Mar  2 23:38:05 2024 kern.warn kernel: [10942.405526]  do_mem_abort+0x44/0x94
Sat Mar  2 23:38:05 2024 kern.warn kernel: [10942.409604]  el0_da+0x24/0x60
Sat Mar  2 23:38:05 2024 kern.warn kernel: [10942.413076]  el0t_64_sync_handler+0xac/0x120
Sat Mar  2 23:38:05 2024 kern.warn kernel: [10942.416204]  el0t_64_sync+0x174/0x178
Sat Mar  2 23:38:05 2024 kern.warn kernel: [10942.421235] Mem-Info:
Sat Mar  2 23:38:05 2024 kern.warn kernel: [10942.424118] active_anon:1134 inactive_anon:800 isolated_anon:0
Sat Mar  2 23:38:05 2024 kern.warn kernel: [10942.424118]  active_file:670 inactive_file:49 isolated_file:0
Sat Mar  2 23:38:05 2024 kern.warn kernel: [10942.424118]  unevictable:0 dirty:0 writeback:0
Sat Mar  2 23:38:05 2024 kern.warn kernel: [10942.424118]  slab_reclaimable:2096 slab_unreclaimable:10645
Sat Mar  2 23:38:05 2024 kern.warn kernel: [10942.424118]  mapped:277 shmem:352 pagetables:263
Sat Mar  2 23:38:05 2024 kern.warn kernel: [10942.424118]  sec_pagetables:0 bounce:0
Sat Mar  2 23:38:05 2024 kern.warn kernel: [10942.424118]  kernel_misc_reclaimable:0
Sat Mar  2 23:38:05 2024 kern.warn kernel: [10942.424118]  free:12151 free_pcp:281 free_cma:0
Sat Mar  2 23:38:05 2024 kern.warn kernel: [10942.442577] Node 0 active_anon:4540kB inactive_anon:3200kB active_file:2684kB inactive_file:136kB unevictable:0kB isolated(anon):0kB isolated(file):0kB mapped:1216kB dirty:0kB writeback:0kB shmem:1408kB writeback_tmp:0kB kernel_stack:2320kB pagetables:1052kB sec_pagetables:0kB all_unreclaimable? no
Sat Mar  2 23:38:05 2024 kern.warn kernel: [10942.468613] DMA free:48404kB boost:0kB min:16384kB low:20480kB high:24576kB reserved_highatomic:0KB active_anon:4540kB inactive_anon:3200kB active_file:2448kB inactive_file:316kB unevictable:0kB writepending:0kB present:524288kB managed:415480kB mlocked:0kB bounce:0kB free_pcp:1392kB local_pcp:120kB free_cma:0kB
Sat Mar  2 23:38:05 2024 kern.warn kernel: [10942.496444] lowmem_reserve[]: 0 0 0 0
Sat Mar  2 23:38:05 2024 kern.warn kernel: [10942.518708] DMA: 144*4kB (UME) 403*8kB (UME) 255*16kB (UME) 898*32kB (UME) 149*64kB (UME) 11*128kB (ME) 1*256kB (M) 0*512kB 0*1024kB 0*2048kB 0*4096kB = 47816kB
Sat Mar  2 23:38:05 2024 kern.warn kernel: [10942.522143] 1136 total pagecache pages
Sat Mar  2 23:38:05 2024 kern.warn kernel: [10942.536719] 0 pages in swap cache
Sat Mar  2 23:38:05 2024 kern.warn kernel: [10942.540267] Free swap  = 0kB
Sat Mar  2 23:38:05 2024 kern.warn kernel: [10942.543481] Total swap = 0kB
Sat Mar  2 23:38:05 2024 kern.warn kernel: [10942.546420] 131072 pages RAM
Sat Mar  2 23:38:05 2024 kern.warn kernel: [10942.549281] 0 pages HighMem/MovableOnly
Sat Mar  2 23:38:05 2024 kern.warn kernel: [10942.552153] 27202 pages reserved
Sat Mar  2 23:38:05 2024 kern.info kernel: [10942.555706] Tasks state (memory values in pages):
Sat Mar  2 23:38:05 2024 kern.info kernel: [10942.559181] [  pid  ]   uid  tgid total_vm      rss pgtables_bytes swapents oom_score_adj name
Sat Mar  2 23:38:05 2024 kern.info kernel: [10942.563826] [    907]    81   907      372      101    32768        0             0 ubusd
Sat Mar  2 23:38:05 2024 kern.info kernel: [10942.572324] [    908]     0   908      227        9    32768        0             0 askfirst
Sat Mar  2 23:38:05 2024 kern.info kernel: [10942.580553] [    943]     0   943      266       16    32768        0             0 urngd
Sat Mar  2 23:38:05 2024 kern.info kernel: [10942.589066] [   1949]   514  1949      494      140    28672        0             0 logd
Sat Mar  2 23:38:05 2024 kern.info kernel: [10942.597143] [   2003]     0  2003      965      184    40960        0             0 rpcd
Sat Mar  2 23:38:05 2024 kern.info kernel: [10942.605450] [   2267]     0  2267      277       16    32768        0             0 dropbear
Sat Mar  2 23:38:05 2024 kern.info kernel: [10942.613492] [   2382]     0  2382      707       24    40960        0             0 hostapd
Sat Mar  2 23:38:05 2024 kern.info kernel: [10942.621793] [   2383]     0  2383      707       24    36864        0             0 wpa_supplicant
Sat Mar  2 23:38:05 2024 kern.info kernel: [10942.629865] [   2394]   101  2394     1878      264    45056        0             0 hostapd
Sat Mar  2 23:38:06 2024 kern.info kernel: [10942.638897] [   2395]   101  2395     1760      134    49152        0             0 wpa_supplicant
Sat Mar  2 23:38:06 2024 kern.info kernel: [10942.647310] [   2447]     0  2447      663      208    32768        0             0 netifd
Sat Mar  2 23:38:06 2024 kern.info kernel: [10942.656505] [   2646]     0  2646      430      100    32768        0             0 odhcpd
Sat Mar  2 23:38:06 2024 kern.info kernel: [10942.664403] [   2764]     0  2764      724       62    32768        0             0 uhttpd
Sat Mar  2 23:38:06 2024 kern.info kernel: [10942.672868] [   3366]     0  3366      707       28    40960        0             0 ntpd
Sat Mar  2 23:38:06 2024 kern.info kernel: [10942.681225] [   3386]   123  3386      329       14    32768        0             0 ntpd
Sat Mar  2 23:38:06 2024 kern.info kernel: [10942.689164] [   3836]     0  3836      269       37    32768        0             0 odhcp6c
Sat Mar  2 23:38:06 2024 kern.info kernel: [10942.697451] [   4742]     0  4742      707       28    32768        0             0 dnsmasq
Sat Mar  2 23:38:06 2024 kern.info kernel: [10942.705541] [   4748]   453  4748     1211      188    45056        0             0 dnsmasq
Sat Mar  2 23:38:06 2024 kern.info kernel: [10942.713633] [   5434]     0  5434      283       23    28672        0             0 dropbear
Sat Mar  2 23:38:06 2024 kern.info kernel: [10942.721967] [   5435]     0  5435      332      116    32768        0             0 ash
Sat Mar  2 23:38:06 2024 kern.info kernel: [10942.730685] [  10943]     0 10943      354      106    36864        0             0 pppd
Sat Mar  2 23:38:06 2024 kern.info kernel: [10942.738633] [  11179]     0 11179      300      161    28672        0             0 modprobe
Sat Mar  2 23:38:06 2024 kern.info kernel: [10942.746703] [  11180]     0 11180      364      154    32768        0             0 hotplug-call
Sat Mar  2 23:38:06 2024 kern.info kernel: [10942.755126] [  11190]     0 11190      365      136    32768        0             0 hotplug-call
Sat Mar  2 23:38:06 2024 kern.info kernel: [10942.764092] [  11221]     0 11221      335      125    32768        0             0 fw4
Sat Mar  2 23:38:06 2024 kern.info kernel: [10942.772659] [  11222]     0 11222      269      105    32768        0             0 odhcp6c
Sat Mar  2 23:38:06 2024 kern.info kernel: [10942.780373] [  11225]     0 11225      743      299    36864        0             0 utpl
Sat Mar  2 23:38:06 2024 kern.info kernel: [10942.788709] [  11227]     0 11227      609      138    36864        0             0 nft
Sat Mar  2 23:38:06 2024 kern.info kernel: [10942.797050] [  11232]     0 11232      357      202    32768        0             0 sysntpd
Sat Mar  2 23:38:06 2024 kern.info kernel: [10942.804773] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/,task=utpl,pid=11225,uid=0
Sat Mar  2 23:38:06 2024 kern.err kernel: [10942.813123] Out of memory: Killed process 11225 (utpl) total-vm:2972kB, anon-rss:736kB, file-rss:460kB, shmem-rss:0kB, UID:0 pgtables:36kB oom_score_adj:0
Sat Mar  2 23:38:07 2024 user.notice firewall: Reloading firewall due to ifupdate of wan (pppoe-wan)

I think you are right. WIth bitthief NSS build I had /etc/config/ecm file with below settings in order to mitigate the SSL errors. This was broadly discussed several months ago.

I am still receiving SSL errors when accessing the LAN using the latest builds from @qosmio.
I'm unsure if anyone else is experiencing this issue.

What do you do and how do you notice the SSL errors in your LAN?
In my case I couldn't open one specific website that used an encrypted communication.
Performing a bufferbloat test especially via WiFi couldn't complete upload test because of the numerous SSL errors.
Additionally I had an upload cap of only 30 Mbps on all speedtests performed on WiFi clients.
I mentioned all of them in my older posts when I started using earliest implementation of NSS for ipq807x from @bitthief.
I'm glad that I no longer see any of them now.
@anom3 was the first one that started to investigate those SSL errors.

I did not encounter this issue when using devices connected via WLAN. However, when downloading through https using wget/curl on a LAN device, I frequently received the following error.

2024-03-03 21:03:19 (1.81 MB/s) - Read error at byte 327339/5173995520 (error:1408F119:SSL routines:ssl3_get_record:decryption failed or bad record mac). Retrying.

After poking around I found that the error will disappear immediately with

ethtool -K lan tx-checksum-ip-generic off

My device has two ports for LAN/WAN respectively.

ethtool -i lan
driver: nss-dp
version: 6.1.79
firmware-version:
expansion-rom-version:
bus-info: 3a007000.dp6-syn
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no
root@OpenWrt:~# ethtool -i wan
driver: nss-dp
version: 6.1.79
firmware-version:
expansion-rom-version:
bus-info: 3a003000.dp5-syn
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no

Anyone find a fix for the Qnap 301W 10G-1 port not working?

Yep Mesh seems to be very buggy. So I've reverted back to Firmware 12.0.

https://openwrt.admincomps.ru/nss-wifi/

Hi boys,

This version include NSS offload for WiFi (MESH NOT WORKING)

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

Changelog (include upstream of OpenWRT):

  • Added the latest commits from @qosmio for NSS (openwrt and nss-packages)
  • Enabled again the modules of Mesh with NSS firmware 12.0 (MESH is not working)

Notes:

Sources:

BUILDED: https://github.com/AgustinLorenzo/openwrt/releases/tag/ipq807x-nsswifi-2024-03-03-2320

NOTE: Now I am only compiling for the AX3600, AX6 and AX9000 and Dynalink DL-WRX36 and Buffalo WXR-5950AX12 and QNAP QHora-301W devices and Netgear RAX120v2, if anyone has used my versions with other devices, tell me and I will add them again.

Regards, Agustin

1 Like

Hi boys,

This version include NSS offload for WiFi (MESH SHOULD BE WORK)

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

Changelog (include upstream of OpenWRT):

  • Added the latest commits from @qosmio for NSS (openwrt and nss-packages)
  • Downgrade to NSS 11.4 firmware (should be work Mesh with NSS, TEST and give me feedback)

Notes:

Sources:

BUILDED: https://github.com/AgustinLorenzo/openwrt/releases/tag/ipq807x-nsswifi-mesh-2024-03-04-0004

NOTE: Now I am only compiling for the AX3600, AX6 and AX9000 and Dynalink DL-WRX36 and Buffalo WXR-5950AX12 and QNAP QHora-301W devices and Netgear RAX120v2, if anyone has used my versions with other devices, tell me and I will add them again.

Regards, Agustin

2 Likes

Good evening, thank you for your suggestion. I couldn't get it to work in mesh. I went back to the 10/28 version.

Hi @dckiller51

Can you share the log of dmesg and kernel log for review that?

Regards, Agustin