wpa_supplicant: reconfigure drops control directory

Paul Szabo paul.szabo at sydney.edu.au
Sat Dec 20 11:37:34 PST 2025


I notice that a reconfigure of wpa_supplicant causes it to drop the
control directory and never recreate it. This happens both when the
reconfigure is initiated by SIGHUP or with "wpa_cli reconfigure".
(In the latter case, the directory is gone before wpa_cli completes
and so wpa_cli hangs.)

The issue does not really affect me: I thought of using reconfigure,
then found that reassociate is sufficient for my needs. Still, this
seems a bug that ought to be noted or fixed.

Thanks, Paul
--
Paul Szabo       psz at maths.usyd.edu.au       www.maths.usyd.edu.au/u/psz
School of Mathematics and Statistics   University of Sydney    Australia


===


Demonstration of the issue, using SIGHUP:

root# ps aux | grep supplicant | grep -v grep
root         632  0.0  0.1  18588  8824 ?        Ss   Dec19   0:00 /usr/sbin/wpa_supplicant -s -B -P /run/wpa_supplicant.eth0.pid -i eth0 -D wired -c /etc/wpa_supplicant/wpa_supplicant.conf -C /run/wpa_supplicant
root# ls -ld /run/wpa_supplicant
drwxr-x--- 2 root root 60 Dec 19 06:47 /run/wpa_supplicant
root# kill -HUP 632
root# ps aux | grep supplicant | grep -v grep
root         632  0.0  0.1  18588  9020 ?        Ss   Dec19   0:01 /usr/sbin/wpa_supplicant -s -B -P /run/wpa_supplicant.eth0.pid -i eth0 -D wired -c /etc/wpa_supplicant/wpa_supplicant.conf -C /run/wpa_supplicant
root# ls -ld /run/wpa_supplicant
ls: cannot access '/run/wpa_supplicant': No such file or directory
root# 


Demonstration of the issue, using "wpa_cli reconfigure":

root# ps aux | grep supplicant | grep -v grep
root         621  0.0  0.1  18588  8884 ?        Ss   14:47   0:00 /usr/sbin/wpa_supplicant -s -B -P /run/wpa_supplicant.eth0.pid -i eth0 -D wired -c /etc/wpa_supplicant/wpa_supplicant.conf -C /run/wpa_supplicant
root# ls -ld /run/wpa_supplicant
drwxr-x--- 2 root root 60 Dec 20 14:47 /run/wpa_supplicant
root# wpa_cli reconfigure
Selected interface 'eth0'
^Celoop: could not process SIGINT or SIGTERM in two seconds. Looks like there
is a bug that ends up in a busy loop that prevents clean shutdown.
Killing program forcefully.
 
root# ps aux | grep supplicant | grep -v grep
root         621  0.0  0.1  18588  9048 ?        Ss   14:47   0:00 /usr/sbin/wpa_supplicant -s -B -P /run/wpa_supplicant.eth0.pid -i eth0 -D wired -c /etc/wpa_supplicant/wpa_supplicant.conf -C /run/wpa_supplicant
root# ls -ld /run/wpa_supplicant
ls: cannot access '/run/wpa_supplicant': No such file or directory
root# 


===



More information about the Hostap mailing list