Robot fails to connect to AP

[msminirobot]

We tried to connect the Create3 running on ROS 2 Humble to our local WiFi but it does not connect. The problem has to be on the side of the robot since we already successfully connected 8 other Create3 robots / TurtleBot4 with the WiFi. However, for two robots we get the following error messages:

Dec 4 20:27:46 iRobot-6C4BFF1904584B9C962595A6408CFB2A user.notice network_manager: sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper Dec 4 20:27:46 iRobot-6C4BFF1904584B9C962595A6408CFB2A daemon.err network[1467]: [ERROR] (src/wifi_control.c:209 errno:Address not available) sudo network_device_interfaces_control.sh --interface=softap --action=del returned status 1 Dec 4 20:27:47 iRobot-6C4BFF1904584B9C962595A6408CFB2A daemon.notice network[1467]: [INFO] (src/wifi_control.c:1891) wlan monitor event - CTRL-EVENT-SCAN-STARTED Dec 4 20:27:48 iRobot-6C4BFF1904584B9C962595A6408CFB2A user.notice ntpd: ntpd: bad address '0.irobot.pool.ntp.org' Dec 4 20:27:48 iRobot-6C4BFF1904584B9C962595A6408CFB2A user.notice create-platform: [INFO] [1701721668.926824630] [create-platform]: Activating kinematics_engine node Dec 4 20:27:48 iRobot-6C4BFF1904584B9C962595A6408CFB2A user.notice create-platform: [INFO] [1701721668.928342909] [turtle10._internal.kinematics_engine]: Lifecycle callback: on_activate Dec 4 20:27:49 iRobot-6C4BFF1904584B9C962595A6408CFB2A user.notice create-platform: [INFO] [1701721669.929685910] [create-platform]: Started kinematics_engine node Dec 4 20:27:49 iRobot-6C4BFF1904584B9C962595A6408CFB2A user.notice create-platform: [INFO] [1701721669.929953740] [create-platform]: Configuring composite_hazard node Dec 4 20:27:49 iRobot-6C4BFF1904584B9C962595A6408CFB2A user.notice create-platform: [INFO] [1701721669.930523357] [turtle10._internal.composite_hazard]: Lifecycle callback: on_configure Dec 4 20:27:50 iRobot-6C4BFF1904584B9C962595A6408CFB2A daemon.notice network[1467]: [INFO] (src/wifi_control.c:1891) wlan monitor event - CTRL-EVENT-SCAN-RESULTS Dec 4 20:27:50 iRobot-6C4BFF1904584B9C962595A6408CFB2A daemon.notice network[1467]: [INFO] (src/wifi_control.c:1891) wlan monitor event - WPS-AP-AVAILABLE Dec 4 20:27:50 iRobot-6C4BFF1904584B9C962595A6408CFB2A daemon.notice network[1467]: [INFO] (src/wifi_control.c:1891) wlan monitor event - CTRL-EVENT-SSID-REENABLED id=0 ssid="***********" Dec 4 20:27:50 iRobot-6C4BFF1904584B9C962595A6408CFB2A user.notice create-platform: [DBG] OSMonitor::OSMonitor: [ CREATED OS MONITOR ] Dec 4 20:27:50 iRobot-6C4BFF1904584B9C962595A6408CFB2A user.notice create-platform: [DBG] [TSSM] Waiting for 'internal_nodes' task to resume Dec 4 20:27:50 iRobot-6C4BFF1904584B9C962595A6408CFB2A user.notice create-platform: [DBG] [TSSM] 'internal_nodes' task resuming Dec 4 20:27:50 iRobot-6C4BFF1904584B9C962595A6408CFB2A user.notice create-platform: [DBG] [TSSM] 'internal_nodes' task resumed Dec 4 20:27:50 iRobot-6C4BFF1904584B9C962595A6408CFB2A user.notice create-platform: [DBG] [TSSM] Waiting for 'nodes_0' task to resume Dec 4 20:27:50 iRobot-6C4BFF1904584B9C962595A6408CFB2A user.notice create-platform: [DBG] [TSSM] 'nodes_0' task resuming Dec 4 20:27:50 iRobot-6C4BFF1904584B9C962595A6408CFB2A user.notice create-platform: [DBG] [TSSM] 'nodes_0' task resumed Dec 4 20:27:50 iRobot-6C4BFF1904584B9C962595A6408CFB2A user.notice create-platform: [DBG] [TSSM] Waiting for 'nodes_1' task to resume Dec 4 20:27:50 iRobot-6C4BFF1904584B9C962595A6408CFB2A user.notice create-platform: [DBG] [TSSM] 'nodes_1' task resuming Dec 4 20:27:50 iRobot-6C4BFF1904584B9C962595A6408CFB2A user.notice create-platform: [DBG] [TSSM] 'nodes_1' task resumed Dec 4 20:27:50 iRobot-6C4BFF1904584B9C962595A6408CFB2A user.notice create-platform: [WAR] Packet handler running too long exec_time: 30 id: 25 Dec 4 20:27:50 iRobot-6C4BFF1904584B9C962595A6408CFB2A user.notice create-platform: [WAR] Packet handler running too long exec_time: 206 id: 25 Dec 4 20:27:50 iRobot-6C4BFF1904584B9C962595A6408CFB2A user.notice create-platform: [WAR] Packet handler running too long exec_time: 135 id: 18 Dec 4 20:27:50 iRobot-6C4BFF1904584B9C962595A6408CFB2A user.notice create-platform: [WAR] Packet handler running too long exec_time: 134 id: 25 Dec 4 20:27:50 iRobot-6C4BFF1904584B9C962595A6408CFB2A user.notice create-platform: [WAR] Packet handler running too long exec_time: 251 id: 65 Dec 4 20:27:50 iRobot-6C4BFF1904584B9C962595A6408CFB2A user.notice create-platform: [WAR] Packet handler running too long exec_time: 264 id: 25 Dec 4 20:27:50 iRobot-6C4BFF1904584B9C962595A6408CFB2A user.notice create-platform: [WAR] Packet handler running too long exec_time: 46 id: 25 Dec 4 20:27:50 iRobot-6C4BFF1904584B9C962595A6408CFB2A user.notice create-platform: [DBG] [SE]: !wheels_stopped - odom:-14,0 Dec 4 20:27:50 iRobot-6C4BFF1904584B9C962595A6408CFB2A user.notice create-platform: [WAR] Packet handler running too long exec_time: 44 id: 25 Dec 4 20:27:50 iRobot-6C4BFF1904584B9C962595A6408CFB2A daemon.notice network[1467]: [INFO] (src/wifi_control.c:1891) wlan monitor event - Trying to associate with **:**:**:**:**:** (SSID='***********' freq=2432 MHz) Dec 4 20:27:51 iRobot-6C4BFF1904584B9C962595A6408CFB2A daemon.err network[1467]: [ERROR] (src/wifi_control.c:1857) connection to AP rejected Dec 4 20:27:51 iRobot-6C4BFF1904584B9C962595A6408CFB2A daemon.notice network[1467]: [INFO] (src/wifi_control.c:1891) wlan monitor event - CTRL-EVENT-ASSOC-REJECT bssid=**:**:**:**:**:** status_code=1 Dec 4 20:27:51 iRobot-6C4BFF1904584B9C962595A6408CFB2A daemon.notice network[1467]: [INFO] (src/wifi_control.c:1891) wlan monitor event - CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="***********" auth_failures=15 duration=268 reas

[shamlian]

The snippet you posted above shows "connection to AP rejected;" to confirm, are you in control of your infrastructure, or are you on a network administered by someone else? Can you tell for what reason the AP is refusing connection? Are you 100% sure you've typed your network's SSID and password correctly? Giving us a full log can help to determine what happens before this event, but the piece you've posted makes it look like either user error (incorrect credentials) or something with the AP causing the connection to be rejected.