Reopening this bug in wpa_supplicant. It seems that the issue is with
the ifupdown script from wpa_supplicant. If the script cannot be run
early in the boot process it should fail gracefully and leave the
interface unconfigured until the networking init script is run. Could
the wpa_supplicant ifupdown script be run in debugging mode (set -x) to
figure out why it fails?
I've also reverted the udev rules change to wait for the networking init
script to have run. It breaks the boot process as we're trying to
configure network interfaces as soon as they're discovered.
** Changed in: wpasupplicant (Ubuntu)
Status: Invalid => Triaged
--
wpasupplicant doesn't start when the network start
https://bugs.launchpad.net/bugs/44194
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
