Eng:
Iperf v2 often seems to send packet headers of various formats that break the v2 format

What is expected:
[sequence (4 bytes)] [timestamp (8 bytes)] [flags (4 bytes)] [threads (4 bytes)] [port (4 bytes)] [winband (4 bytes)] [amount (4 bytes)]

What is sometimes received:
[40010078] [00000001] [00001389] [00000000] [00000000]

or

[00000001] [630d33a30001b552] [00000000] [0c010098] [00000001] [00001389] [00000000] [00000000]

or

[00000000] [630fcebc000cb12d] [00000000] [08000000] [303132...]

1. Does anyone know what accounts for these inconsistencies in the packet header?

2. Does anyone know what the first field is when it is not the sequence? (eg. 40010078)

3. Does anyone know what the 4th field is when it is not the thread count? (eg. 0c010098 / 08000000 )

Thanks.

---

Fr:

Iperf v2 semble souvent envoyer des en-têtes de paquets de différents formats qui cassent le format v2

Ce qui est attendu :
[séquence (4 octets)] [horodatage (8 octets)] [flags (4 octets)] [threads (4 octets)] [port (4 octets)] [winband (4 octets)] [quantité (4 octets)]

Ce qui est parfois reçu :
[40010078] [00000001] [00001389] [00000000] [00000000]

ou

[00000001] [630d33a30001b552] [00000000] [0c010098] [00000001] [00001389] [00000000] [00000000]

ou

[00000000] [630fcebc000cb12d] [00000000] [08000000] [303132...]

1. Est-ce que quelqu'un sait ce qui explique ces incohérences dans l'en-tête du paquet ?

2. Est-ce que quelqu'un sait quel est le premier champ quand ce n'est pas la séquence ? (ex. 40010078)

3. Est-ce que quelqu'un sait ce qu'est le 4ème champ quand ce n'est pas le nombre de threads ? (par exemple 0c010098 / 08000000 )

Merci