Luci is not accesible | nl80211: kernel reports: key addition failed

Hello everyone,

I have a simple setup as follows:
AP1<---ethernet-->meshNode1<===80211s===>meshNode2<--ethernet---->AP2

I get internet access through the two APs and the two meshNodes connect over 5 ghz wifi. All the 4 nodes are running batman-adv which I primarily have for ferrying vlans over the whole network.
All 4 nodes are TP link onhubs and running 23.05.5.

Recently I have started to have two problems:

  1. I cannot access Luci for AP2 if I am not directly connected to AP2. I go to the address and it just never finishes loading. Luci works for AP1 no matter which AP I am connected to.

    • ping works between AP1 and AP2.
    • batctl traceroute works.
    • I can ssh into AP2
    • If I directly connect to AP2 using a wifi ssid exclusive to that, I can access luci just fine.
    • I have tried resetting AP2 and uploading a backup and I still get the same problem.
  2. I am seeing the below errors consistently in the logs for both AP1 and AP2:

Fri Nov  1 14:54:21 2024 daemon.err hostapd: nl80211: kernel reports: key addition failed
Fri Nov  1 15:02:16 2024 daemon.err hostapd: nl80211: kernel reports: key addition failed
Fri Nov  1 15:06:55 2024 daemon.err hostapd: nl80211: kernel reports: key addition failed
Fri Nov  1 15:07:05 2024 daemon.err hostapd: nl80211: kernel reports: key addition failed
Fri Nov  1 15:07:16 2024 daemon.err hostapd: nl80211: kernel reports: key addition failed
Fri Nov  1 15:22:57 2024 daemon.err hostapd: nl80211: kernel reports: key addition failed

Sometimes I have to reboot the APs as the internet will stop working, and everytime that happens, I check the logs and there is a flood of these messages. Note that I have been running 23.05.5 for almost 4 weeks and this has only started to happen in the last 7 days. I really don't know what to do here. Searching through the forum it seems it's related to 80211r and I have tried disabling that on both APs and still does not help.

If anyone has any tips to debug this, would be helpful. I am out of options and I need internet to work reliably.

Thanks

meshing.

Turns out it was vlan problem. One side was using vlan and the other side was not. So i had to untag the cpu port and also use the hardware interface name. That fixed it.

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.