TOS/DSCP values for different traffic classes/queues about mgen

[weston-nrl]

My suggestion would be to capture the packets with tcpdump ("-v" option), wireshark, or similar pcap methods and verify that the TOS/DSCP field is getting set correctly (those values work for me, corresponding to 0x20, 0x40, 0x60). Once they're set correctly, what happens to them is more a function of your system queueing discipline and EMANE in this case. It looks like WMM needs to be enabled in EMANE as well if it's not already (see here).

I do not know for sure what DSCP values correspond to the different WMM traffic classes. Various sources online lead me to believe the DSCP values corresponding to the 4 classes may be 0, 8, 32, 48 -- if that's correct, it might make sense that one of the values you tried corresponds to one of those, while the others all went into the default class.

[vivianchiong]

Yes, I saw that my TOS values are indeed being set by using tcpdump and wmm is indeed enabled. Hopefully there isn't some other configuration or detail in the algorithm that I'm missing.

When I viewed the EMANE logs, I couldn't confidently say that my packets are even being processed by other nodes. After looking at the EMANE IEEE 802.11abg code, you are correct that the TOS values map to DSCP values with min values of 0, 8, 32, 48 so I adjusted my TOS values a bit so that the mgen flows would disperse into the different queues, but sadly no luck.

I opened an issue for this in the EMANE repo. If there is any other insight you can provide I would really appreciate it! Otherwise feel free to close this issue and I'll keep debugging on that other issue.

Thank you so much for your help thus far and have a great weekend!