[Wi-Fi Setup] Cannot connect to 802.1X Enterprise Network (TTLS/MSCHAPv2) - Immediate disconnect post-association

[ilham-9-9]

Robot Model

Turtlebot4 Standard

ROS distro

Jazzy

Networking Configuration

Simple Discovery

OS

Ubuntu 24.04

Built from source or installed?

Installed

Package version

ros-jazzy-turtlebot4-setup version 2.0.2-1noble

Type of issue

Networking

Expected behaviour

I connect my TurtleBot 4's Raspberry Pi to my university's enterprise Wi-Fi network (WPA-Enterprise, 802.1X, TTLS, MSCHAPv2).

Actual behaviour

Since the turtlebot4-setup tool only seems to support standard WPA-Personal (SSID/Password) networks, I had to configure the connection manually using nmcli. However, despite configuring all the required parameters (identity, password, disabling MAC randomization, etc.), the connection fails.

The physical radio is working but it is instantly disconnected by the AP a fraction of a second later. Because it disconnects, NetworkManager assumes the password is wrong or missing, and since it's a headless setup, it throws a no-secrets error.

Error messages

When running `sudo nmcli connection up something`, here is the output from `journalctl -xe NM_CONNECTION=... + NM_DEVICE=wlan0`:


Mar 20 09:44:02 turtlebot4 NetworkManager[3904]: <info>  [1773999842.5916] device (wlan0): supplicant interface state: scanning -> associating
Mar 20 09:44:02 turtlebot4 NetworkManager[3904]: <info>  [1773999842.7788] device (wlan0): supplicant interface state: associating -> associated
Mar 20 09:44:02 turtlebot4 NetworkManager[3904]: <info>  [1773999842.8422] device (wlan0): supplicant interface state: associated -> disconnected
Mar 20 09:44:02 turtlebot4 NetworkManager[3904]: <info>  [1773999842.9389] device (wlan0): supplicant interface state: disconnected -> scanning
Mar 20 09:44:16 turtlebot4 NetworkManager[3904]: <warn>  [1773999856.7253] device (wlan0): Activation: (wifi) association took too long
Mar 20 09:44:16 turtlebot4 NetworkManager[3904]: <info>  [1773999856.7255] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Mar 20 09:44:16 turtlebot4 NetworkManager[3904]: <warn>  [1773999856.7264] device (wlan0): Activation: (wifi) asking for new secrets
Mar 20 09:44:16 turtlebot4 NetworkManager[3904]: <warn>  [1773999856.7375] device (wlan0): no secrets: No agents were available for this request.
Mar 20 09:44:16 turtlebot4 NetworkManager[3904]: <info>  [1773999856.7377] device (wlan0): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed')
Mar 20 09:44:16 turtlebot4 NetworkManager[3904]: <warn>  [1773999856.7391] device (wlan0): Activation: failed for connection 'something'
Mar 20 09:44:16 turtlebot4 NetworkManager[3904]: <info>  [1773999856.7498] device (wlan0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')

To Reproduce

1. Cleaned up /etc/netplan/ to ensure no conflicting configurations (only kept the default ethernet/usb configs).
2. Manually set the system date/time
3. Configured the connection via nmcli with the following parameters:
   • 802-1x.eap ttls
   • 802-1x.phase2-auth mschapv2 (also tried pap)
   • 802-1x.identity and 802-1x.anonymous-identity set to my specific university domain requirements.
   • 802-1x.password-flags 0 (to save the password system-wide)
   • 802-11-wireless.mac-address-randomization 1 (Disabled randomization)
   • 802-1x.system-ca-certs no (Ignored CA certs to isolate the issue, also tried with yes and pointing to /etc/ssl/certs/ca-certificates.crt).

The full configuration command used:
sudo nmcli connection add type wifi ifname wlan0 con-name something ssid something wifi-sec.key-mgmt wpa-eap 802-1x.eap ttls 802-1x.phase2-auth mschapv2 802-1x.identity "username@domain.de" 802-1x.anonymous-identity "anonymous@domain.de" 802-1x.password "<PASSWORD>" 802-1x.system-ca-certs no 802-1x.password-flags 0 802-11-wireless.mac-address-randomization 1

Other notes

No response