Why don't eth2-eth5 ports route traffic?

Question

Mikrotik

1. There is the simplest Microtik mikrotik hex lite, firmware 6.43.4. I reset all settings. Turn off all firewall rules.
2. Interfaces eth2- eth4 are combined into a bridge. eth1 and eth5 are free.
3. Assign eth1 address 192.168.1.1/24; bridge - 192.168.99.1/24, eth5-192.168.2.1/24
The traceroute utility, in microtik itself, will allow you to select the interface from which icmp requests are made.
We try to trace addresses 192.168.99.1, 192.168.2.1 from the eth1 interface - there are no problems, the first hop is 192.168.1.1 and then to the interface address.
If we try to trace addresses 192.168.1.1 or 192.168.2.1 from the bridge interface, we get Host unreachable from 192.168.99.1
Similarly, if we trace addresses 192.168.1.1 or 192.168.99.1 from the eth5 interface, we get Host unreachable from
192.168.2.1 from the corresponding settings for the port.
How can I not determine what kind of setting gives such a result, or is the hex lite piece of iron somehow limited?

Answer 1

What if you think about it?) I'm more inclined to the option that you quarreled with the trolls who rule the routing. Make amends and everything will work)