Bonding balance-alb

I got someting like this

R1
ether2 ↔ ether2
ether5 ↔ ether5

[admin@MikroTik] > interface bonding print
Flags: X - disabled, R - running
0 R name=“bonding1” mtu=1500 mac-address=B8:69:F4:CF:51:F0 arp=enabled arp-timeout=auto
slaves=ether2,ether5 mode=balance-alb primary=ether2 link-monitoring=mii
arp-interval=100ms arp-ip-targets=“” mii-interval=100ms down-delay=0ms up-delay=0ms
lacp-rate=30secs transmit-hash-policy=layer-2 min-links=0

Interfaces ether 2 are set a 100Mbps full duplex, and ether 5 are set to 10Mbps full duplex.
So, with bonding balance-alb I expecting to pass 110Mbps in both directions.
But when I’m trying to test BW with Bandwidth tester or Traffic Generator between R1 and R2, I get traffic only in ether 2 (100Mbps).
Only when ether 2 goes down, traffic passes to ether 5, and at 10Mbps…
So, what I’m doing wrong on this?

Thanks in advance.

When bonding layer has to decide which member to use for transmitting next packet, it uses some kind of algorithm to decide. In addition it is often (if not always) desirable that packets belonging to same L4 connection (TCP most notably, UDP as well) pass same member link due to timing reasons (to avoid out-of-order delivery).
Setting transmit-hash-policy=layer-2 means that it will consider only L2 addresses (that’s MAC addresses) of sender and receiver when deciding which line to use. Hence if you use some kind of traffic generator between a pair of test machines, traffic will always pass same physical line because all packets will have same pair of source and destination MAC addresses. Mind that packets may take different line in the reverse direction (because the other bond partner might implement hashing algorithm slightly differently).
If you want to spread traffic between same pair of hosts over multiple bond members, you have to use some other transmit hash policy. Read about those in bonding manual. And even if you use other policies, it will only work if there are multiple concurrent connections active at the same time.

Thanks mkx…
I was reading your suggestion and it seems to be a test issue, not an config issue.
thanks a lot!