#267 QoS tags not working on windows

[Andres]

We are using iperf to validate qos management over our hardware but we dont see proper qos tagging at the output of the client

iperf version: 2.1.9

BK

• server: iperf -s -u -e -B 192.168.1.96 -f m -i 5 -p 10001
• client: iperf -u -e -B 192.168.1.196 -c 192.168.1.96 -f m -i 5 -p 10001 -t 56600 -P 1 -b 32.444024999999996m -l 900 -S 0x40
  BE
• server: iperf -s -u -e -B 192.168.1.96 -f m -i 5 -p 10000
• client: iperf -u -e -B 192.168.1.196 -c 192.168.1.96 -f m -i 5 -p 10000 -t 56600 -P 1 -b 32.444024999999996m -l 900 -S 0x0
  both client and server are 2 nucs with windows 10

the wireshark capture is being done at the output of the client PC
expected a difference in DSCP tags for each port but both flows are tagged as CS0 at the output

also tested with client commands using "cs1", "cs7"... and some others recommended in the help

[Robert McMahon]

Windows doesn't allow apps to directly set QoS but I'll double check to see if this has changed.