On Thu, 16 May 2019 at 13:19, Jouke Witteveen <j.witteveen@gmail.com> wrote:
On Thu, May 16, 2019 at 11:53 AM Emil Velikov <emil.l.velikov@gmail.com> wrote:
After a bit of debugging I've noticed the move to wpa_cli broke my setup. Namely: wpa_cli does not reliably detect when the laptop resumes into another wireless network. Issue happens fairly intermittently - from once a week to multiple times a day - yet I have not seen it even once in the years of using wpa_actiond.
Is this related to your wpa_actiond patch [1] to wait for three missing PONGs before failing?
Haven't confirmed (did not hack on wpa_cli yet) but I suspect they're different. The PONGs are required solely due to resource starvation - high memory/CPU/fd usage. While here we have a wifi network change across suspend/resume.
Should I file a archlinux bug report, any suggestions how to proceed?
It would be nice if you could gather some more details about the issue you are experiencing. Most likely, it indicates a bug in wpa_cli. In my experience, you are likely to get a helpful response over at the hostap mailing list.
Dully noted, will do - thanks. -Emil