Hi, till now I used ros v2.51, but I installed ros v3. The same settings, also in ros 3 I set in bridge settings use ip firewall and use ip firewall for vlan. The problem is that in simple queues it shows me tx speed but in real it is rx from internet, and also there is problem with queue tree. I tryed to change parent in queue tree(inteface, bridge, global-in, global-out), nothing helped.
Ether1 is connection to internet.
Bridge1 is bridge with: wlan1, ether2, ether3.
Also queue tree doesnt work well.
213.151.203.22
name:demo
password:demo
Can be used in ros 3 SQ and QT in one device, or is better to do qt in one device and sq in next one?
connection is bidirectional, it’s upload + download. so for ‘IN’ you should mark packets not just by conection-mark, but also in-interface = your_uplink (ether1?)
or just set parent for ‘IN’ to ‘bridge’
I dont understand this idea: connection is bidirectional, it’s upload + download. so for ‘IN’ you should mark packets not just by conection-mark, but also in-interface = your_uplink (ether1?), can you be more specifically, you mean connection mark in mangle, I use pre and post routing, with interfaces.
I tryed bridge as parent for IN, but SQs dont work right. When I set parent for IN(traffic from internet to my network): bridge and for OUT(traffic from my network to internet, parent ether1 - internet), SQ shows still tx despite they should show rx. The only thing I could propably do is to use 2 routers, one for QT and another for SQ. Or is any solution?
simple rule: don’t use SQ and QT together unless you understand, how exactly it’s work simultaneously
Will it be better to do QT in one router and SQ in second?
How it works?
forward → SQ → global-in, global-out → interfaces ?
global-in is before forward 
and SQ is somewhere in global-in, global-out and global-total. AFAIR, SQ is on top of it, so it have priority over QT with the same parent
I was struggling with the same thing and got it all reversed initially. I got some help from the board and drew my attention to the fact the global-in handles both upload and download. so I used the interface as parent instead and got it all wrong again But to make a long short. The bottom line is:
If you use ether1 (your internet interface) as parent, the child queues will be shaping your UPLOAD - not the the download. The reason is, as far as I can tell, that the interface queue is located just in front of the output interface i.e. the part of your queue tree with Ether1 as parent will control the packet flow leaving through ether1.
Anyway, that is my understanding. Please correct me if above is not correct.
rgs Pilgrim
PS. recommend to follow the advice to not have simple - and queue tree in the same setup.
rgs Pilgrim
just read Wiki about Packet Flow and Queues… to limit packets received by interface you should use global-in. parent=interface is not the same as parent=global-out (SRC-NAT is one of differences)