Latest Bookworm on Pi 4 and 5. USB WiFi adaptor plugged in to use as access point. Using nmcli to configure access point. Everything works. Reboot no problem.
I then bridge eth0 to wlan1 using nmcli. It works until I reboot. Before reboot, nmcli dev status shows wlan1 connected to con-name br1-wifi. After reboot, br1-wifi is not shown as having a device. Before reboot, the SSD is visible in the network management thing in the OS toolbar and in the network list of a notebook sitting nearby. After reboot, the SSID is no longer public.![:x]( "Mad")
In the notebook, I attempt to connect to a hidden network. The notebook shows no error messages in dmesg for the attempt.
A manual edit of the br1-wifi connection shows no password. I added the password and saved the change. The SSID is then visible in the notebook.![:shock:]( "Shocked")
Why did the password not survive the boot?
After the SSID is public and I connect on 5 GHz band, the connection drops out without completing. The only difference I can find is that the WiFi added to the Pi has the following:dmesg on the notebook says the following. I have not found out anything about changing this sort of stuff in NetworkManager.
I then bridge eth0 to wlan1 using nmcli. It works until I reboot. Before reboot, nmcli dev status shows wlan1 connected to con-name br1-wifi. After reboot, br1-wifi is not shown as having a device. Before reboot, the SSD is visible in the network management thing in the OS toolbar and in the network list of a notebook sitting nearby. After reboot, the SSID is no longer public.
In the notebook, I attempt to connect to a hidden network. The notebook shows no error messages in dmesg for the attempt.
A manual edit of the br1-wifi connection shows no password. I added the password and saved the change. The SSID is then visible in the notebook.
Why did the password not survive the boot?After the SSID is public and I connect on 5 GHz band, the connection drops out without completing. The only difference I can find is that the WiFi added to the Pi has the following:
Code:
VHT Capabilities (0x03c051b2):Supported Channel Width: neither 160 nor 80+80Code:
wlo1: send auth to 1c:bf:ce:db:f9:93 (try 1/3)wlo1: authenticatedwlo1: associate with 1c:bf:ce:db:f9:93 (try 1/3)wlo1: RX AssocResp from 1c:bf:ce:db:f9:93 (capab=0x11 status=0 aid=1)Statistics: Posted by peterlite — Tue Jul 09, 2024 5:06 am