Wi-Fi working despite "WiFi set failed" message

Hello AllStarLink Community,

I decided to begin my journey into AllStarLink by building a SHARI PiHatU. After reading the instructions multiple times, with some patience and slow but steady soldering, assembly went well and was trouble free.

I set up my MicroSD card (32GB Sandisk High Endurance) using the following:

  • Windows 10 PC
  • Raspberry Pi Imager (v1.90)
  • The “allstar3-arm64-3.0.15.img.xz” file downloaded today (12/2/2024)
  • AllStarLink github Raspberry Pi Install Instructions

After the first boot of my Raspberry Pi4 4GB and SHARI PiHatU, I checked for software updates. Next, I worked through all the settings for different components explained in both the ASL3 and SHARI documentation.

After checking Allmon3 was working with a connection and test to the Parrot server, as well as creating a new Port Forwarding rule in my network, I appeared to have a working node connected to my home wireless network; a UniFi system with both 2.4 & 5.0 GHz connections using the same SSID and password.

I went to add some other known WiFi networks to my node and found the following message in red under “Configured WiFi Networks”… “WiFi set failed”. My home Wi-Fi network, which the node is connected to, isn’t listed. Further, while a new network can be “successfully added”, the entry doesn’t get saved under “Configured WiFi Networks”.

I did notice this single line in my Logs after a reboot:
“nl80211: kernel reports: Registration to specific type not supported” (wpa_supplicant)

I’m also just getting started with Linux so I’m a bit puzzled. Any thoughts on why I’m seeing this error message and behavior even though my node seems to be connecting to my pre-configured Wi-Fi normally?

Many thanks!

To be clear,

Are you using asl3 or shari software ?
and
what/whose instructions were you following for wifi ?

Generically, I can guess that you did not have root privileges when you ran the command and therefore it would not write updated settings

sudo command
Just a guess.

Hey Mike,

I used ASL3. The instructions I followed for making the initial image were from Raspberry Pi Install - AllStarLink Manual.

When trying to add my other known networks I was using the ASL3 Web Admin Portal and the included WiFi Manager.

Given that I added my home network info into the Pi Imager I would have expected the ASL3 WiFi Manager to show it as “Preconfigured” or something similar.

There is no utility in ASL to manage wifi.
You are doing your settings from the OS.

I don’t use asl3 with Pi’s so I am a bit lost.

The user you are running commands in the terminal must not have root privileges.
Try them again with ‘sudo’ in front of them to get super user privileges.
ie

nmcli device wifi connect RadioSite password RF1234

sudo nmcli device wifi connect RadioSite password RF1234

Without proper rights, it can not write new config’s.

Perhaps you are doing this ?

I’m not entirely sure what your root concern/problem is. However the network that you configured in the RPi Imager will show up as “preconfigured”. You should see something like this:

In this case, “preconfigured” is the label for my home WiFi “MFamily Clients” and “FBI Surveillance” is the same for another site where the SSID is “FBI Surveillance”. Can you supply some screenshots of what you’re seeing? Did you set your WiFi region properly in the imager, presumably based on your callsign to US?

I’m not using the terminal. There is a utility (menu choice) on the ASL3 Web Admin Portal. It’s called WiFi Manager.

I was careful to properly set all fields, including the Wi-Fi region (US), with the imager. The network I configured in the RPi Imager (my home network) does not show up as “preconfigured”… even though the node is connected using that exact wi-fi info. Instead I see the error message mentioned in my first post and shown in this screen shot…

The attached screen shot also shows an additional Wi-Fi network that says it was successfully added but which doesn’t get saved.

If it would be helpful, the one error I have in my Logs shows:
“nl80211: kernel reports: Registration to specific type not supported” (wpa_supplicant)

wpa_supplicant

nl80211: kernel reports: Registration to specific type not supported

PRIORITY

3

SYSLOG_FACILITY

3

SYSLOG_IDENTIFIER

wpa_supplicant

SYSLOG_PID

635

SYSLOG_TIMESTAMP

Dec 2 13:00:08

_BOOT_ID

ed71c664c81b4f5da74c5bc08202e24b

_CAP_EFFECTIVE

1ffffffffff

_CMDLINE

/sbin/wpa_supplicant -u -s -O “DIR=/run/wpa_supplicant GROUP=netdev”

_COMM

wpa_supplicant

_EXE

/usr/sbin/wpa_supplicant

_GID

110

_HOSTNAME

node63535

_MACHINE_ID

4cc936676857f17a9a6c0ad0674cf386

_PID

635

_RUNTIME_SCOPE

system

_SOURCE_REALTIME_TIMESTAMP

1733162408848795

_SYSTEMD_CGROUP

/system.slice/wpa_supplicant.service

_SYSTEMD_INVOCATION_ID

7b451b541a9a4eac9fb6c962e52c1d1f

_SYSTEMD_SLICE

system.slice

_SYSTEMD_UNIT

wpa_supplicant.service

_TRANSPORT

syslog

_UID

0

__CURSOR

