What were you trying to do that didn't work?

When making a networking change using cockpit, the entered IPv4 address is backwards; e.g. entering 192.168.1.10 on the cockpit display is saved in the network config file as 10.1.168.192. Same issue occurs for saving gateway IP address. Using nm-tui does not have this problem. The linux hardware architecture is s390x, so I'm suspicious that using a big-endian system may be contributing to this behaviour.

What is the impact of this issue to you?

Updating the IP addresses via Cockpit GUI breaks the network connection (due to the address being written backwards) and must be corrected manually or via nm-tui. This impacts systems administrator productivity and possibly end-users.

Please provide the package NVR for which the bug is seen:

cockpit-344-1.el9.s390x  

How reproducible is this bug?:

100% on s390x architecture.

We were unable to reproduce on x86_64.

Steps to reproduce

1. Change IP address of an interface in the Cockpit GUI and save
2. Verify how the address is reflected in the configuration file written by cockpit

Expected results

IP address string matches what was input

Actual results

IP address octets are reversed