I'm running Debian GNU/Linux 12 (bookworm) on Raspberry Pi 4 Model B Rev 1.1 and tried to boot with wlan on but some static IPv4. I got wlan and DHCP working yesterday but did some extra-clever moves this morning. These screwed my pi and I'd really appreciate some help for I'm lost now. I can log in via cable on eth0 and this is how it looks:
signal@192.168.178.43's password:
Linux signal 6.12.25+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.12.25-1+rpt1 (2025-04-30) aarch64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sat May 17 11:19:52 2025 from 192.168.178.20
signal@signal:~ $ ip l
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
link/ether dc:a6:32:38:a4:1a brd ff:ff:ff:ff:ff:ff
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
link/ether dc:a6:32:38:a4:1b brd ff:ff:ff:ff:ff:ff
...
No wlan switched on, doing it by hand like said here:
signal@signal:~ $ sudo wpa_supplicant -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf &
[1] 1708
signal@signal:~ $ Successfully initialized wpa_supplicant
nl80211: kernel reports: Registration to specific type not supported
wlan0: Trying to associate with e0:28:6d:b5:c5:a5 (SSID='hare-aerie1' freq=5260 MHz)
wlan0: Associated with e0:28:6d:b5:c5:a5
wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
wlan0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=DE
wlan0: WPA: Key negotiation completed with e0:28:6d:b5:c5:a5 [PTK=CCMP GTK=CCMP]
wlan0: CTRL-EVENT-CONNECTED - Connection to e0:28:6d:b5:c5:a5 completed [id=0 id_str=home]
signal@signal:~ $ ip l
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
link/ether dc:a6:32:38:a4:1a brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DORMANT group default qlen 1000
link/ether dc:a6:32:38:a4:1b brd ff:ff:ff:ff:ff:ff
...
Now wlan is on and the router does report the pi connected with IPv4 .119 and connecting via ssh works fine but still ...
signal@signal:~ $ sudo ip l
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
link/ether dc:a6:32:38:a4:1a brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DORMANT group default qlen 1000
link/ether dc:a6:32:38:a4:1b brd ff:ff:ff:ff:ff:ff
...
First question: Why is wlan said to be UP mode DORMANT and without an IPv4 while the router / DHCP-service from the other side knows the .119-raspberry very well and can connect?
Second question: After the reboot wlan0 is not started again automatically. How to change that?
Any help is very appreciated by
Chris
