openwrt-configuration-ansible VS openwrt-sfe-flowoffload-ath79

I have something similar: https://github.com/danielvijge/openwrt-configuration-ansible Using an ansible playbook this can configure multiple devices in the same network. But this uses the default configuration files, sometimes with JINJA2 templating when required. For me using the same config format as on a device is convenient, because it allows to first configure using (l)uci, diff the config, then store it.

I use this setup with one router and (currently one) access point. The GitHub description lists the exact configuration. The ansible script is there to push the same configuration from a central lcomputer to both the router and multiple access points, but is totally optional.

https://github.com/danielvijge/openwrt-configuration-ansible might help. I did it with routers as AP, but can work with RPi's too I think.

The WiFi card on this router relies on the CPU doing a lot of work. It simply cannot deliver the necessary performance without the hardware flow offloading, which only exists in the stock firmware. In the past there was also this OpenWRT fork: https://github.com/gwlim/openwrt-sfe-flowoffload-ath79 which enables support for Shortcut Forwarding Engine which exists on this router, but this is no longer updated.

How can I be sure the installation was successful? Network test results are not conclusive, and I am missing "cake" as an option under queuing discipline (like this https://github.com/gwlim/openwrt-sfe-flowoffload-ath79/issues/6).

For TP-Link Archer C7 specifically, there is nothing in official repositories that can help. There was an unofficial fork with the "sfe offload" support (sfe stands for "shortcut forwarding engine"), not sure about its status now.

Try this custom build with hardware offloading support https://github.com/gwlim/openwrt-sfe-flowoffload-ath79