On Wed 15 Jun 2022 at 03:30:53 (+0200), Vincent Lefevre wrote: > On 2022-06-14 15:43:40 +0100, Brian wrote: > > On Tue 14 Jun 2022 at 13:15:56 +0200, Vincent Lefevre wrote: > > > No issues with iwlist and nmcli. > > > > /usr/sbin/wpa_gui and /sbin/wpa_cli should both give sensible outputs > > when run as root. > > For security reasons, I don't want to run them as root.
Then don't run them? You can put wpa_cli status into sudoers so that it will only run with that command. > The iwlist and nmcli utilities don't need root to work correctly. Run them then? I wasn't aware that iwlist would tell the OP which AP is the connected one. I presume nmcli is something to do with NetworkManager, which I've never installed. But, as I wrote earlier, "I would have thought that the program by which you connect would be able to show you all the information it, by definition, knows about the connection that it set up." For most machines, I now use iwd, like Celejar. Cheers, David.
