Comment 1 for bug 1933402

Hi,
since this is some character/encoding mess it would be helpful to get hat value those have exactly.
I mean there might be a byte swap or odd encoding somewhere, but these values might help to track down what it is.

here an example from a non-affected system (for comparison):

$ ip a | grep altname | hexdump --canonical
00000000 20 20 20 20 61 6c 74 6e 61 6d 65 20 65 6e 70 32 | altname enp2|
00000010 73 30 66 30 0a 20 20 20 20 61 6c 74 6e 61 6d 65 |s0f0. altname|
00000020 20 65 6e 70 32 73 30 66 31 0a 20 20 20 20 61 6c | enp2s0f1. al|
00000030 74 6e 61 6d 65 20 65 6e 70 32 73 30 66 32 0a 20 |tname enp2s0f2. |
00000040 20 20 20 61 6c 74 6e 61 6d 65 20 65 6e 70 32 73 | altname enp2s|
00000050 30 66 33 0a 20 20 20 20 61 6c 74 6e 61 6d 65 20 |0f3. altname |
00000060 65 6e 70 34 73 30 66 30 0a 20 20 20 20 61 6c 74 |enp4s0f0. alt|
00000070 6e 61 6d 65 20 65 6e 70 38 73 30 6e 70 30 0a 20 |name enp8s0np0. |
00000080 20 20 20 61 6c 74 6e 61 6d 65 20 65 6e 70 34 73 | altname enp4s|
00000090 30 66 31 0a |0f1.|
00000094