Le 10/09/2025 à 16:39, Peter via Dng a écrit :

> Ralph & all,
>
> From:    Ralph Ronnquist via Dng <dng@???>
> Date:    Wed, 10 Sep 2025 09:59:19 +1000
>> The key trick is to make wpa_supplicant reload configuration from
>> the file after you have enabled the network with wpa_gui.
>> ----
>>      # pkill -HUP wpa_supplicant
>> or
>>      $ wpa_cli reconfigure
>> ----
> User interaction, correct?
>
> I'm interested in automation.  When the system boots up the connection
> is established without user attention to wpa_cli, wpagui & etc.
>
> Thx,          ... P.
>

    I still use ifupdown and wpa_supplicant. With configuration by
wpa_gui. When I introduce a new wifi hub, it is enough to save
configuration and wpa_supplicant reconnects automatically on next
reboot. But there's also ifplugd installed, which plays an essential
role. That whole set is pretty convoluted and it takes me a while to
understand what's going on when it doen't work, essentially on a fresh
install. Usually it works like a charm for years. Never used wpa_cli.

--     Didier