RRM: Ignoring radio measurement request: Not RRM network

Troubleshooting
1

Required Information

DietPi version | cat /boot/dietpi/.version
G_DIETPI_VERSION_CORE=8
G_DIETPI_VERSION_SUB=16
G_DIETPI_VERSION_RC=2
G_GITBRANCH=‘master’
G_GITOWNER=‘MichaIng’
Distro version | echo $G_DISTRO_NAME $G_RASPBIAN
bullseye 0
Kernel version | uname -a
Linux DietPi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux
SBC model | echo $G_HW_MODEL_NAME or (EG: RPi3)
RPi 3 Model B+ (aarch64)
Power supply used | (EG: 5V 1A RAVpower)
5V 3A
SD card used | (EG: SanDisk ultra)
SanDisk 32GBDietPi v8.16.2 : 15:46 - Thu 04/13/23
Device model : RPi 3 Model B+ (aarch64)

In a brand new install with Log System set to Full syslog keeps on showing the following message every few seconds non-stop:

May  1 21:07:28 DietPi wpa_supplicant[348]: RRM: Ignoring radio measurement request: Not RRM network
May  1 21:07:34 DietPi wpa_supplicant[348]: RRM: Ignoring radio measurement request: Not RRM network
May  1 21:07:40 DietPi wpa_supplicant[348]: RRM: Ignoring radio measurement request: Not RRM network
May  1 21:07:46 DietPi wpa_supplicant[348]: RRM: Ignoring radio measurement request: Not RRM network

WiFi signal is ok and connection is stable. I did not find a topic on this case in DietPi Forum but googled and read that you can decrease the verbosity of wpa_supplicant by using -q or even -qq.

So advice on whether such message is regarded as ok or should be fixed is appreciated.

2

I guess it should be fine to reduce log level

3

Thank you. I think I could edit

sudo nano /lib/systemd/system/wpa_supplicant.service
[Unit]
Description=WPA supplicant
Before=network.target
After=dbus.service
Wants=network.target
IgnoreOnIsolate=true

[Service]
Type=dbus
BusName=fi.w1.wpa_supplicant1
ExecStart=/sbin/wpa_supplicant -u -s -O /run/wpa_supplicant

[Install]
WantedBy=multi-user.target
Alias=dbus-fi.w1.wpa_supplicant1.service

and replace
ExecStart=/sbin/wpa_supplicant -u -s -O /run/wpa_supplicant
with
ExecStart=/sbin/wpa_supplicant -u -s -O -qq /run/wpa_supplicant
for even less verbosity.

I have both eth0 and wlan0 enabled on purpose (test and try which has preference over the other and whether preference can be set)

dietpi@DietPi:~$ sudo ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether aa:aa:aa:aa:aa:aa brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.10/24 brd 192.168.1.255 scope global dynamic eth0
       valid_lft 6828sec preferred_lft 6828sec
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether aa:aa:aa:aa:aa:ab brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.12/24 brd 192.168.1.255 scope global dynamic wlan0
       valid_lft 6926sec preferred_lft 6926sec

Howver, the service seems to be disabled

dietpi@DietPi:~$ sudo systemctl status wpa_supplicant.service
● wpa_supplicant.service - WPA supplicant
     Loaded: loaded (/lib/systemd/system/wpa_supplicant.service; disabled; vendor preset: enabled)
     Active: inactive (dead)

So would editing
/lib/systemd/system/wpa_supplicant.service
be ok? Or additional steps needed? Thank you in advance!

4

Do not edit the service files directly, the changes will not persist the next update.
Use dietpi-services to modify you servive files.

In the edited file you should then have to uncomment the ExecStart line and insert another one, like this:

ExecStart=
ExecStart=/sbin/wpa_supplicant -u -s -O -qq /run/wpa_supplicant

The service is loaded, looks fine to me.

5

Thank you for your feedback. Little doubt now, wpa_supplicant service is not showing via dietpi-services:

