On Sat, Oct 14, 2017 at 11:16:38AM +0200, Stefan Sperling wrote: > On Fri, Oct 13, 2017 at 09:12:05PM -0400, Andre Smagin wrote: > > After testing extensively for two days, I cannot reproduce this issue > > at all, the firewall is as stable as it was for some years. > > > > Are there any debugging printf-s I can add > > What is bs.bs_bmissthreshold set to before and after the change? >
Actually, nevermind. The problem must be somewhere else. This ath(4) driver code bmissthreshold change only affects client mode, but you're running ath(4) in access point mode. So I suppose the culprit is somewhere inside net80211 code changes.
