I've just seen the problem reports in OpenWrt 19.07.0 second release candidate and asking myself, if it is a good idea to use 19.07.0 on this device or if it is better to wait for a possible 19.07.1?
Has anyone used the 19.07.0 RC2 on this device and can say something to the Wifi (especially 5GHZ) and its behavior regarding hostapd 2.9?
People have been pointing to hostapd 2.9 as the culprit for a few issues in the past weeks, and ynezz has a staging tree with a hostapd bump containing quite a few fixes. The ath10k-ct issue killing wireless has been addressed it seems, which is what most ath10k users seemed to run into, but it looks like hostapd might be creating issues.
yes, i've seen the same on trunk. it makes out its own version of interface crash, completely unrelated to the driver, and refuses to bring up interface unless rebooted...
No issues with Unbound here and I have been running (pre) 19.07 builds for quite a while. Better check first what's actually going wrong (and file a bug) before just reverting to 18.06 - if it's a reproducible issue it will just pop up again in 19.07.1 and so on...
Because its a production system I've reverted to 18.06 (.6) and everything is back to normal now.
What I've done before is to reset 19.07.0 completly to stock and installed unbound-daemon. It was crashing. After setting dnsmasq to another port it seems to run. But this cannot be my problem, because thats also done by my setup script and I've checked if something is listening to port 53 after setup. There was nothing.
All things done by my setting on the unbound and dnsmasq config are not the problem (at least I think so). After reverting them step by step unbound was also crashing. Because everything else is (many but only) uci firewall and network config + some switch stuff for vlans I don't know whats the problem.