*) API - fixed possible crash when running concurrent commands;
*) console - fixed logging commands: ‘warning’, ‘error’ and ‘debug’ were
all using ‘info’ topic;
*) bgp - added routing-table configuration option for instances;
*) bgp - added ‘as-override’ and ‘passive’ configuration options for peers;
*) bgp - added support for Site of Origin extended communities;
*) bgp - fixed some network issues;
*) ospf - fixed problem: when last neighbor on multi-access interface disappeared,
incorrect RouterLSA was generated on designated router;
*) metarouter - allow to specify metarouter’s memory size when importing image;
*) firewall - added ‘routing-table’ matcher;
*) fixed problem - e1000 driver did not work in virtual machines;
ok, just installed 4.3 on a 433uah and it basically turned two of the interface into “ghost interfaces” (everything looks normal, no traffic going over them)
downgraded back to 4.2 and all good again
actually, it was my feature request this function should check, whether ip address have a route in selected routing table… but seems like it can only check dst-address… what about src?
I also requested ‘routing-table’ matcher when talking with Sergejs at the USA mum. Thanks to Mikrotik team for adding this feature, it will make my life a lot easier.
gbh, it is very important to get more information about your configuration, we need support output file from the router in 4.3, when the problem is present. Please send file to support@mikrotik.com
We have upgraded few RB433UAH, it seems they are working fine.
I have a good idea of how this new “routing-table” works, and how to implement it, but it would be great if Mikrotik support could put some notes in the wiki describing this new feature, I see there is a note on the BGP wiki page but but it would be good to have a description on the filter page as well as info on how the “routing-table” works inside RouterOS logically…