We are trying to simplify the network configuration of our embedded Linux product. We use the 802.11ah module with 802.11s using the morse version of the wpa_supplicant. We are on Morse versions 1_12_4
When we eliminated NetworkManager from our Linux system, we encounter a strange situation. The AP starts, but then the supplicant encounters an error “mesh join error=-114” and then just sits there. If we use systemd to restart the wpa_supplicant then it properly joins the already present 802.11s network.
I would need to know your host processor architecture to be sure, but on two of the platforms I have at hand, -114 is errno EALREADY - “Operation already in progress”.
This could indicate a running service is already trying to interact with the interface. It sounds like that shouldn’t be NetworkManager, as you have removed that.
When you see the mesh join error, is that in the logs from the wpa_supplicant started by systemd? Or a console output from you running wpa_supplicant manually?
Greetings. I am getting that error code from a supplicant started by systemd. Nothing else should be accessing the radio at that point. My platform is armv7.
I can confirm that -114 is EALREADY for this architecture.
Can you try set a long delay in the automatic service start with something like ExecStartPre=/bin/sleep 30 in the systemd unit file. I’m curious if this is related to some early init condition of the system.
