Can't connect to wifi [FAILED] DietPi-Config | systemctl restart ifup@wlan0

Niaz · 7 March 2025 19:43

Creating a bug report/issue

I have searched the existing open and closed issues

Required Information

DietPi version | 9.11.2
Distro version | bookworm
Kernel version | Linux RPi8 6.6.74+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.74-1+rpt1 (2025-01-27) aarch64 GNU/Linux
Architecture | arm64
SBC model | RPi 4 Model B (aarch64)
Power supply used | 5V 1A
SD card used | Samsung M2 SSD

Additional Information (if applicable)

Bug report ID | fa62ff01-86b9-4f25-9060-4747b414f86e

Steps to reproduce

Trying to connect to WiFi through dietpi-config

Expected behaviour

connect to WiFi

Actual behaviour

Not connecting to WiFI

Extra details

I have wired connection from one network 192.168.0.0/24, I need to connect to another network 10.0.0.0/24. When I configure the WiFi, it fails to connect. I tried to disable and enable the adapter and purge the config, but it still fails on the same issue. Outputs here:

systemd[1]: Starting ifup@wlan0.service - ifup for wlan0...
wpa_supplicant[9759]: Successfully initialized wpa_supplicant
wpa_supplicant[9759]: nl80211: kernel reports: Registration to specific type not supported
wpa_supplicant[9763]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-52 retry=1
ifup[9770]: RTNETLINK answers: File exists
ifup[9745]: ifup: failed to bring up wlan0
systemd[1]: ifup@wlan0.service: Main process exited, code=exited, status=1/FAILURE
wpa_supplicant[9763]: p2p-dev-wlan0: CTRL-EVENT-DSCP-POLICY clear_all
wpa_supplicant[9763]: p2p-dev-wlan0: CTRL-EVENT-DSCP-POLICY clear_all
wpa_supplicant[9763]: nl80211: deinit ifname=p2p-dev-wlan0 disabled_11b_rates=0
wpa_supplicant[9763]: p2p-dev-wlan0: CTRL-EVENT-TERMINATING
wpa_supplicant[9763]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
wpa_supplicant[9763]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
wpa_supplicant[9763]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Job for ifup@wlan0.service failed because the control process exited with error code.
See "systemctl status ifup@wlan0.service" and "journalctl -xeu ifup@wlan0.service" for details.
[FAILED] DietPi-Config | systemctl restart ifup@wlan0
[ INFO ] DietPi-Config | Reloading networking data, please wait...
[  OK  ] DietPi-Config | Network restarted

systemctl status ifup@wlan0.service
× ifup@wlan0.service - ifup for wlan0
     Loaded: loaded (/etc/systemd/system/ifup@.service; static)
     Active: failed (Result: exit-code) since Fri 2025-03-07 20:31:59 CET; 6min ago
   Duration: 2min 10.561s
    Process: 9745 ExecStart=/sbin/ifup --allow=hotplug wlan0 (code=exited, status=1/FAILURE)
   Main PID: 9745 (code=exited, status=1/FAILURE)
        CPU: 104ms

wpa_supplicant[9763]: p2p-dev-wlan0: CTRL-EVENT-DSCP-POLICY clear_all
wpa_supplicant[9763]: p2p-dev-wlan0: CTRL-EVENT-DSCP-POLICY clear_all
wpa_supplicant[9763]: nl80211: deinit ifname=p2p-dev-wlan0 disabled_11b_rates=0
wpa_supplicant[9763]: p2p-dev-wlan0: CTRL-EVENT-TERMINATING
wpa_supplicant[9763]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
wpa_supplicant[9763]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
wpa_supplicant[9763]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
wpa_supplicant[9763]: wlan0: CTRL-EVENT-TERMINATING
systemd[1]: ifup@wlan0.service: Failed with result 'exit-code'.
systemd[1]: Failed to start ifup@wlan0.service - ifup for wlan0.

