Open MarcoTheDingo opened 2 years ago
Probably just needs an extra flag added here.
I would also say this issue probably only applies to networks with WPA3 only.
Great, want to open a PR and test it?
I am by no means a developer, but I did fork and add the flag in both networkmanager.h & wifiManager.cc. https://github.com/TheOfficialJosh/openpilot/tree/wifi-wpa3
It sees the network and allows me to type in the password, but it does not actually connect.
Accidentally closed this
Tested with two different Wi-Fi networks using only WPA3. It only saves the password, but never connects. Going to guess there's something more than these two lines.
Is there a log file I can provide to help with figuring it out?
I can replicate this on my comma three, and looking at the system logs doesn't give much information. I think we might just have to update the network manager package, which is already on the latest release available in apt for Ubuntu 20.04/agnos...
EDIT: If anyone wants to try and solve this I expect you'll need to temporarily add the jammy
(22.04) package list to apt sources and upgrading network manager (remount /
as rw and ro again after, and be warned upgrading any package might break your agnos! just try upgrading network manager alone)
We build ModemManager from source, might have to do the same for NetworkManager.
@andiradulescu you know if 24.04 fixes this for free?
As it is, I kind of doubt it. I need to test - switching my router to WPA3 only - let's see what happens when I try to connect from 24.04.
The WPA3 network appears in the list grayed out with a "forbidden" icon to the left of the right signal icon. I think I need to patch this in https://github.com/commaai/openpilot/pull/27824.
selfdrive/ui/qt/network/wifi_manager.cc: Unsupported network! sflag: 1, wpaflag: 0, rsnflag: 1160
Patched wifi_manager.cc to be able to connect to my WPA3 SSID but it doesn't work:
selfdrive/ui/qt/network/wifi_manager.cc: DBus call error: "Did not receive a reply. Possible causes include: the remote
application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the
network connection was broken."
also tried with nmcli 1.46.0 in Ubuntu 24.04:
nmcli -v
nmcli tool, version 1.46.0
nmcli conn show
NAME UUID TYPE DEVICE
...
openpilot connection **redacted-ssid** e5aea78d-42bb-4082-b4b8-d978c24098c9 wifi --
ifconfig wlan0
wlan0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 00:0a:f5:90:e8:d4 txqueuelen 3000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
dmesg -w
...
[ 1819.334487] R0: [soft_irq][35058324353] [09:07:21.967314] wlan: [0:E :SME] sme_8023_multicast_list: Invalid session: 0
[ 1819.339776] R0: [soft_irq][35058426523] [09:07:21.972635] wlan: [0:E :SME] sme_8023_multicast_list: Invalid session: 0
[ 1836.334879] R0: [cds_mc_thread][35384732358] [09:07:38.967482] wlan: [45934:E :SME] csr_get_active_scan_entry: 4978: Active list Empty scanId: 0
[ 1845.045532] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
So, it still doesn't work also in Ubuntu 24.04 with Network Manager 1.46.0
Wi-Fi networks using only the WPA3 security protocol are showing the 🚫 symbol next to them, and cannot be joined.
See the network "DingoAteYourBaby" in the attached screenshot, which is only using WPA3. The IOT network current connected, has the exact same settings, on the same Access Point, except it is using WPA2.