Hi all, co-worker of @Airum here.
I’ve done a few tests on the wifi, and the results have been strangely inconsistent as stated above. These are the logs of the wifi service from my most recent test.
Starting WiFi Connect
Deleting already created by WiFi Connect access point connection profile: "TAGe-WiFi"
Error: D-Bus failure: Get org.freedesktop.NetworkManager.Device::Interface property failed on /org/freedesktop/NetworkManager/Devices/20: No such interface 'org.freedesktop.DBus.Properties' on object at path /org/freedesktop/NetworkManager/Devices/20
caused by: "No such interface \'org.freedesktop.DBus.Properties\' on object at path /org/freedesktop/NetworkManager/Devices/20"
I should mention that we are using the most recent version of the wifi-connect service. The only modification made was to hardcode the Dockerfile to pull the correct image/executable for our architecture (aarch64
). For some reason the environment variables the original Dockerfile used were pulling the wrong versions, even though looking at the documentation it should have pulled the correct ones (but that’s a separate issue).
Looking at dmesg
, I see these lines as being the most relevant:
[ 5.397386] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 5390, rev 0502 detected
[ 5.427759] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 5370 detected
[ 5.435915] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
...
[ 6.521652] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin'
[ 6.531580] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.36
...
[ 14.918885] ieee80211 phy0: rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x1700 with error -71
...
[ 16.365390] ieee80211 phy1: rt2x00_set_rt: Info - RT chipset 5390, rev 0502 detected
[ 16.395764] ieee80211 phy1: rt2x00_set_rf: Info - RF chipset 5370 detected
[ 16.397554] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
...
[ 16.423152] ieee80211 phy1: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin'
[ 16.432748] ieee80211 phy1: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.36
There were also several lines that said IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
, and one that said IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
, despite the fact that the wifi wasn’t configured.
So it looks as if the chipset was detected and the firmware loaded, but then it ran into an error getting the vendor code from the dongle, so it started the process over again.
After checking all this, I noticed that the wifi’s AP was broadcasting, so I connected to it and gave it wifi credentials, and it connected up right away. This is also strange, as lately it has taken a few tries to get it to A) see the right network and B) connect. Checking the logs, it looks like it worked right away, and the old logs about the D-Bus error were gone.
Starting WiFi Connect
WiFi device: wlan0
Access points: [<REDACTED>]
Starting access point...
Access point 'TAGe-WiFi' created
Starting HTTP server on 192.168.42.1:80
request error = Header
User connected to the captive portal
request error = Header
request error = Header
Stopping access point 'TAGe-WiFi'...
Access point 'TAGe-WiFi' stopped
Access points: [<REDACTED>]
Connecting to access point <REDACTED>...
Internet connectivity established
It looks as if the container restarted itself (I did not set the restart
parameter in the compose file) and had no issues.
I’ll be honest, I have no clue what’s going on here.