What am I doing wrong? Thank you.

Joulinar · 8 March 2025 09:38

you can try to bring down/up the interface manually

ifdown wlan0
ifup wlan0

or try rebooting

Niaz · 8 March 2025 10:11

I’ve tried rebooting before with no progress. But this experiment showed something:

ifdown wlan0
ifdown: interface wlan0 not configured

ifup wlan0
Error: ipv4: Address already assigned.
ifup: failed to bring up wlan0

Doesn’t make much sense. This device was never before in 10.0.0.0 network. And wifi adapter was never configured on it. This is the first time I’m trying to use it.

Is there a way to flush any settings from the adapter?

Joulinar · 8 March 2025 10:15

can you check

cat /etc/network/interfaces

Niaz · 8 March 2025 10:19

I honestly don’t know what happened, but the WiFi is connected now.

Didn’t do anything since I wrote this post and until I’ve put the ifdown and ifup commands.

Did it just need good night sleep?

EDIT: Something is definitely funky. Tried to change IP Address to make sure all is clear, but it end up with no connection and:

[  OK  ] DietPi-WiFiDB | mkdir -p /etc/wpa_supplicant
[  OK  ] DietPi-WiFiDB | eval > /var/lib/dietpi/dietpi-wifi.db
[ INFO ] DietPi-WiFiDB | Applied WiFi DB slot 0 with SSID "RPi8"
[ INFO ] DietPi-WiFiDB | Applied WiFi DB slot 1 with SSID ""
[ INFO ] DietPi-WiFiDB | Applied WiFi DB slot 2 with SSID ""
[ INFO ] DietPi-WiFiDB | Applied WiFi DB slot 3 with SSID ""
[ INFO ] DietPi-WiFiDB | Applied WiFi DB slot 4 with SSID ""
[  OK  ] DietPi-WiFiDB | chown root:root /var/lib/dietpi/dietpi-wifi.db /etc/wpa_supplicant/wpa_supplicant.conf
[  OK  ] DietPi-WiFiDB | chmod 600 /var/lib/dietpi/dietpi-wifi.db /etc/wpa_supplicant/wpa_supplicant.conf
[ SUB1 ] DietPi-Set_hardware > wifimodules (enable)
[ INFO ] DietPi-Set_hardware | Please wait, enabling WiFi modules...
[  OK  ] DietPi-Set_hardware | modprobe cfg80211
[  OK  ] DietPi-Set_hardware | modprobe brcmfmac
[  OK  ] DietPi-Set_hardware | modprobe brcmutil
[ INFO ] DietPi-Set_hardware | Checking for required APT packages: iw wireless-tools wpasupplicant wireless-regdb
[  OK  ] wifimodules enable | Completed
[ INFO ] DietPi-Config | Restarting network connections, please wait...
[  OK  ] DietPi-Config | systemctl daemon-reload
[ INFO ] DietPi-Config | systemctl restart ifup@eth0, please wait...
Mar 08 11:21:37 RPi8 systemd[1]: Stopping ifup@eth0.service - ifup for eth0...
Mar 08 11:21:38 RPi8 systemd[1]: ifup@eth0.service: Deactivated successfully.
Mar 08 11:21:38 RPi8 systemd[1]: Stopped ifup@eth0.service - ifup for eth0.
Mar 08 11:21:38 RPi8 systemd[1]: Starting ifup@eth0.service - ifup for eth0...
Mar 08 11:21:38 RPi8 systemd[1]: Finished ifup@eth0.service - ifup for eth0.
[  OK  ] DietPi-Config | systemctl restart ifup@eth0
[ INFO ] DietPi-Config | systemctl restart ifup@wlan0, please wait...
Mar 08 11:21:38 RPi8 systemd[1]: Starting ifup@wlan0.service - ifup for wlan0...
Mar 08 11:21:38 RPi8 wpa_supplicant[24351]: Successfully initialized wpa_supplicant
Mar 08 11:21:38 RPi8 wpa_supplicant[24351]: nl80211: kernel reports: Match already configured
Mar 08 11:21:38 RPi8 wpa_supplicant[24351]: nl80211: kernel reports: Match already configured
Mar 08 11:21:38 RPi8 wpa_supplicant[24351]: nl80211: kernel reports: Match already configured
Mar 08 11:21:38 RPi8 wpa_supplicant[24351]: nl80211: kernel reports: Match already configured
Mar 08 11:21:38 RPi8 wpa_supplicant[24351]: nl80211: kernel reports: Match already configured
Mar 08 11:21:38 RPi8 wpa_supplicant[24351]: nl80211: kernel reports: Match already configured
Mar 08 11:21:38 RPi8 wpa_supplicant[24351]: nl80211: kernel reports: Match already configured
Mar 08 11:21:38 RPi8 wpa_supplicant[24351]: nl80211: kernel reports: Match already configured
Mar 08 11:21:38 RPi8 wpa_supplicant[24351]: nl80211: kernel reports: Match already configured
Mar 08 11:21:38 RPi8 wpa_supplicant[24351]: nl80211: kernel reports: Match already configured
Mar 08 11:21:38 RPi8 wpa_supplicant[24351]: nl80211: kernel reports: Match already configured
Mar 08 11:21:38 RPi8 wpa_supplicant[24351]: nl80211: kernel reports: Match already configured
Mar 08 11:21:38 RPi8 wpa_supplicant[24351]: nl80211: kernel reports: Match already configured
Mar 08 11:21:38 RPi8 wpa_supplicant[24351]: nl80211: kernel reports: Match already configured
Mar 08 11:21:38 RPi8 wpa_supplicant[24351]: nl80211: kernel reports: Match already configured
Mar 08 11:21:38 RPi8 wpa_supplicant[24351]: nl80211: kernel reports: Match already configured
Mar 08 11:21:38 RPi8 wpa_supplicant[24351]: nl80211: kernel reports: Match already configured
Mar 08 11:21:38 RPi8 wpa_supplicant[24351]: nl80211: kernel reports: Match already configured
Mar 08 11:21:38 RPi8 wpa_supplicant[24351]: nl80211: kernel reports: Match already configured
Mar 08 11:21:38 RPi8 wpa_supplicant[24351]: nl80211: kernel reports: Match already configured
Mar 08 11:21:38 RPi8 wpa_supplicant[24351]: nl80211: kernel reports: Match already configured
Mar 08 11:21:38 RPi8 wpa_supplicant[24351]: nl80211: kernel reports: Match already configured
Mar 08 11:21:38 RPi8 wpa_supplicant[24351]: nl80211: kernel reports: Match already configured
Mar 08 11:21:38 RPi8 wpa_supplicant[24351]: nl80211: kernel reports: Match already configured
Mar 08 11:21:38 RPi8 wpa_supplicant[24351]: nl80211: kernel reports: Match already configured
Mar 08 11:21:38 RPi8 wpa_supplicant[24351]: nl80211: kernel reports: Match already configured
Mar 08 11:21:38 RPi8 wpa_supplicant[24351]: nl80211: kernel reports: Match already configured
Mar 08 11:21:38 RPi8 wpa_supplicant[24351]: nl80211: kernel reports: Match already configured
Mar 08 11:21:38 RPi8 wpa_supplicant[24351]: ctrl_iface exists and seems to be in use - cannot override it
Mar 08 11:21:38 RPi8 wpa_supplicant[24351]: Delete '/run/wpa_supplicant/wlan0' manually if it is not used anymore
Mar 08 11:21:38 RPi8 wpa_supplicant[24351]: Failed to initialize control interface 'DIR=/run/wpa_supplicant GROUP=netdev'.
                                            You may have another wpa_supplicant process already running or the file was
                                            left by an unclean termination of wpa_supplicant in which case you will need
                                            to manually remove this file before starting wpa_supplicant again.