image
image968×484 8.19 KB

So, should I add a new service with the Add option?

6

Hmm let’s wait what the more experienced members recommend to do.

7

we don’t show the service there. However you could add it by hitting the Add button. Or you adjust the service manually. :smiley:

8

Thank you. I chose the second option (manually) so,

dietpi@DietPi:~$ sudo cat /lib/systemd/system/wpa_supplicant.service
[Unit]
Description=WPA supplicant
Before=network.target
After=dbus.service
Wants=network.target
IgnoreOnIsolate=true

[Service]
Type=dbus
BusName=fi.w1.wpa_supplicant1
#ExecStart=/sbin/wpa_supplicant -u -s -O /run/wpa_supplicant
ExecStart=/sbin/wpa_supplicant -u -s -qq -O /run/wpa_supplicant

[Install]
WantedBy=multi-user.target
Alias=dbus-fi.w1.wpa_supplicant1.service

Rebooted and still,

dietpi@DietPi:~$ sudo tail -f /var/log/syslog
May  3 08:31:57 DietPi wpa_supplicant[349]: RRM: Ignoring radio measurement request: Not RRM network
May  3 08:32:03 DietPi wpa_supplicant[349]: RRM: Ignoring radio measurement request: Not RRM network
May  3 08:32:09 DietPi wpa_supplicant[349]: RRM: Ignoring radio measurement request: Not RRM network
May  3 08:32:21 DietPi wpa_supplicant[349]: RRM: Ignoring radio measurement request: Not RRM network

I noticed thogh, that wpa_supplicant is running with different parameters -s -B -P instead of expected -u -s -qq


dietpi@DietPi:~$ ps aux | grep wpa
root         349  0.0  0.1  13980  1376 ?        Ss   07:40   0:00 /sbin/wpa_supplicant -s -B -P /run/wpa_supplicant.wlan0.pid -i wlan0 -D nl80211,wext -c /etc/wpa_supplicant/wpa_supplicant.conf

Please, any ideas on how to advance?

9

maybe @MichaIng could have a look

10

I think you have to modify it to

#ExecStart=/sbin/wpa_supplicant -u -s -O /run/wpa_supplicant
ExecStart=
ExecStart=/sbin/wpa_supplicant -u -s -qq -O /run/wpa_supplicant
11

Is there a reason you enabled wpa_supplicant.service? It is not used by default, instead ifup invokes a dedicated wpa_supplicant process for each configured WiFi interface, which is the process with the different arguments you see.

The wpa_supplicant call from the service with -u flag but without any interface defined is aimed to be controlled via DBus interface. So I guess it is meant to be used by 3rd party network software to dynamically toggle WPA for interfaces, like AFAIK NetworkManager does it. Not sure what this RRM network log is about. There is tons of search results about this, but at a quick view I only found the same -qq flag info to mute it instead of any helpful information what it means and how to stop wpa_supplicant from trying to do what it does to trigger this message. However, as long as you do not intentionally use NetworkManager or something else, just disable this service:

systemctl disable --now wpa_supplicant

And to assure there is not unintentionally NetworkManager installed:

dpkg-query -s network-manager && systemctl status NetworkManager
12

Thank you all for your valuable feedback. @MichaIng the only reason I edited wpa_supplicant.service was to add the -q parameter and see whether it would stop syslog showing all those RRM: Ignoring radio measurement request: Not RRM network messages

dietpi@DietPi:~$ dpkg-query -s network-manager
dpkg-query: package 'network-manager' is not installed and no information is available
Use dpkg --info (= dpkg-deb --info) to examine archive files.

dietpi@DietPi:~$ sudo systemctl status NetworkManager
Unit NetworkManager.service could not be found.

Anyhow, in the end I switched to eth0 but leave this topic open for anyone to jump in at any time.

Thank you once more.

13

Since ifupdown starts wpa_supplicant, this would need to be added in the related script in one of the /etc/network/if-*up.d/wpasupplicant scripts.