Skip to content

Commit

Permalink
wpa_supplicant: start after wireless interfaces
Browse files Browse the repository at this point in the history
wpa_supplicant fails to start if the wireless interfaces aren't ready yet,
so we need to add a system ordering directive here to start wpa_supplicant
after the interfaces are ready. Note that Requires= is not enough since
it does not imply ordering.
  • Loading branch information
bennofs committed Jun 15, 2016
1 parent 41d523a commit 519673e
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion nixos/modules/services/networking/wpa_supplicant.nix
Expand Up @@ -129,7 +129,7 @@ in {
in {
description = "WPA Supplicant";

after = [ "network-interfaces.target" ];
after = [ "network-interfaces.target" ] ++ lib.concatMap deviceUnit ifaces;
requires = lib.concatMap deviceUnit ifaces;
wantedBy = [ "network.target" ];

Expand Down

2 comments on commit 519673e

@danbst
Copy link
Contributor

@danbst danbst commented on 519673e Jun 15, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So, how about autodetected interfaces? They still have this problem, don't they?

@bennofs
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixing this for autodetected devices is a much larger task, and I don't know how it could work. Also, I'm not sure if it is even broken, shouldn't the udev rule handle that?

Please sign in to comment.