Wifi connection fails, Colibri iMX8X

uwdlg · January 23, 2025, 1:37pm

Hi,
I want to switch from a wired connection to wireless, so I ran nmcli -a device wifi connect <WIFI_NAME> in a host console and successfully connected to my WLAN. I then unplugged the ethernet cable and manually added my device in the VS Code extension using its new IP, port 22 and the torizon user and password, which also worked, including being able to access the Portainer web GUI via the new WLAN IP. I then set that device as default and tried to run something on it, but the connection always fails after some time. The device still shows up with the same IP in my router, but pings (from other devices in the same network and WSL2) give “Destination host unreachable”:

ping 192.168.178.94
PING 192.168.178.94 (192.168.178.94) 56(84) bytes of data.
From 192.168.178.29 icmp_seq=3 Destination Host Unreachable

…where .94 is the board and .29 is my dev machine with WSL2 and the VS Code extension.
I can unplug and restart the board to temporarily “repair” the connection, but after a while the same thing happens. Am I doing something wrong / what can I do to fix this?

ToradexAI · January 23, 2025, 1:39pm

Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!

Did you like my answer?

Hello,

I’m sorry to hear about the Wi-Fi connectivity issues you’re experiencing with your Colibri iMX8X. Let’s go through some steps that might help resolve this problem:

Network Configuration:
- Double-check that your Wi-Fi network settings, such as the SSID and password, are correctly configured.
- Ensure that your network manager is set to automatically reconnect to the Wi-Fi network if the connection drops.
Power Management Settings:
- Sometimes, power-saving modes can cause the Wi-Fi to disconnect. Check if power management settings are affecting the Wi-Fi module and adjust them if necessary. You can do this using nmcli or by editing the network configuration files.
Signal Strength and Interference:
- Make sure the Wi-Fi signal is strong and consistent. Weak signals can lead to intermittent connectivity.
- Look for potential sources of interference, such as other electronic devices or physical obstructions between the router and your Colibri iMX8X.
Driver and Firmware Updates:
- Ensure that the Wi-Fi drivers and firmware on your Colibri iMX8X are up to date, as outdated drivers can cause connectivity issues.
Router Configuration:
- Check that your router is not limiting the number of connected devices or has settings that might cause disconnections.
- Rebooting the router can sometimes resolve temporary issues.
Logs and Diagnostics:
- Review the system logs on your Colibri iMX8X for any error messages related to the Wi-Fi connection. This can provide clues about the cause of the disconnection. Use dmesg or journalctl to view logs and look for any relevant entries.

By systematically checking these areas, you should be able to identify and resolve the cause of the Wi-Fi disconnections. If the issue persists, further investigation into your specific network environment may be necessary.

I hope this helps! If you have any more questions, feel free to ask.

Best regards,
Toradex AI Assistant.

Please, also check if these links can help you solve your problem:

Wifi throughput issue with Colibri IMX8QXP and TorizonCore.

collin.tx · January 23, 2025, 3:28pm

Dear @uwdlg ,

That is indeed interesting behaviour. I will try this out on my side too.
In the meantime I have two questions:

Which specific Torizon version are you using?
Are you using the antennas attached to the module? The use might make a difference in reception.

Best regards,
Collin

uwdlg · January 23, 2025, 4:33pm

This is the tdx-info output:

Software summary
------------------------------------------------------------
Bootloader:               U-Boot
Kernel version:           5.15.129-6.5.0+git.6f8fd49366db #1-TorizonCore SMP PREEMPT Fri Dec 22 11:15:52 UTC 2023
Kernel command line:      root=LABEL=otaroot rootfstype=ext4 quiet logo.nologo vt.global_cursor_default=0 plymouth.ignore-serial-consoles splash fbcon=map:3 ostree=/ostree/boot.1/torizon/7e7d5c182b8db9a981d1f942cee2a808b3535fa86862471d67f718c4959f44df/0
Distro name:              NAME="TorizonCore"
Distro version:           VERSION_ID=6.5.0-build.8
Distro variant:           VARIANT="Docker"
Hostname:                 colibri-imx8x-07329158
------------------------------------------------------------