Mar 08 11:21:38 RPi8 wpa_supplicant[24351]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Mar 08 11:21:38 RPi8 wpa_supplicant[24351]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Mar 08 11:21:38 RPi8 wpa_supplicant[24351]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Job for ifup@wlan0.service failed because the control process exited with error code.
See "systemctl status ifup@wlan0.service" and "journalctl -xeu ifup@wlan0.service" for details.
[FAILED] DietPi-Config | systemctl restart ifup@wlan0
[ INFO ] DietPi-Config | Reloading networking data, please wait...
[  OK  ] DietPi-Config | Network restarted

Joulinar · 8 March 2025 10:23

try to reboot and check if your settings survive. Maybe the manual ifdown clear stuff

Niaz · 8 March 2025 10:30

The connection works after ifdown and ifup. But doesn’t survive a reboot.

Even dietpi-config shows this weird change:

WiFi         : Not Found | [On] | Disconnected
Onboard WiFi : [Off]

Joulinar · 8 March 2025 10:43

can you try to toggle onboard WIFI to on and reboot

Niaz · 8 March 2025 10:51

It stayed on, but no connection.

Joulinar · 8 March 2025 11:03

does this changed after switching onboard WiFo on?

Niaz · 8 March 2025 11:06

Yes, it’s:

WiFi         : Available | [On] | Disconnected

