If its an android media box, you can simply create a rule so that all traffic on that box is "Video Streaming".
With that you wouldn't have to micro manage and look for other identification deficiencies.
You can use these templates ( keep in mind that these templates have always been included inside the script itself )
Code:
Download
# ${tc} filter add dev br0 protocol all prio $1 u32 match ip dst 192.168.1.100/32 flowid ${VOIP} #Template Rule 2 (All incoming traffic w/ LAN destination ip 192.168.1.100 goes to "VOIP" Traffic Container)
Upload
# iptables -D POSTROUTING -t mangle -o eth0 -s 192.168.1.100/32 -j MARK --set-mark ${VOIP_mark} &> /dev/null #Template Rule 2 WORKING ALTERNATIVE (Line1/2)
# iptables -A POSTROUTING -t mangle -o eth0 -s 192.168.1.100/32 -j MARK --set-mark ${VOIP_mark} #Template Rule 2 WORKING ALTERNATIVE (Line2/2)
Everyone should feel free open the script with Notepad++ and take a look inside the script there as there is additional documentation not present in the first posts of this thread that can be beneficial depending on user need).
As for mis-categorization, it's simply deficiency in the trend micro rules responsible for deep packet analysis. This is the same reason I have custom rules to identify my VoIP traffic.
What I am really interested in how that traffic is getting into "Net Control". Can you turn on "App Analysis" and tell me the app name that the traffic is being identified as?
---
Also new update for gaming rules is coming. Currently the optional gaming rules direct 80/443 traffic into downloads.
Users have reported that actual download traffic is drowning out port 80/443 gaming traffic.
Going forward, the default configuration will be to place 80/443 gaming traffic "Defaults" category. (This is the non WebUI adjustable category that is locked in the bottom place.)
This will allow gaming port 80/443 traffic to have it's own guaranteed traffic allotment making it so file downloads, torrent, etc will not drown it out anymore.
(This is necessary since log-in + matchmaking also operates on these ports in addition to the bulky game updates, This traffic was being heavily drown out by downloads leading to a poor experience logging in/matchmaking )
I will also move the priority of "Defaults" up one position. This means that if you last traffic category in WebUI is "Downloads", then the actual QOS traffic priority will be "Defaults" and then "Downloads".
I am a little busy right now, but the update will come soon.