s=eb0c70a320794f258281a15003914fc3;i=2fb;b=ed71c664c81b4f5da74c5bc08202e24b;m=8ba194;t=6284d51b7adcb;x=a7be5b48623fe0d0

__MONOTONIC_TIMESTAMP

9150868

__REALTIME_TIMESTAMP

1733162408848843

ASL3 doesn’t use wpa_supplicant, it uses NetworkManager. The fact that’s running makes me wonder if there’s something broken with your install. As root, what’s the output of running /usr/share/cockpit/wifimanager/bin/wifi-list-configured.py?

Is this the output you’re looking for?
Traceback (most recent call last):
File “/usr/share/cockpit/wifimanager/bin/wifi-list-configured.py”, line 44, in
display_parameters(nmconnections)
File “/usr/share/cockpit/wifimanager/bin/wifi-list-configured.py”, line 27, in display_parameters
if parameters[‘connection’][‘type’] == “wifi”:
~~~~~~~~~~^^^^^^^^^^^^^^
KeyError: ‘connection’

Just to see if I had something strange happen with my image process I used a new MicroSD card and burned some fresh images carefully following the instructions and entering all suggested information. Here is the outcome:

Using a new “allstar3-arm64-3.0.15.img.xz” file my device booted and found no updates.

  • I ended up with the same error: WiFi not set

Using the “allstar3-arm64-3.0.14.img.xz” file my device booted and found no updates.

  • I ended up with the same error: WiFi not set

Using the “allstar3-arm64-3.0.13.img.xz” file my device booted and found no updates.

  • I ended up with a working device with a normal WiFi Manager screen.
  • Oddly, I still see the same error in my log:
    “nl80211: kernel reports: Registration to specific type not supported” (wpa_supplicant)

Some questions

  1. What Pi hardware are you using?
  2. Does your wireless network SSID or password have any character in it beyond a-z and 0-9?
  3. Paste in the contents of the file /etc/NetworkManager/system-connections/preconfigured.connect and blank out the line psk= if it’s in there.
  4. What version of Rasberry Pi Imager do you have and what OS are you using it on?

Answering your questions based on my initial card imaged with v3.0.15…

  1. Pi hardware = Pi4 4GB
  2. Home Wi-Fi password contains two symbols: @ and !
  3. I don’t have a file by that name in the location you described. I have two files there; “preconfigured.nmconnection” and “wifi.nmconnection”. The contents of the “preconfigured.nmconnection” are as follows:

[connection]
id=preconfigured
uuid=4c59193b-4fe3-4b88-8b94-6e69daaab316
type=wifi
[wifi]
mode=infrastructure
ssid=MyHomeWiFi (name changed for post)
hidden=false
[ipv4]
method=auto
[ipv6]
addr-gen-mode=default
method=auto
[proxy]
[wifi-security]
key-mgmt=wpa-psk
psk= (long character string-deleted for post)

  1. Pi Imager 1.9 on a Windows 10 PC

That’s my bad on the extension. What’s in wifi.nmconnection? Something is blowing up the tool.

Also, was your psk= field the plaintext password or was it the obfuscated base64 string?

No worrries! I really appreciate your help with this.

My psk= field was the string… I just deleted it as you requested.

Contents of wifi.nmconnection file from the location you specified are as follows:

# DO NOT EDIT THIS FILE
# Edit /boot/firmware/wifi.nmconnection and it will be copied here
# Uncomment everything below this line and set your ssid and password
# [connection]
# id=wifi
# uuid=593819b8-135a-4a3e-9611-c36cdeadbeef
# type=wifi
# interface-name=wlan0

# [wifi]
# mode=infrastructure
# ssid=set your wifi ssid here

# [wifi-security]
# auth-alg=open
# key-mgmt=wpa-psk
# psk=set your password here

# [ipv4]
# method=auto

# [ipv6]
# addr-gen-mode=default
# method=auto

# [proxy]

Hrm thats weird. I wonder how that happened but I see the issue.

Delete that second file and see if everything works.

I deleted the “wifi.nmconnection” file from /etc/NetworkManager/system-connections/ with elevated permissions (sudo). Upon a reboot of the node the file reappears. The contents of the new file are the same as previously posted.

As referenced in the /etc/NetworkManager/system-connections/wifi.nmconnection file, I also see a “wifi.nmconnection” file in /boot/firmware/. The contents of that file are below:

# Uncomment everything below this line and set your ssid and password
# [connection]
# id=wifi
# uuid=593819b8-135a-4a3e-9611-c36cdeadbeef
# type=wifi
# interface-name=wlan0

# [wifi]
# mode=infrastructure
# ssid=set your wifi ssid here

# [wifi-security]
# auth-alg=open
# key-mgmt=wpa-psk
# psk=set your password here

# [ipv4]
# method=auto

# [ipv6]
# addr-gen-mode=default
# method=auto

# [proxy]

Should I try deleting the file from both locations?

I was seeing this and a couple of other kernel messages on RPi 3B+, but my node works.
FWIW, the messages disappeared last update.

Chuck