I believe these two lines are incorrect.
/ip firewall mangle
add action=mark-connection chain=prerouting dst-address-type=local in-interface=“Bridge LAN” new-connection-mark=mangle_BGC per-connection-classifier=both-addresses-and-ports:1/0
add action=mark-connection chain=prerouting dst-address-type=local in-interface=“Bridge LAN” new-connection-mark=mangle_VOO per-connection-classifier=both-addresses-and-ports:2/0Destination address of the router should be EXcluded, and probably also the directly connected subnets of BGC and VOO. Incoming connections already marked should probably also not be marked again.
/ip firewall mangle
add action=mark-connection chain=prerouting dst-address-type=!local connection-mark=no-mark in-interface=“Bridge LAN” new-connection-mark=mangle_BGC per-connection-classifier=both-addresses-and-ports:1/0
add action=mark-connection chain=prerouting dst-address-type=!local connection-mark=no-mark in-interface=“Bridge LAN” new-connection-mark=mangle_VOO per-connection-classifier=both-addresses-and-ports:2/0I think the distance of the default routes should be higher than the marked ones.
/ip route
add check-gateway=ping distance=3 gateway=“ether 1 - Belgacom”
add check-gateway=ping distance=4 gateway=“ether 2 - Voo”
As j7n pointed out the gateways of the mangled traffic should be lower than the default gateway (from an engineering standpoint) but don’t necessarily have to be (due to routing marks and independent gateways for those marks) since only unmarked traffic will exit the default gateway anyway and at that point distance becomes irrelevant only until you have more than one gateway per routing mark.
I would also exclude ports from PCC, as MovingNetworksForward suggested, to keep protocols and web sites requiring multiple connections always see the same address for each client. Otherwise some FTP servers will not work, and some webpages require repeated logins, for example.
If you only use the src-address in PCC, a particular local computer will always get the same routing mark and use the same WAN port. This may or may not be what you want. both-addresses:2/1 and both-addresses:2/0 work fine too.
The distances of the routes for marked packets should be smaller, not greater.
If you have any type of server on your network, I think the two rules in Input should be moved to Prerouting (will handle input to the router too). But first deal with outgoing connections.