Should hardware flow offloading be enabled under Network>Firewall - Routing/NAT Offloading?
My r7800, latest build, setup 5G wifi client to connect my other ISP router, and LAN to PC.
Using speedtest.com, The wifi speed is 640down and 470up. Very good!
1 Like
software offloading and/or hardware offloading on the firewall page should be both turned off.
The hardware offloading is hardcoded in. If somebody knows how to not have it hardcoded in and for that firewall page to toggle on/off NSS hardware offloading I would love for that to be an option. Might make it more attractive to include at least some of the NSS work in to mainline. 
1 Like
Still issues with the firewall, now incoming external connections aren't forwarded (router->internal server) according to the rules I have.
I can't connect to the mail server forward rule externally.
I can't connect to the mail server forward rule when on local ethernet.
I CAN connect to the mail server forward rule when on local wifi!?
I also see stuff like this is dmesg, this is apparently my chromecast, never seen it before.
br-lan: received packet on wlan0 with own address as source address (addr:54:60:xx:xx:xx:xx, vlan:0)
this log spam seems to come up for a fair number of users for different reasons. You can do a forum search and try a few solutions. While it may have been triggered by your other symptoms, I suspect it's harmless and not contributing to your other issues.
The log spam is very annoying tho and makes troubleshooting issues difficult.
HTH.
Could it be this rule from /etc/firewall.d/qca-nss-ecm?
iptables -A FORWARD -m physdev --physdev-is-bridged -j ACCEPT
What does it translate to with nft?
how you enabled ccache and how you use it during build?
thanks
Easy, make menuconfig --> [*] Advanced configuration options --> [*] Use ccache (in middle of the list).
mefju51
1679
Is it possible that you can share you current startup NSS Config and SQM Config?
I'm trying to limit bandwith on one of the wireless network using SQM, but it affects to all wlan hosts. Beside of that I have similar network to yours so I was wondering if my setup is propely configured.
Thanks in advance.
ok thank you, and I have to add a folder in buildroot or any where I want on my pc? and to use it or start it, I add it with make ?
just in first post, everythig is there
I do not care where the cache real location is, just did it.
1 Like
Ok but the question was how you use it after enabled it.
Someone could help me.
Sorry I'm a beginner
no difference, when I first make -j4, building time is much longer.
then second make, 10~20min.
I can't for the life of me get a forward to an internal machine work with nft...
Maybe I'm missing some module... it kind of works but not from an external connection and only from local wifi.
Rebuild with clean, the Old ea8500 driver + latest v5.10 code is OK.
I believe the new ea8500 driver does not work for mine, because inverted the addr <0> and <4>.
Got a kernel error on NSS, what does that means?
Fri Feb 4 13:29:39 2022 kern.err kernel: [39163.190784] wlan1: NSS TX failed with error: NSS_TX_FAILURE_TOO_SHORT
Fri Feb 4 13:34:38 2022 kern.err kernel: [39462.093882] wlan1: NSS TX failed with error: NSS_TX_FAILURE_TOO_SHORT
Fri Feb 4 13:29:39 2022 kern.err kernel: [39163.190784] wlan1: NSS TX failed with error: NSS_TX_FAILURE_TOO_SHORT
Fri Feb 4 13:34:38 2022 kern.err kernel: [39462.093882] wlan1: NSS TX failed with error: NSS_TX_FAILURE_TOO_SHORT
Fri Feb 4 13:39:37 2022 kern.err kernel: [39760.997705] wlan1: NSS TX failed with error: NSS_TX_FAILURE_TOO_SHORT
Fri Feb 4 13:44:36 2022 kern.err kernel: [40059.902528] wlan1: NSS TX failed with error: NSS_TX_FAILURE_TOO_SHORT
Fri Feb 4 13:49:35 2022 kern.err kernel: [40358.806182] wlan1: NSS TX failed with error: NSS_TX_FAILURE_TOO_SHORT
Fri Feb 4 13:54:34 2022 kern.err kernel: [40657.710670] wlan1: NSS TX failed with error: NSS_TX_FAILURE_TOO_SHORT
Fri Feb 4 13:59:33 2022 kern.err kernel: [40956.616313] wlan1: NSS TX failed with error: NSS_TX_FAILURE_TOO_SHORT
Fri Feb 4 14:04:32 2022 kern.err kernel: [41255.528880] wlan1: NSS TX failed with error: NSS_TX_FAILURE_TOO_SHORT
Fri Feb 4 14:09:31 2022 kern.err kernel: [41554.440818] wlan1: NSS TX failed with error: NSS_TX_FAILURE_TOO_SHORT
Fri Feb 4 14:14:30 2022 kern.err kernel: [41853.351405] wlan1: NSS TX failed with error: NSS_TX_FAILURE_TOO_SHORT
Thanks
The problem I had with the firewall was that ifconfig br-lan promisc needed to be set when running NSS.
I also reverted back to a fw3 build, fw4 is in it's current state not working very well BUT improvements are being made, I hope fw4/nft will work with NSS too eventually.
Hey,
this is a great project and I tried out the Master-NSS-binary with Kernel 5.10 and 5.4:
For both kernels IPv4 is working well and very fast.
But for IPv6 I had many trouble in 5.10 (looks like packet-loss like in the OpenWRT 2021.2.1 when using "Software-Offload").
IPv6 in 5.4 works, but is slow (slower than in OpenWRT 2021.2.1). Is that by intention?
Router is R7800..
Thanks
quarky
1690
How is your IPv6 configured? R7800 with NSS should accelerate IPv6 if it is configured using standard DHCPv6.
