Repository navigation
FAQ
Questions from the forum thread.
No. Only ppe-nss is built. The last edma-nss
images stay on the releases page, and their sources are the
archive/nss-edma-rework-final tag of this repo and the
archive/edma-nss-final tag of the builder.
Yes, with a normal sysupgrade, followed by a few manual steps: turn
hardware flow offloading on, switch SQM to hw_ppe.qos and delete the old
configs. They are on Migrating from edma-nss.
Hardware flow offloading is probably off. This is the usual result of an upgrade from edma-nss with settings kept. Check it:
uci show firewall.@defaults[0] | grep flow_offloading
grep -c HW_OFFLOAD /proc/net/nf_conntrackBoth options must be 1. See Migrating from edma-nss and
Wired Offload.
No. The service sets it to 0 before it boots the NSS core and back to 1
two minutes after the bring-up succeeded. If a bring-up hangs the board,
the next boot comes up on the host path. Check the state with
logread -e nss-wifi; "offload armed again for the next boot" means it
worked. See Wi-Fi Offload.
For routed traffic, yes. The Wi-Fi offload takes routed flows from the same fw4 flowtable as the PPE. Bridged Wi-Fi connections and multicast do not need it.
They belonged to the old vendor stack and are gone. The PPE and the Wi-Fi offload report through standard tools and debugfs; the commands are in Wired Offload, Wi-Fi Offload and Reporting Bugs. Queue classes moved to Network → PPE QoS.
Only the radios inside the SoC are offloaded. A PCIe radio (QCN9074 or an
ath10k radio such as the QCA9984) runs on the host path. The mac80211
nss_redirect parameter was part of the old vendor stack and does not
exist here.
Drop every NSS package of the old stack (qca-nss-drv, ECM, the NSS
clients and qdiscs, nss-userspace). The Wi-Fi offload needs only
CONFIG_PACKAGE_kmod-nss-wifi-drv=y, CONFIG_ATH11K_NSS_WIFI=y and the
firmware choice. The seeds/ files hold both variants. See Building.
Remove tmp/ in the build tree and run make defconfig again. Stale
package metadata from another branch causes it. Start from a seed file
rather than an old config.
Yes. Each release publishes every kernel module built with its kernel, and
the image points apk at that feed: apk update && apk add kmod-<name>.
The kmods in the official OpenWrt feeds do not match the kernel. The
image picker lists the modules of each release.
On the physical wan port, with hw_ppe.qos. Do not put it on
pppoe-wan or a VLAN device: the switch only knows the port. See
SQM and QoS.
Hardware SQM is new. Turn SQM off and report your line type, the rates you set and a test result with and without SQM.
Yes, with a multicast routing daemon such as igmpproxy, which is not in
the images. Build it in. With the Wi-Fi offload on, routed streams to
Wi-Fi run on the NSS cores and reach each station as unicast. See
Multicast and IPTV.
The normal ppe-nss image. It carries NSS firmware 12.5 and 11.4 and boots
12.5, which does not accept a mesh interface. Switch to 11.4 once:
uci set nss-wifi.general.firmware=11.4; uci commit nss-wifi; reboot.
Measure with iperf3 between a Wi-Fi client and a wired host, never with
the router itself as the server or client. Run it with the offload on and
off and report both numbers, with your MTU if it is not 1500.
It is not tested. If Wi-Fi clients break with mwan3, set
nss-wifi.general.offload to 0, reboot, and report it.
The images build and boot the same drivers, but the maintainer has no IPQ60xx board, so nothing on IPQ60xx is tested here. Reports with logs are welcome; see Reporting Bugs.
The PPE offload has no proprietary parts. It is proposed in openwrt/openwrt#24806. The Wi-Fi offload needs the NSS firmware, which has its own license, so it stays in this tree.