Joulinar · 8 March 2025 11:19

and if you try to reconfigure again?

Niaz · 8 March 2025 11:31

Failed again:

Mar 08 12:29:27 RPi8 systemd[1]: Starting ifup@wlan0.service - ifup for wlan0...
Mar 08 12:29:27 RPi8 wpa_supplicant[2761]: Successfully initialized wpa_supplicant
Mar 08 12:29:27 RPi8 wpa_supplicant[2761]: nl80211: kernel reports: Registration to specific type not supported
Mar 08 12:29:27 RPi8 ifup[2768]: Error: ipv4: Address already assigned.
Mar 08 12:29:27 RPi8 ifup[2747]: ifup: failed to bring up wlan0
Mar 08 12:29:27 RPi8 systemd[1]: ifup@wlan0.service: Main process exited, code=exited, status=1/FAILURE
Mar 08 12:29:27 RPi8 wpa_supplicant[2765]: p2p-dev-wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Mar 08 12:29:27 RPi8 wpa_supplicant[2765]: p2p-dev-wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Mar 08 12:29:27 RPi8 wpa_supplicant[2765]: nl80211: deinit ifname=p2p-dev-wlan0 disabled_11b_rates=0
Mar 08 12:29:27 RPi8 wpa_supplicant[2765]: p2p-dev-wlan0: CTRL-EVENT-TERMINATING
Mar 08 12:29:27 RPi8 wpa_supplicant[2765]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Mar 08 12:29:27 RPi8 wpa_supplicant[2765]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Mar 08 12:29:27 RPi8 wpa_supplicant[2765]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Job for ifup@wlan0.service failed because the control process exited with error code.
See "systemctl status ifup@wlan0.service" and "journalctl -xeu ifup@wlan0.service" for details.
[FAILED] DietPi-Config | systemctl restart ifup@wlan0
[ INFO ] DietPi-Config | Reloading networking data, please wait...
[  OK  ] DietPi-Config | Network restarted

Once again it says Error: ipv4: Address already assigned. Weird.

Niaz · 8 March 2025 12:44

I’ve changed my setting to DHCP and unhid my SSID to simplify things.

The setting through dietpi-config can load the DHCP setting for the adapter but still fails to bring connection live.

The error that’s common with the previous setting is this:

wpa_supplicant[4298]: nl80211: kernel reports: Registration to specific type not supported

So, I guess the problem is somewhere there, but google is no help to me.