Hardware info
------------------------------------------------------------
HW model:                 Toradex Colibri iMX8QXP on Colibri Evaluation Board V3
Toradex version:          0038 V1.0D
Serial number:            07329158
Processor arch:           aarch64
------------------------------------------------------------

I’m not sure about the antennas as someone else assembled everything (quite a while ago). There is enough reception in the beginning, I could now use it for some time (building a new container, manually running an application via a container console in Portainer) before the same problem occurred again.

collin.tx · January 27, 2025, 12:40pm

Dear @uwdlg,

I have been able to install the same version on my end on an identical module and have not experienced any such behaviour so far.

Could you maybe tell me at what exact point the connection is disrupted?
if checking the status via nmcli device status at different points in time, can you see that the connection is no longer established?
Would you be able to send us logs from the situation (nmcli and/or networkmanager)? Potentially you could make use of the persistent logging functionality: Persistent Journald Logging | Toradex Developer Center
Are you ever entering into any sleep or suspend modes? This might have an influence.

Best regards,
Collin

uwdlg · January 28, 2025, 4:11pm

Thank you for taking the time to try and reproduce my issue!
I tried to gather some helpful logs, but so far haven’t been able to reproduce it anymore myself (of course).
When/if it happens again, I’ll try to supply more useful logs.

collin.tx · January 29, 2025, 8:14am

I see. In that case I will just leave this ticket/thread open in case the issue arises again

uwdlg · January 30, 2025, 1:37pm

…it just did. After getting disconnected from 192.168.178.94, which is the tablet’s IP in the WLAN (network interface uap0) and getting ssh: connect to host 192.168.178.94 port 22: Connection timed out trying to reconnect via ssh, I connected the tablet via ethernet, ssh’d onto it via the LAN IP 192.168.178.89 and looked at the last 500 lines of journalctl, this should be the relevant parts where the WiFi connection drops up until I get an ethernet connection:

journalctl excerpt

