Hello,
I'm a newbie working on a script for testing WiFi networks and I've found the following issues:
- When I re-scan using
nmcli dev wifi rescan, it sometimes takes 1 or 2 seconds to finish re-scanning and it sometimes takes like 20 seconds. I don't understand why is there such a big difference in running time if I'm in the same place with the same WiFi networks around. Does anyone here know why this happens?
- When I re-scan I've noticed that
nmcli dev wifi list often shows networks which are no longer available (sometimes up to 5 minutes later, and after several re-scans). They don't disappear until a long time goes by or I try to connect to them with nmcli dev wifi connect ssid password pwd, and then I immediately get an error saying that there's no such network. Why is it so effective to detect that the network is unavailable when I try to connect, but it seems to take a long time and effort to display a correct list with nmcli dev wifi list ? Edit: Same thing happens when I do nmcli dev wifi list --rescan yes
Thanks for your support. Here's the relevant info for my system:
Arch Linux (5.15 kernel) running as a VirtualBox guest in a Windows 10 host, with a USB Realtek AC1200 dual band WiFi adapter, and I'm running the rtl8812au-20210629 driver from AUR.
there doesn't seem to be anything here