From: Roy Marples Date: Fri, 7 Jun 2013 20:51:44 +0000 (+0000) Subject: If wpa_supplicant is not running when rebinding, start it for X-Git-Tag: v6.0.0~37 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=af4140cdb403b44edde52aa08139536b689610cb;p=thirdparty%2Fdhcpcd.git If wpa_supplicant is not running when rebinding, start it for wireless interfaces. --- diff --git a/dhcpcd-hooks/10-wpa_supplicant b/dhcpcd-hooks/10-wpa_supplicant index 18c889f2..af429d00 100644 --- a/dhcpcd-hooks/10-wpa_supplicant +++ b/dhcpcd-hooks/10-wpa_supplicant @@ -1,4 +1,4 @@ -# Start and stop wpa_supplicant per wireless interface. +# Start, reconfigure and stop wpa_supplicant per wireless interface. # This is needed because wpa_supplicant lacks hotplugging of any kind # and the user should not be expected to have to wire it into their system # if the base system doesn't do this itself. @@ -24,7 +24,10 @@ wpa_supplicant_reconfigure() { local err errn - wpa_cli -i "$interface" status >/dev/null 2>&1 || return 0 + if ! wpa_cli -i "$interface" status >/dev/null 2>&1; then + wpa_supplicant_start + return $? + fi syslog info "reconfiguring wpa_supplicant" err=$(wpa_cli -i"$interface" reconfigure 2>&1) errn=$? diff --git a/dhcpcd.8.in b/dhcpcd.8.in index 355277d1..c9011425 100644 --- a/dhcpcd.8.in +++ b/dhcpcd.8.in @@ -329,6 +329,9 @@ to reload its configuration and rebind its interfaces. If .Nm is not running, then it starts up as normal. +This may also cause +.Xr wpa_supplicant 8 +to reload its configuration for each interface as well. .It Fl o , Fl Fl option Ar option Request the DHCP .Ar option