Jan 30 13:07:14 colibri-imx8x-07329158 systemd-networkd[724]: uap0: Link DOWN
Jan 30 13:07:14 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242434.1148] device (uap0): set-hw-addr: set MAC address to 0E:10:47:42:EC:A5 (scanning)
Jan 30 13:07:14 colibri-imx8x-07329158 systemd-networkd[724]: uap0: Link UP
Jan 30 13:07:14 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242434.1206] device (uap0): supplicant interface state: disconnected -> interface_disabled
Jan 30 13:07:14 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242434.2254] device (uap0): supplicant interface state: interface_disabled -> inactive
Jan 30 13:07:39 colibri-imx8x-07329158 wpa_supplicant[872]: uap0: Reject scan trigger since one is already pending
Jan 30 13:08:56 colibri-imx8x-07329158 sshd[1732]: Timeout, client not responding from user torizon 192.168.178.29 port 61444
Jan 30 13:08:56 colibri-imx8x-07329158 sshd[1719]: pam_unix(sshd:session): session closed for user torizon
Jan 30 13:08:56 colibri-imx8x-07329158 systemd[1]: sshd@0-192.168.178.94:22-192.168.178.29:61444.service: Deactivated successfully.
Jan 30 13:08:56 colibri-imx8x-07329158 systemd[1]: session-c1.scope: Deactivated successfully.
Jan 30 13:08:56 colibri-imx8x-07329158 systemd-logind[697]: Removed session c1.
Jan 30 13:08:59 colibri-imx8x-07329158 sshd[2443]: Timeout, client not responding from user torizon 192.168.178.29 port 59900
Jan 30 13:08:59 colibri-imx8x-07329158 sshd[2441]: pam_unix(sshd:session): session closed for user torizon
Jan 30 13:08:59 colibri-imx8x-07329158 systemd[1]: sshd@2-192.168.178.94:22-192.168.178.29:59900.service: Deactivated successfully.
Jan 30 13:08:59 colibri-imx8x-07329158 systemd[1]: session-c3.scope: Deactivated successfully.
Jan 30 13:08:59 colibri-imx8x-07329158 systemd-logind[697]: Removed session c3.
Jan 30 13:09:09 colibri-imx8x-07329158 systemd[1]: Stopping User Manager for UID 1000...
Jan 30 13:09:09 colibri-imx8x-07329158 systemd[1726]: Activating special unit Exit the Session...
Jan 30 13:09:09 colibri-imx8x-07329158 systemd[1726]: Stopped target Main User Target.
Jan 30 13:09:09 colibri-imx8x-07329158 systemd[1726]: Stopped target Basic System.
Jan 30 13:09:09 colibri-imx8x-07329158 systemd[1726]: Stopped target Paths.
Jan 30 13:09:09 colibri-imx8x-07329158 systemd[1726]: Stopped target Sockets.
Jan 30 13:09:09 colibri-imx8x-07329158 systemd[1726]: Stopped target Timers.
Jan 30 13:09:09 colibri-imx8x-07329158 systemd[1726]: Closed D-Bus User Message Bus Socket.
Jan 30 13:09:09 colibri-imx8x-07329158 systemd[1726]: Removed slice User Application Slice.
Jan 30 13:09:09 colibri-imx8x-07329158 systemd[1726]: Reached target Shutdown.
Jan 30 13:09:09 colibri-imx8x-07329158 systemd[1726]: Finished Exit the Session.
Jan 30 13:09:09 colibri-imx8x-07329158 systemd[1726]: Reached target Exit the Session.
Jan 30 13:09:09 colibri-imx8x-07329158 systemd[1727]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8004 service=[systemd-user] terminal=[<unknown>] user=[torizon] ruser=[<unknown>] rhost=[<>
Jan 30 13:09:09 colibri-imx8x-07329158 systemd[1]: user@1000.service: Deactivated successfully.
Jan 30 13:09:09 colibri-imx8x-07329158 systemd[1]: Stopped User Manager for UID 1000.
Jan 30 13:09:09 colibri-imx8x-07329158 systemd[1]: Stopping User Runtime Directory /run/user/1000...
Jan 30 13:09:09 colibri-imx8x-07329158 systemd[1]: run-user-1000.mount: Deactivated successfully.
Jan 30 13:09:09 colibri-imx8x-07329158 systemd[1]: user-runtime-dir@1000.service: Deactivated successfully.
Jan 30 13:09:09 colibri-imx8x-07329158 systemd[1]: Stopped User Runtime Directory /run/user/1000.
Jan 30 13:09:09 colibri-imx8x-07329158 systemd[1]: Removed slice User Slice of UID 1000.
Jan 30 13:10:57 colibri-imx8x-07329158 systemd-timesyncd[675]: Timed out waiting for reply from 216.239.35.4:123 (time2.google.com).
Jan 30 13:11:07 colibri-imx8x-07329158 systemd-timesyncd[675]: Timed out waiting for reply from [2001:4860:4806:4::]:123 (time2.google.com).
Jan 30 13:11:49 colibri-imx8x-07329158 kernel: usb 1-1.2.1.4: new high-speed USB device number 9 using xhci-hcd
Jan 30 13:11:49 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242709.7364] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/15)
Jan 30 13:11:49 colibri-imx8x-07329158 kernel: ax88179_178a 1-1.2.1.4:1.0 eth0: register 'ax88179_178a' at usb-xhci-hcd.1.auto-1.2.1.4, ASIX AX88179 USB 3.0 Gigabit Ethernet, 00:0e:c6:a0:54:e0
Jan 30 13:11:49 colibri-imx8x-07329158 kernel: usbcore: registered new interface driver ax88179_178a
Jan 30 13:11:49 colibri-imx8x-07329158 systemd-udevd[3030]: Using default interface naming scheme 'v250'.
Jan 30 13:11:49 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242709.8099] device (eth0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jan 30 13:11:50 colibri-imx8x-07329158 systemd-networkd[724]: eth0: Link UP
Jan 30 13:11:50 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242710.1871] settings: (eth0): created default wired connection 'Wired connection 1'
Jan 30 13:11:52 colibri-imx8x-07329158 ModemManager[688]: <info>  [base-manager] couldn't check support for device '/sys/devices/platform/bus@5b000000/5b110000.usb/5b130000.usb/xhci-hcd.1.auto/usb1/1-1/1-1.2/1->
Jan 30 13:11:52 colibri-imx8x-07329158 kernel: ax88179_178a 1-1.2.1.4:1.0 eth0: ax88179 - Link status is: 1
Jan 30 13:11:52 colibri-imx8x-07329158 systemd-networkd[724]: eth0: Gained carrier
Jan 30 13:11:52 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242712.5347] device (eth0): carrier: link connected
Jan 30 13:11:52 colibri-imx8x-07329158 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Jan 30 13:11:52 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242712.5391] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Jan 30 13:11:52 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242712.5435] policy: auto-activating connection 'Wired connection 1' (444bcea7-7d1b-3ef5-a276-33d81c34b9e0)
Jan 30 13:11:52 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242712.5472] device (eth0): Activation: starting connection 'Wired connection 1' (444bcea7-7d1b-3ef5-a276-33d81c34b9e0)
Jan 30 13:11:52 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242712.5480] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 30 13:11:52 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242712.5509] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 30 13:11:52 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242712.5555] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jan 30 13:11:52 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242712.5588] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jan 30 13:11:52 colibri-imx8x-07329158 avahi-daemon[796]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::9f56:9b10:85fb:52d3.
Jan 30 13:11:52 colibri-imx8x-07329158 avahi-daemon[796]: New relevant interface eth0.IPv6 for mDNS.
Jan 30 13:11:52 colibri-imx8x-07329158 avahi-daemon[796]: Registering new address record for fe80::9f56:9b10:85fb:52d3 on eth0.*.
Jan 30 13:11:52 colibri-imx8x-07329158 kernel: IPv4: martian source 192.168.178.94 from 192.168.178.29, on dev eth0
Jan 30 13:11:52 colibri-imx8x-07329158 kernel: ll header: 00000000: ff ff ff ff ff ff 44 e5 17 a7 9a f4 08 06
Jan 30 13:11:53 colibri-imx8x-07329158 kernel: IPv4: martian source 192.168.178.94 from 192.168.178.29, on dev eth0
Jan 30 13:11:53 colibri-imx8x-07329158 kernel: ll header: 00000000: ff ff ff ff ff ff 44 e5 17 a7 9a f4 08 06
Jan 30 13:11:54 colibri-imx8x-07329158 systemd-networkd[724]: eth0: Gained IPv6LL
Jan 30 13:11:54 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242714.5503] dhcp6 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jan 30 13:11:54 colibri-imx8x-07329158 avahi-daemon[796]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::9f56:9b10:85fb:52d3.
Jan 30 13:11:54 colibri-imx8x-07329158 avahi-daemon[796]: Joining mDNS multicast group on interface eth0.IPv6 with address 2001:16b8:cbc8:8700:4d98:697:3dfd:6973.
Jan 30 13:11:54 colibri-imx8x-07329158 avahi-daemon[796]: Registering new address record for 2001:16b8:cbc8:8700:4d98:697:3dfd:6973 on eth0.*.
Jan 30 13:11:54 colibri-imx8x-07329158 avahi-daemon[796]: Withdrawing address record for fe80::9f56:9b10:85fb:52d3 on eth0.
Jan 30 13:11:54 colibri-imx8x-07329158 avahi-daemon[796]: Registering new address record for fd85:9c4d:89d5:0:522b:f0c8:bcc6:324e on eth0.*.
Jan 30 13:11:54 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242714.5579] dhcp6 (eth0): state changed new lease
Jan 30 13:11:54 colibri-imx8x-07329158 dbus-daemon[689]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.5' (uid=>
Jan 30 13:11:54 colibri-imx8x-07329158 kernel: IPv4: martian source 192.168.178.89 from 192.168.178.1, on dev eth0
Jan 30 13:11:54 colibri-imx8x-07329158 kernel: ll header: 00000000: 00 0e c6 a0 54 e0 48 5d 35 01 55 a5 08 00
Jan 30 13:11:54 colibri-imx8x-07329158 kernel: IPv4: martian source 192.168.178.89 from 192.168.178.1, on dev eth0
Jan 30 13:11:54 colibri-imx8x-07329158 kernel: ll header: 00000000: 00 0e c6 a0 54 e0 48 5d 35 01 55 a5 08 00
Jan 30 13:11:54 colibri-imx8x-07329158 systemd[1]: Starting Network Manager Script Dispatcher Service...
Jan 30 13:11:54 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242714.5978] dhcp4 (eth0): state changed new lease, address=192.168.178.89
Jan 30 13:11:54 colibri-imx8x-07329158 avahi-daemon[796]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.178.89.
Jan 30 13:11:54 colibri-imx8x-07329158 avahi-daemon[796]: New relevant interface eth0.IPv4 for mDNS.
Jan 30 13:11:54 colibri-imx8x-07329158 avahi-daemon[796]: Registering new address record for 192.168.178.89 on eth0.IPv4.
Jan 30 13:11:54 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242714.6241] policy: set 'Wired connection 1' (eth0) as default for IPv4 routing and DNS
Jan 30 13:11:54 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242714.6261] manager: NetworkManager state is now CONNECTING
Jan 30 13:11:54 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242714.6270] policy: set 'Wired connection 1' (eth0) as default for IPv6 routing and DNS
Jan 30 13:11:54 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242714.6443] device (eth0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jan 30 13:11:54 colibri-imx8x-07329158 kernel: IPv4: martian source 192.168.178.89 from 192.168.178.89, on dev mlan0
Jan 30 13:11:54 colibri-imx8x-07329158 kernel: ll header: 00000000: ff ff ff ff ff ff 00 0e c6 a0 54 e0 08 06

I wasn’t quick enough to get nmcli device status output while only the ethernet connection was working as I only re-read your post later (my bad) and the WLAN connection got reestablished after I plugged in the LAN cable, here’s how it looks with both back up:

DEVICE           TYPE      STATE         CONNECTION
eth0             ethernet  connected     Wired connection 1
mlan0            wifi      connected     Escapeverse.de
uap0             wifi      disconnected  --
ethernet0        ethernet  unavailable   --
br-9f6e87ccf015  bridge    unmanaged     --
br-fefdd16d2313  bridge    unmanaged     --
docker0          bridge    unmanaged     --
veth01dc154      ethernet  unmanaged     --
veth5b22356      ethernet  unmanaged     --
vethdb4636f      ethernet  unmanaged     --
sit0             iptunnel  unmanaged     --
lo               loopback  unmanaged     --

…and here are all the messages from NetworkManager since boot:

journalctl --unit NetworkManager -n 500 excerpt

Jan 30 13:00:30 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242030.8867] device (mlan0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jan 30 13:00:30 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242030.8880] device (mlan0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jan 30 13:00:30 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242030.8899] manager: NetworkManager state is now CONNECTED_LOCAL
Jan 30 13:00:30 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242030.8933] manager: NetworkManager state is now CONNECTED_SITE
Jan 30 13:00:30 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242030.8946] policy: set 'Escapeverse.de' (mlan0) as default for IPv4 routing and DNS
Jan 30 13:00:30 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242030.8983] device (mlan0): Activation: successful, device activated.
Jan 30 13:00:30 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242030.9017] manager: NetworkManager state is now CONNECTED_GLOBAL
Jan 30 13:00:32 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242032.8210] dhcp6 (mlan0): activation: beginning transaction (timeout in 45 seconds)
Jan 30 13:00:32 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242032.8246] policy: set 'Escapeverse.de' (mlan0) as default for IPv6 routing and DNS
Jan 30 13:00:33 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242033.0259] dhcp6 (mlan0): state changed new lease
Jan 30 13:00:40 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242040.8692] manager: (docker0): new Bridge device (/org/freedesktop/NetworkManager/Devices/6)
Jan 30 13:00:41 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242041.0294] manager: (br-9f6e87ccf015): new Bridge device (/org/freedesktop/NetworkManager/Devices/7)
Jan 30 13:00:41 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242041.1638] manager: (br-fefdd16d2313): new Bridge device (/org/freedesktop/NetworkManager/Devices/8)
Jan 30 13:00:44 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242044.5132] manager: (vethfcdebd7): new Veth device (/org/freedesktop/NetworkManager/Devices/9)
Jan 30 13:00:44 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242044.5663] manager: (veth01dc154): new Veth device (/org/freedesktop/NetworkManager/Devices/10)
Jan 30 13:00:44 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242044.6130] manager: (veth5d33e72): new Veth device (/org/freedesktop/NetworkManager/Devices/11)
Jan 30 13:00:44 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242044.6257] manager: (vethdb4636f): new Veth device (/org/freedesktop/NetworkManager/Devices/12)
Jan 30 13:00:46 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242046.9527] device (vethdb4636f): carrier: link connected
Jan 30 13:00:46 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242046.9542] device (br-fefdd16d2313): carrier: link connected
Jan 30 13:00:46 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242046.9549] device (veth01dc154): carrier: link connected
Jan 30 13:00:46 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242046.9563] device (br-9f6e87ccf015): carrier: link connected
Jan 30 13:02:01 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242121.6841] manager: (veth3b08c10): new Veth device (/org/freedesktop/NetworkManager/Devices/13)
Jan 30 13:02:01 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242121.7084] manager: (veth5b22356): new Veth device (/org/freedesktop/NetworkManager/Devices/14)
Jan 30 13:02:03 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242123.1522] device (veth5b22356): carrier: link connected
Jan 30 13:07:14 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242434.1148] device (uap0): set-hw-addr: set MAC address to 0E:10:47:42:EC:A5 (scanning)
Jan 30 13:07:14 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242434.1206] device (uap0): supplicant interface state: disconnected -> interface_disabled
Jan 30 13:07:14 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242434.2254] device (uap0): supplicant interface state: interface_disabled -> inactive
Jan 30 13:11:49 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242709.7364] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/15)
Jan 30 13:11:49 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242709.8099] device (eth0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jan 30 13:11:50 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242710.1871] settings: (eth0): created default wired connection 'Wired connection 1'
Jan 30 13:11:52 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242712.5347] device (eth0): carrier: link connected
Jan 30 13:11:52 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242712.5391] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Jan 30 13:11:52 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242712.5435] policy: auto-activating connection 'Wired connection 1' (444bcea7-7d1b-3ef5-a276-33d81c34b9e0)
Jan 30 13:11:52 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242712.5472] device (eth0): Activation: starting connection 'Wired connection 1' (444bcea7-7d1b-3ef5-a276-33d81c34b9e0)
Jan 30 13:11:52 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242712.5480] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 30 13:11:52 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242712.5509] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 30 13:11:52 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242712.5555] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jan 30 13:11:52 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242712.5588] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jan 30 13:11:54 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242714.5503] dhcp6 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jan 30 13:11:54 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242714.5579] dhcp6 (eth0): state changed new lease
Jan 30 13:11:54 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242714.5978] dhcp4 (eth0): state changed new lease, address=192.168.178.89
Jan 30 13:11:54 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242714.6241] policy: set 'Wired connection 1' (eth0) as default for IPv4 routing and DNS
Jan 30 13:11:54 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242714.6261] manager: NetworkManager state is now CONNECTING
Jan 30 13:11:54 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242714.6270] policy: set 'Wired connection 1' (eth0) as default for IPv6 routing and DNS
Jan 30 13:11:54 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242714.6443] device (eth0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jan 30 13:11:54 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242714.7492] device (eth0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jan 30 13:11:54 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242714.7508] device (eth0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jan 30 13:11:54 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242714.7529] manager: NetworkManager state is now CONNECTED_GLOBAL
Jan 30 13:11:54 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242714.7551] device (eth0): Activation: successful, device activated.
Jan 30 13:14:11 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242851.8705] device (uap0): set-hw-addr: set MAC address to A2:5A:17:E0:1C:B1 (scanning)
Jan 30 13:14:11 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242851.8724] device (uap0): supplicant interface state: inactive -> interface_disabled
Jan 30 13:14:11 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242851.9829] device (uap0): supplicant interface state: interface_disabled -> disconnected
Jan 30 13:14:11 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738242851.9896] device (uap0): supplicant interface state: disconnected -> inactive
Jan 30 13:21:11 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738243271.1284] device (uap0): set-hw-addr: set MAC address to 32:C2:F6:60:4F:9D (scanning)
Jan 30 13:21:11 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738243271.1315] device (uap0): supplicant interface state: inactive -> interface_disabled
Jan 30 13:21:11 colibri-imx8x-07329158 NetworkManager[720]: <info>  [1738243271.2483] device (uap0): supplicant interface state: interface_disabled -> inactive

