After some experimenting I found out that you can create rules to modify the default destination of the specific applications identified within app analysis. Lets go over two examples
Code:
From /tmp/bwdpi/bwdpi.app.db
4,132,0,Netflix
13,7,0,Speedtest.net
netflix
general category: 4dec = 04 hex
specific identification: 132dec = 0084 hex
speedtest
general category: 13dec = 0d hex
specific identification: 7dec = 0007 hex
so
Code:
realtc filter add dev br0 protocol all prio 2 u32 match mark 0x80040084 0xc03fffff flowid ${Default} # will stick netflix into defaults
realtc filter add dev br0 protocol all prio 2 u32 match mark 0x800d0007 0xc03fffff flowid ${Default} # will stick speedtest.net into defaults
I don't like too many rules, but if some app is causing havoc **cough speedtest.net cough**, you can stick it into defaults/filedownloads instead of web browsing.
The general form goes like this
8# 0d 0007 = (Download, Web Browsing, Speedtest)
where
8 = traffic direction [ download (8) or upload (4) ]
# = traffic priorty (highest,high,medium,default,lowest)
0d = traffic type (see post 3 or bwdpi.app.db)
0007 = specific application/traffic within category (see bwdpi.app.db )
Note: numbers in TC are in hex. Numbers in "bwdpi.app.db" are in dec. Conversion is necessary.