Paul, I think that the real cause here is that (by looking into debian/ifupdown/functions.sh) wpasupplicant depends on the previous single-file ifstate.
Currently, for the sake of the locking mechanism, it has been split into an individual ifstate.$IFACE per interface, while wpasupplicant still checks for the state /run/network/ifstate.
This leads to loosing track of aliases and misusing of the locking.
I will work on fixing this for Ubuntu and Debian and will appreciate your help in testing it as soon as a hotfix is ready.
Paul, I think that the real cause here is that (by looking into debian/ ifupdown/ functions. sh) wpasupplicant depends on the previous single-file ifstate. ifstate.
Currently, for the sake of the locking mechanism, it has been split into an individual ifstate.$IFACE per interface, while wpasupplicant still checks for the state /run/network/
This leads to loosing track of aliases and misusing of the locking.
I will work on fixing this for Ubuntu and Debian and will appreciate your help in testing it as soon as a hotfix is ready.
Thanks!