Regarding sleep/suspend modes: not that I know, but how can I check?

uwdlg · January 31, 2025, 2:41pm

…meant to write “network interface mlan0” instead of …uap0. Can’t seem to edit my post.

uwdlg · February 3, 2025, 3:41pm

I think powersave is disabled for the Wifi connection, as /etc/NetworkManager/system-connections/Escapeverse.de.nmconnection has powersave=2, full file contents below.

Other than that I’m still stuck with the same intermittent connection drops. From the journalctl logs it looks to me like the second wifi interface changing its state seems to cause the first to lose its connection, output like this seems to always appear right before my ssh connection fails:

Feb 03 15:33:35 colibri-imx8x-07329158 systemd-networkd[757]: uap0: Link DOWN
Feb 03 15:33:35 colibri-imx8x-07329158 NetworkManager[753]: <info>  [1738596815.8114] device (uap0): set-hw-addr: set MAC address to 52:0E:A0:ED:03:10 (scanning)
Feb 03 15:33:35 colibri-imx8x-07329158 systemd-networkd[757]: uap0: Link UP
Feb 03 15:33:35 colibri-imx8x-07329158 NetworkManager[753]: <info>  [1738596815.8189] device (uap0): supplicant interface state: inactive -> disconnected
Feb 03 15:33:35 colibri-imx8x-07329158 NetworkManager[753]: <info>  [1738596815.8246] device (uap0): supplicant interface state: disconnected -> inactive

