<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Feb 16, 2017, at 12:03 AM, Dave Täht <<a href="mailto:dave@taht.net" class="">dave@taht.net</a>> wrote:</div><div class=""><div class=""><br class="">What I'd done in cerowrt was disable the internal mac80211 QoS<br class="">classifier entirely. (-1 line of code). Another way to do it is to apply<br class="">an iptables rule to wash away all diffserv markings, but I don't care<br class="">for that answer.<br class=""><br class="">try as I might I cannot remember if this was even possible in hostapd or<br class="">in the mac layer any other way. I'll look this week.<br class=""></div></div></blockquote></div><br class=""><div class="">Aha, so since I’m only doing the rrul_be test for now, this won’t matter anyway right? I suppose somewhere diffserv markings are mapped to WMM access categories.</div><div class=""><br class=""></div><div class="">It looks like AirOS has its own mappings: <a href="https://help.ubnt.com/hc/en-us/articles/205231750-airMAX-How-is-QoS-and-prioritization-handled-by-airMAX-" class="">https://help.ubnt.com/hc/en-us/articles/205231750-airMAX-How-is-QoS-and-prioritization-handled-by-airMAX-</a></div><div class=""><br class=""></div><div class="">and there doesn’t look like a practical way to disable it in their UI. So still, for now, disabling WMM is something I can only do in testing.</div><div class=""><br class=""></div><div class="">It looks like FreeNet doesn’t touch diffserv markings in their QoS config, which means they leave it up to AirOS’s mappings above. This always makes me wonder what’s to keep someone from just marking all their traffic 0x7 and stomping over everyone else.</div><div class=""><br class=""></div><div class="">Thanks,</div><div class="">Pete</div><div class=""><br class=""></div></body></html>