Ben Greear

First, please open one issue for one question/bug in the future. For 5/10 Mhz support, I have no current plans to implement it. This would normally be work I would...

The re-key is for bcast/mcast frames, so when sniffing, possible issues would be ARP not working or something like that. In past issues with firmware keys, I noticed bugs that...

Here are my notes from viewing the logs. The re-key is correlated with improved performance, but there was one re-key where performance did not improve, and in the second rekey...

I've moved development efforts to a new firmware tree that is my patches rebased on top of newer QCA firmware. I'm very curious to know if that helps this problem...

If I build you a set of firmware images, would you be interested in trying to bisect the problem? The procedure is to copy the firmware blob onto your owrt...

Do you really need this to work?

This is probably some issue with owrt and/or its config. Please ask there.

I think this might be a supplicant bug. I saw this message in other testing scenarios: [349951.140828] sta5002: 04:f0:21:67:53:95 authenticate with f8:a0:97:44:94:55 at: 1520282299.350687 [349951.141350] sta5002: failed to insert STA...

Have you been able to test with supplicant patched as suggested?

There are no obvious errors in the logs, though there is one failed-to-transmit message. Normally one of those is OK and system recovers, but perhaps in your case it is...