Are ether2 and ether5 bridged? do they have different subnets? what is the lan set up?
I set a little test up but I'm on a bridge so I used src address instead of interface.
you could try having your wan as the parent target and eth2 and eth5 as your child targets. You will need to follow a couple rules.
1)The parent queue needs to have a max-limit set(setting it to high is not desirable try and be close to what the connection can actually handle).
2)The parent queue should not have a limit-at set and the priority does not mater.
3)Both child queues need to have a limit-at set so that when added together they add to the max-limit of the parent.
4) priority will only help distribute parent bandwidth so it only works in the child(leaf) queues
I don't have a test router on me right this sec to test interface priority but since I'm not to familiar with simple queue priority(mangle->queue-tree still seems simpler to me) I set up a test on my lan.
I'm running 6.1 currently and Allot has changed in simple queue in the new release so I hope this will still work if you haven't upgraded yet. I also suggest changing your default-small queue in queue types to sfq as it will limit on a per user basis cleaner than fifo.
lets say you have a bridge called bridge-lan that you have a /24 allocated. You want to prioritize and give more bandwidth to the first half of the subnet then the other.
add max-limit=0/9M name=parent-download target=bridge-lan
add limit-at=0/6M max-limit=0/9M name=priority-down parent=parent-download priority=7/7 target=192.168.1.0/25 total-priority=7
add limit-at=0/3M max-limit=0/9M name=regular-down parent=parent-download target=192.168.1.128/25
add max-limit=0/3M name=parent-upload target=1-wan
notice that the upload needs to have the wan as the parent instead of the lan and that the upload can't prioritize the two groups.
I'm still kind of confused why the parent queue can't be set to global. I think that would allow us to capture up and down traffic. As is, in the example above the queues can only limit traffic that is going out of their target interface.
as of right now there are not many examples on simple queues in version 6. Most of them have to do with using a /32 src address in a pcq situation and work just fine for the upload and download.
This example works great for the download prioritization but upload is just limited on a all user basis(bandage work around for now i hope).
I hope this helps. I can get a test router and try in 5.25 with your interface situation if this does not help you come to a resolution.