[SOLVED] nl80211: kernel reports: Match already configured

othersamo_ · 2022-01-14 19:02:05

Hello,
I get the following set of error messages on every boot occasion:
https://pastebin.com/sZDbcbR5

I suspect this has to do something with interfering with NetworkManager and netctl-auto.
This started happening when I tried to set up automatic wifi connecting at the boot which works, just my journal gets clogged up with those error messages.
I am quite confused what causes it.
I tried steps in this tread but it ended in wifi connection loss: https://unix.stackexchange.com/question … but-yet-wl

On the other hand, I get this when running wifi-menu:

Interface 'wlp4s0' is controlled by netctl-auto

Any help would be appreciated

Last edited by othersamo_ (2022-01-18 21:10:18)

Head_on_a_Stick · 2022-01-14 19:07:17

othersamo_ wrote:

I suspect this has to do something with interfering with NetworkManager and netctl-auto.

Why are you using both?

Please post the output of

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

othersamo_ · 2022-01-14 19:16:04

Head_on_a_Stick wrote:

othersamo_ wrote:
I suspect this has to do something with interfering with NetworkManager and netctl-auto.
Why are you using both?
Please post the output of
find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

Here is the output

bluetooth.service                        | bluetooth.target.wants
dbus-org.bluez.service                   | system
dbus-org.freedesktop.nm-dispatcher.service | system
dirmngr.socket                           | sockets.target.wants
display-manager.service                  | system
gcr-ssh-agent.socket                     | sockets.target.wants
getty@tty1.service                       | getty.target.wants
gpg-agent-browser.socket                 | sockets.target.wants
gpg-agent-extra.socket                   | sockets.target.wants
gpg-agent.socket                         | sockets.target.wants
gpg-agent-ssh.socket                     | sockets.target.wants
netctl-auto@wlp4s0.service               | sys-subsystem-net-devices-wlp4s0.device.wants
NetworkManager.service                   | multi-user.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
ntpd.service                             | multi-user.target.wants
p11-kit-server.socket                    | sockets.target.wants
pulseaudio.socket                        | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
ufw.service                              | multi-user.target.wants
xdg-user-dirs-update.service             | default.target.wants

Head_on_a_Stick · 2022-01-14 19:36:39

Once more: why are you using both netctl and NetworkManager? Using multiple networking applications on the same interface may cause conflicts, as you have already noted.

And please don't full-quote unnecessarily. It really winds me up.

othersamo_ · 2022-01-14 20:02:41

Head_on_a_Stick wrote:

Once more: why are you using both netctl and NetworkManager? Using multiple networking applications on the same interface may cause conflicts, as you have already noted.

I started with NetworkManager but on the first sight it seemed as it was unable to connect me, so I went to netctl-auto. Does it look as NetworkManager with WPA supplicant is taking care of auto wifi startup at the bginning, respectively how can I determine which one does? The problem is no matter of which one I stop, wifi won't work at all, and not even start automatically.

Last edited by othersamo_ (2022-01-14 20:05:35)

seth · 2022-01-14 20:30:08

Disable the netctl-auto service, reboot, try to connect to the wifi and then post a complete system journal ("sudo journalctl -b | curl -F 'f:1=<-' ix.io")

othersamo_ · 2022-01-14 21:11:23

seth wrote:

Disable the netctl-auto service, reboot, try to connect to the wifi and then post a complete system journal ("sudo journalctl -b | curl -F 'f:1=<-' ix.io")

I was unable to connect to wifi:
https://imgur.com/a/UTlFlj9

Here is what happened, I tried wifi-menu

seth · 2022-01-14 21:14:23

Running wifi-menu while networkmanager is controlling the NIC won't work.
We need the journal - if there's no wired connection on that system, you can maybe use https://wiki.archlinux.org/title/Tethering
Otherwise redirect the journal into a file, usb-walk that to a machine w/ Internet connection and upload it from there.

othersamo_ · 2022-01-14 22:05:13

seth wrote:

Running wifi-menu while networkmanager is controlling the NIC won't work.
We need the journal - if there's no wired connection on that system, you can maybe use https://wiki.archlinux.org/title/Tethering
Otherwise redirect the journal into a file, usb-walk that to a machine w/ Internet connection and upload it from there.

Right, here is the journal: https://ufile.io/w7rpcxuc

seth · 2022-01-15 08:22:52

There's only networkmanager, no crash in the iwlwifidriver, NM is scanning around a bit, but there's no attempt being made to connect to any AP?
Are you somehow looking for https://wiki.archlinux.org/title/Networ … et_on_boot ?

othersamo_ · 2022-01-15 13:24:33

seth wrote:

There's only networkmanager, no crash in the iwlwifidriver, NM is scanning around a bit, but there's no attempt being made to connect to any AP?

Well, I get connected to wifi right after logging to XFCE. Stopping netctl-auto resulted in no wifi connection.
I figured out that NetworkManager.service cares about the auto wifi startup on boot, it is not reliable, though (sometimes I get connected, sometimes not). When the service is disabled, I won't get connected automatically but I can connect through wifi-menu.

Are you somehow looking for https://wiki.archlinux.org/title/Networ … et_on_boot ?

Yes, this is one of the options. I installed the applet but is says "device not ready" under wifi options. This happens even though I am normally connected to wifi.

Last edited by othersamo_ (2022-01-15 13:42:41)

seth · 2022-01-15 14:12:34

Well, I get connected to wifi right after logging to XFCE.

Not according to the journal you posted. Not w/ NM nor with anything else.

I figured out that NetworkManager.service cares about the auto wifi startup on boot.

Only if you configure it according to the link I posted in #10 - otherwise at best w/ the session login, but again: not during the brief boot for the journal you posted.

I installed the applet but is says "device not ready" under wifi options.

Not sure what that means, but you'll have to have NM running and NO OTHER service dogging on the NIC (in this case likely netctl-auto)

othersamo_ · 2022-01-18 21:09:13

Right, thank you. Complete removal of netctl components solved the issue.

Arch Linux

#1 2022-01-14 19:02:05

[SOLVED] nl80211: kernel reports: Match already configured

#2 2022-01-14 19:07:17

Re: [SOLVED] nl80211: kernel reports: Match already configured

#3 2022-01-14 19:16:04

Re: [SOLVED] nl80211: kernel reports: Match already configured

#4 2022-01-14 19:36:39

Re: [SOLVED] nl80211: kernel reports: Match already configured

#5 2022-01-14 20:02:41

Re: [SOLVED] nl80211: kernel reports: Match already configured

#6 2022-01-14 20:30:08

Re: [SOLVED] nl80211: kernel reports: Match already configured

#7 2022-01-14 21:11:23

Re: [SOLVED] nl80211: kernel reports: Match already configured

#8 2022-01-14 21:14:23

Re: [SOLVED] nl80211: kernel reports: Match already configured

#9 2022-01-14 22:05:13

Re: [SOLVED] nl80211: kernel reports: Match already configured

#10 2022-01-15 08:22:52

Re: [SOLVED] nl80211: kernel reports: Match already configured

#11 2022-01-15 13:24:33

Re: [SOLVED] nl80211: kernel reports: Match already configured

#12 2022-01-15 14:12:34

Re: [SOLVED] nl80211: kernel reports: Match already configured

#13 2022-01-18 21:09:13

Re: [SOLVED] nl80211: kernel reports: Match already configured

Board footer