I installed 24.04 on a Raspberry Pi 4b (8 GB). In addition to the built-in NIC, I have a Netgear USB A8000 NIC installed. When I turn on the Hotspot for the internal NIC, NetworkManager creates and activates the connection. However, when I try to connect to the hotspot from a different machine (Windows, Ubuntu), the connection does not succeed. The connection machine reports:
2024-05-15T18:07:23.013534-04:00 moose-Oryx-Pro NetworkManager[949]: <warn> [1715810843.0128] device (wlp0s20f3): Activation: failed for connection 'apex-uploader'
The connecting machine syslog contains these additional messages:
2024-05-15T18:07:23.013845-04:00 moose-Oryx-Pro NetworkManager[949]: <info> [1715810843.0134] device (wlp0s20f3): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
2024-05-15T18:07:23.014848-04:00 moose-Oryx-Pro avahi-daemon[867]: Withdrawing address record for fe80::3a5c:e0c8:60b2:9e0 on wlp0s20f3.
2024-05-15T18:07:23.015214-04:00 moose-Oryx-Pro avahi-daemon[867]: Leaving mDNS multicast group on interface wlp0s20f3.IPv6 with address fe80::3a5c:e0c8:60b2:9e0.
2024-05-15T18:07:23.015818-04:00 moose-Oryx-Pro avahi-daemon[867]: Interface wlp0s20f3.IPv6 no longer relevant for mDNS.
2024-05-15T18:07:23.035133-04:00 moose-Oryx-Pro NetworkManager[949]: <info> [1715810843.0350] dhcp4 (wlp0s20f3): canceled DHCP transaction
2024-05-15T18:07:23.035251-04:00 moose-Oryx-Pro NetworkManager[949]: <info> [1715810843.0350] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds)
2024-05-15T18:07:23.035319-04:00 moose-Oryx-Pro NetworkManager[949]: <info> [1715810843.0351] dhcp4 (wlp0s20f3): state changed no lease
2024-05-15T18:07:23.163156-04:00 moose-Oryx-Pro kernel: [25000.975378] wlp0s20f3: deauthenticating from e4:5f:01:2e:e8:cd by local choice (Reason: 3=DEAUTH_LEAVING)
2024-05-15T18:07:23.263930-04:00 moose-Oryx-Pro wpa_supplicant[955]: wlp0s20f3: CTRL-EVENT-DISCONNECTED bssid=e4:5f:01:2e:e8:cd reason=3 locally_generated=1
2024-05-15T18:07:23.264177-04:00 moose-Oryx-Pro wpa_supplicant[955]: wlp0s20f3: CTRL-EVENT-DSCP-POLICY clear_all
2024-05-15T18:07:23.265227-04:00 moose-Oryx-Pro NetworkManager[949]: <info> [1715810843.2650] device (wlp0s20f3): supplicant interface state: completed -> disconnected
2024-05-15T18:07:23.265515-04:00 moose-Oryx-Pro NetworkManager[949]: <info> [1715810843.2651] device (p2p-dev-wlp0s20f3): supplicant management interface state: completed -> disconnected
The Hotspot server syslog contains these messages:
2024-05-15T22:06:38.207093+00:00 pi4-1u wpa_supplicant[816]: wlan0: AP-STA-CONN\
ECTED dc:1b:a1:0b:ed:3e
2024-05-15T22:06:38.208584+00:00 pi4-1u wpa_supplicant[816]: wlan0: EAPOL-4WAY-\
HS-COMPLETED dc:1b:a1:0b:ed:3e
2024-05-15T22:07:23.195161+00:00 pi4-1u wpa_supplicant[816]: wlan0: AP-STA-DISC\
ONNECTED dc:1b:a1:0b:ed:3e
I've tried various remedies obtained from Googling but none change this behavior. I have tried this on both 24.04 server and desktop. Hotspot does work on the same machine with Pi OS Bookworm.
I installed 24.04 Desktop on a Pi 5. When I enabled Hotspot on the internal NIC, ifconfig reported successful configuration: UP,BROADCAST, RUNNING, MULTICAST> mtu 1500 6807:a627: da82 prefixlen 64 scopeid 0x20<link> 17T09:52: 58.712376- 04:00 pi5-0ud NetworkManager[ 1128]: <info> [1715953978.7117] device (wlan0): Activation: starting connection 'Hotspot' (5e79d83f- bdf5-488d- a204-44b4b11fe9 33) 17T09:52: 58.712675- 04:00 pi5-0ud NetworkManager[ 1128]: <info> [1715953978.7125] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') 17T09:52: 58.713302- 04:00 pi5-0ud NetworkManager[ 1128]: <info> [1715953978.7131] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') 17T09:52: 58.718217- 04:00 pi5-0ud NetworkManager[ 1128]: <info> [1715953978.7179] device (wlan0): Activation: (wifi) access point 'Hotspot' has security, but secrets are required. 17T09:52: 58.719063- 04:00 pi5-0ud NetworkManager[ 1128]: <info> [1715953978.7180] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') 17T09:52: 58.720596- 04:00 pi5-0ud NetworkManager[ 1128]: <info> [1715953978.7204] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') 17T09:52: 58.723198- 04:00 pi5-0ud NetworkManager[ 1128]: <info> [1715953978.7223] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') 17T09:52: 58.723362- 04:00 pi5-0ud NetworkManager[ 1128]: <info> [1715953978.7229] device (wlan0): Activation: (wifi) connection 'Hotspot' has security, and secrets exist. No new secrets needed. 17T09:52: 58.724332- 04:00 pi5-0ud NetworkManager[ 1128]: <info> [1715953978.7231] Config: added 'ssid' value 'pi5-0ud' 17T09:52: 58.725169- 04:00 pi5-0ud NetworkManager[ 1128]: <info> [1715953978.7232] Config: added 'mode' value '2' 17T09:52: 58.725273- 04:00 pi5-0ud NetworkManager[ 1128]: <info> [1715953978.7232] Config: added 'frequency' value '2412' 17T09:52: 58.725337- 04:00 pi5-0ud NetworkManager[ 1128]: <info> [1715953978.7232] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256' 17T09:52: 58.725393- 04:00 pi5-0ud NetworkManager[ 1128]: <info> [1715953978.7232] Config: added 'psk' value '<hidden>' 17T09:52: 58.725468- 04:00 pi5-0ud NetworkManager[ 1128]: <info> [1715953978.7232] Config: added 'proto' value 'RSN' 17T09:52: 58.725534- 04:00 pi5-0ud NetworkManager[ 1128]: <info> [1715953978.7232] Config: added 'pairwise' value 'CCMP' 17T09:52: 58.725591- 04:00 pi5-0ud NetworkManager[ 1128]: <info> [1715953978.72...
wlan0: flags=4163<
inet 10.42.0.1 netmask 255.255.255.0 broadcast 10.42.0.255
inet6 fe80::cea:
ether d8:3a:dd:e9:9c:d0 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 93 bytes 9831 (9.8 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
However, the Hotspot is not visible from other machines. That is, it does not appear during a scan. The Pi 5 syslog contains these messages:
2024-05-
2024-05-
2024-05-
2024-05-
2024-05-
2024-05-
2024-05-
2024-05-
2024-05-
2024-05-
2024-05-
2024-05-
2024-05-
2024-05-
2024-05-
2024-05-