If you have two bridges on one chip it will only be able to hardware accelerate one of those two bridges (this was also the case before, where you could only have one master port per switch chip).I have one bridge on the gigabit chip and 2 bridges on the fast chip.
*) dhcpv6-server - recreate DHCPv6 server binding if it is no longer within prefix pool when rebinding/renewing;
Can you clarify what you meant by deactivated bridges - did you have a bridge created but it was disabled? Maybe this is why the conversion failed, if it wasn't expecting this.I changed the L2 MTU to 1500. I think because of the Airport Extreme.
Excellent! Glad that helped. It is not always unusual for there to be a delay when making major routing changes.Sorry for delayed edit! The problem is now solved. I don't know why now, but in some cases I have seen delayed reactions on some lower level Mikrotik routers (like RB750).
Then, the most likely problem is that your other routers are probably missing a route to the 192.168.134.0/24 subnet, and can't get the reply packet back to the PC as a result.It can ping ONLY IPs bound to that router, and nothing else.
Can that PC ping a backbone IP that is actually bound to that router? Or it cannot ping any backbone IPs, including backbone IPs bound to that router?What else should I provide?