Wi-Fi device stuck in loop when using AP Mode

Product support balenaOS
1

Hi all,

After some time, I was finally able to create an access point for my device.
But after some tweaking with the settings, after some disconnection and activation of the Wi-Fi device, it’s stuck in some sort of loop.

I get the following errors while diagnosing via nmcli dev:

(process:365): GLib-GIO-WARNING **: ../../glib-2.54.3/gio/gdbusobjectmanagerclient.c:1585: Processing InterfaceRemoved signal for path /org/freedesktop/NetworkManager/ActiveConnection/2542 but no object proxy exists

(process:365): GLib-GIO-WARNING **: ../../glib-2.54.3/gio/gdbusobjectmanagerclient.c:1585: Processing InterfaceRemoved signal for path /org/freedesktop/NetworkManager/AccessPoint/2574 but no object proxy exists

I don’t know where the ActiveConnection/2542 or AccessPoint/2574 are coming from, because I haven’t created that many connections. But these are the errors/warnings that are visible when the wlp4s0 is stuck in a loop.

The loop is the following while using nmcli dev monitor wlp4s0:

(process:32051): GLib-GIO-WARNING **: ../../glib-2.54.3/gio/gdbusobjectmanagerclient.c:1585: Processing InterfaceRemoved signal for path /org/freedesktop/NetworkManager/ActiveConnection/509 but no object proxy exists

(process:32051): GLib-GIO-WARNING **: ../../glib-2.54.3/gio/gdbusobjectmanagerclient.c:1585: Processing InterfaceRemoved signal for path /org/freedesktop/NetworkManager/AccessPoint/541 but no object proxy exists

wlp4s0: disconnected
wlp4s0: connecting (prepare)
wlp4s0: using connection 'AP.7E332M010186A55D79'
wlp4s0: connecting (configuring)
wlp4s0: connection failed
wlp4s0: disconnected
wlp4s0: connecting (prepare)
wlp4s0: using connection 'AP.7E332M010186A55D79'
wlp4s0: connecting (configuring)
wlp4s0: connection failed

And it continues to do that on and on.

Some information:
Hardware: UP Squared
BalenaOS: 2.39.0+rev1 (Development)
Supervisor: 10.1.5

When a container starts, it forces to update the current connection file (because there might be changes), then disconnects wlp4s0 and activates the connection. So maybe this is causing problems, but if somebody has a suggestion to push changes to the connection, I’ll be all ears.

Thanks in advance!

2

Just some added information, this is the nmconnection file:

[connection]
id=AP.7E332M010186A55D79
uuid=07311413-93b0-42c5-9c68-e2759fa9cbbc
type=wifi
permissions=

[wifi]
band=bg
mac-address-blacklist=
mode=ap
ssid=7E332M010186A55D79

[wifi-security]
auth-alg=open
key-mgmt=wpa-psk
proto=rsn;
psk=aPFUtNxjNxSl3BrZrN45MqlJ8Q5abG

[ipv4]
address1=172.24.1.1/24
dns-search=
method=shared

[ipv6]
addr-gen-mode=stable-privacy
dns-search=
method=ignore
3

When a container starts, it forces to update the current connection file (because there might be changes), then disconnects wlp4s0 and activates the connection. So maybe this is causing problems, but if somebody has a suggestion to push changes to the connection, I’ll be all ears.

Could you share some more details about how the container achieves this? Like the script it runs. Is it using the DBUS interface? If helpful, I have found the following resources that appear relevant:

7

I’m sorry for the late reply. The feature that needs the AP in our project is currently on hold. Other features got a higher priority right now. I’ll keep you posted if there are any changes!