Trying to connect raspberry pi 5 mm6108 to AP

Software
1

My raspberry pi5 is loading the drivers dmesg has no errors.

I do have my Halowlink2 AP set up Halow devices will get an ip on this devices local network, which is how I’d like this to work.

kbsherman@pi5:~ $ sudo ip link set wlan1 up
kbsherman@pi5:~ $ sudo iw dev wlan1 scan | grep SSID
SSID: halowlink2-36a7

I had used these steps successfully to connect the station to the AP, but they however no longer work.
sudo ip link set wlan1 up
sudo wpa_supplicant -B -i wlan1 -c /etc/wpa_supplicant/wpa_supplicant-wlan1.conf
sudo dhclient wlan1

dhclient wlan1 never returns an ip address

4: wlan1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 3c:22:7f:71:df:13 brd ff:ff:ff:ff:ff:ff

My AP is set to country code US.

kbsherman@pi5:~ $ sudo iw reg get
global
country US: DFS-FCC
(902 - 904 @ 2), (N/A, 30), (N/A)
(904 - 920 @ 16), (N/A, 30), (N/A)
(920 - 928 @ 8), (N/A, 30), (N/A)
(2400 - 2472 @ 40), (N/A, 30), (N/A)
(5150 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5350 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
(5470 - 5730 @ 160), (N/A, 24), (0 ms), DFS
(5730 - 5850 @ 80), (N/A, 30), (N/A), AUTO-BW
(5850 - 5895 @ 40), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW, PASSIVE-SCAN
(5925 - 7125 @ 320), (N/A, 12), (N/A), NO-OUTDOOR, PASSIVE-SCAN
(57240 - 71000 @ 2160), (N/A, 40), (N/A)

phy#2 (self-managed)
country US: DFS-invalid
(902 - 904 @ 2), (N/A, 36), (N/A), AUTO-BW
(904 - 912 @ 8), (N/A, 36), (N/A), AUTO-BW
(912 - 920 @ 8), (N/A, 36), (N/A), AUTO-BW
(920 - 928 @ 8), (N/A, 36), (N/A), AUTO-BW
(5650 - 5690 @ 40), (N/A, 36), (N/A), AUTO-BW
(5170 - 5330 @ 160), (N/A, 36), (N/A), AUTO-BW
(5490 - 5650 @ 160), (N/A, 36), (N/A), AUTO-BW
(5735 - 5895 @ 160), (N/A, 36), (N/A), AUTO-BW

phy#0
country 99: DFS-UNSET
(2402 - 2482 @ 40), (6, 20), (N/A)
(2474 - 2494 @ 20), (6, 20), (N/A)
(5140 - 5360 @ 160), (6, 20), (N/A)
(5460 - 5860 @ 160), (6, 20), (N/A)

wpa_supplicant-wlant.conf
country=US
network={
ssid=“halowlink2-36a7”
#psk=“removed for illustration”
psk=441d3497e743c756f6eabf6961b6483a43963e4db89df046215144568ca35694
}

What’s the best way to troubleshoot this?

2

Using nmcli to connect seems to be working

nmcli dev wifi connect “SSID” password “pwd” ifname wlan1

Will keep testing over the next several days.

3

As you’ve discovered, nmcli resolves the issue where direct starting of supplicant does not.

The issue is wlan1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN , specifically NO-CARRIER.
Someone will definitely correct me, but if I recall correctly, this is because there is an rfkill module on RaspberryPi OS/Ubuntu which keeps the interfaces disabled, network manager handles the enablement of radios through rfkill transparently.

rfkill list all will tell you the state of the radios. Inspect it both before using nmcli, and after using nmcli.

wpa_supplicant might work happily, directly, with rfkill unblock all called before it. Personally I’d just use NetworkManager unless you need a specific feature of wpa_supplicant_s1g.