nmcli fails to configure static addresses with leading zero

[crschardt]

When a team sets the static IP, they may include a leading zero in the third octet of the IP address. For example team 3206 might enter the IP address as 10.32.06.11. Apparently nmcli doesn't like the leading 0 in 06 and fails to update the configuration correctly. The result is that the configuration call will fail and the coprocessor isn't using the IP address the team thinks it assigned. If entered without the leading zeros, e.g., 10.32.6.11 instead, it works.

Here's an example of the failure from the logs:

Jan 30 05:04:41 photonvision java[665]: [2025-01-30 05:04:41] [General - ShellExec] [DEBUG] Executing "nmcli connection modify static-end1 autoconnect yes ipv4.method manual ipv6.method disabled ipv4.addresses 10.32.06.11/8 ipv4.gateway 10.32.06.1 "
Jan 30 05:04:41 photonvision java[665]: [2025-01-30 05:04:41] [General - ShellExec] [DEBUG] Got exit code 2

Exit code 2 is Invalid user input, wrong nmcli invocation. according to the nmcli documentation.

Here's the logs for success:

Jan 30 05:11:12 photonvision java[665]: [2025-01-30 05:11:12] [General - ShellExec] [DEBUG] Executing "nmcli connection modify static-end1 autoconnect yes ipv4.method manual ipv6.method disabled ipv4.addresses 10.32.6.11/8 ipv4.gateway 10.32.6.1 "
Jan 30 05:11:13 photonvision java[665]: [2025-01-30 05:11:13] [General - ShellExec] [DEBUG] Got exit code 0

[mcm001]

Looks like it’s not to bad to do with the InetAddress class. Also go to bed