Can I prevent uap0 from doing that? I tried sudo ifconfig uap0 down, but that seems to have only temporarily removed uap0 (at least from the ifconfig output).

/etc/NetworkManager/system-connections/Escapeverse.de.nmconnection

[connection]
id=Escapeverse.de
uuid=cc915828-7da0-4938-83d5-7edc9e44a2a8
type=wifi
interface-name=mlan0
timestamp=1738342853

[wifi]
mode=infrastructure
powersave=2
ssid=Escapeverse.de

[wifi-security]
auth-alg=open
key-mgmt=wpa-psk
psk=

[ipv4]
method=auto

[ipv6]
addr-gen-mode=stable-privacy
method=auto

[proxy]

collin.tx · February 5, 2025, 2:33pm

Dear @uwdlg,

I have had a look at the information provided by you and I believe systemd-networkd should not actually be running by itself since we have a networkmanager “taking over”. Could you maybe try the following commands and check the behaviour?

systemctl stop systemd-networkd
systemctl disable systemd-networkd

In order to see the status of systemd-networkd you can use the following command:
systemctl status systemd-networkd

I am curious to see if this might be the culprit of the disconnections.
Should this not be the case I would recommend reinstalling a new Torizon image and looking into the wifi connection after to it manually. If the connection appears stable after this step, we know there might be an issue with the image.

Best regards,
Collin

uwdlg · February 10, 2025, 12:31pm

I have found a “fix”:
I could deactivate that second interface with nmcli dev set uap0 managed no and to make it stick, I created /etc/NetworkManager/NetworkManager.conf with

[device]
match-device=interface-name:uap0
managed=false

With this the disconnects don’t happen anymore.

collin.tx · February 12, 2025, 11:33am

Dear @uwdlg,

Thank you for showing your solution.

Best regards,
Collin