Hi, i have a curious case , post purpose is to find out if it happened to other too
At the company where i work we have link made of two powerbeam 5ac gen 2, in many frequencies a packet which we still have to figure out will cause one of the radios to reboot, changing frequency “fixes” it , so we tried flashing the two powerbeams with openwrt, and to our surprise , also with openwrt it crashes, we already changed 3 times the offending hardware ( radio and power supply ).
We had this happen several times with various ubnt gear, but since i guess part of the ath10k firmware they use has same codebase as ct one used by openwrt….
We haven’t been able to capture anything in dmesg.
Anyone here ad a case of an airborne packet causing ath10k to crash so bad that triggers whole system reboot?
I have had a case of a reboot. It was caused by the ath10k-ct drivers on a system with limited ram - in my case Ubiquiti too. With heavy traffic the CT drivers used up all the free memory triggering a system OOM (Out Of Memory) followed by a reboot. The reboot, of course, clears the dmsg buffer so you will not see anything.
I did find changing the channel helped only that it reduced the traffic for a while, so was not really helping.
The fix, in my case, was to change to the non-ct ath10k drivers that are optionally available..
It varies site from site, on that last case basically anything < 5.7 ghz crashes, to reply also to @_bernd i’m running ct 10.1 , default shipped with openwrt 25.
On ubiquiti firmware sometimes this happened in sites where also cambium hardware was deployed but take it with caution because being crowded places anything can be, i will try some day to take a packet capture with a mediatek radio…