On Thu, May 16, 2019 at 11:53 AM Emil Velikov 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
Hi team,
On Sat, 9 Feb 2019 at 09:19, Thomas Bächler wrote:
>
> Am 8. Februar 2019 20:17:52 MEZ schrieb Jouke Witteveen
> :
> >On Fri, Feb 8, 2019 at 3:36 PM Emil Velikov
> >wrote:
> >>
> >> On Thu, 7 Feb 2019 at 14:50, Jouke Witteveen via arch-projects
> >> wrote:
> >> >
> >> > The same
On Sat, 9 Feb 2019 at 09:19, Thomas Bächler wrote:
>
> Am 8. Februar 2019 20:17:52 MEZ schrieb Jouke Witteveen
> :
> >On Fri, Feb 8, 2019 at 3:36 PM Emil Velikov
> >wrote:
> >>
> >> On Thu, 7 Feb 2019 at 14:50, Jouke Witteveen via arch-projects
> >> wrote:
> >> >
> >> > The same functionality
On Fri, Feb 8, 2019 at 3:36 PM Emil Velikov wrote:
>
> On Thu, 7 Feb 2019 at 14:50, Jouke Witteveen via arch-projects
> wrote:
> >
> > The same functionality is provided by wpa_supplicant, so we do not need
> > an extra and Arch Linux specific dependency.
>
> The introduction of wpa_actiond [1]
On Thu, 7 Feb 2019 at 14:50, Jouke Witteveen via arch-projects
wrote:
>
> The same functionality is provided by wpa_supplicant, so we do not need
> an extra and Arch Linux specific dependency.
The introduction of wpa_actiond [1] hints there are issues with wpa_cli. Namely:
- partial or missing
The same functionality is provided by wpa_supplicant, so we do not need
an extra and Arch Linux specific dependency.
---
README | 4 ++--
contrib/PKGBUILD.in | 1 -
src/lib/auto.action | 31 ++-
src/netctl-auto | 30 +-
4
