/32 works with /31 on the remote side.

Why on Earth, would you need to use /32 on local and /31 on remote? This is a very poor implementation of RFC3021, if you could even call it an attempt.

Still currently seeing this issue on ROS 7.12, any plans for a fix?

input.limit-process-routes-ipv4 https://help.mikrotik.com/docs/display/ROS/BGP#BGP-TemplateMenu This is a poor implementation of a function that should be hard limiting prefixes received. On many prominent Internet Exchanges, they configure a hard limit of routes received from peers based on Peerin...

If the plan is to advertise only the default route downstream, you can stick with setting the default-originate to always. It doesn't re-advertise your colo provider's default route and gateway (unless you're using iBGP... in which case you should turn on next-hop-self for your downstream peers) bu...

You can't "convert" Ubuntu to a MikroTik CHR. The only way is to use the pre-built image files.

Hello all, We are receiving BGP routes from a number of IX peers over bilateral peering sessions, routes from the IX route servers, a full table from a transit provider and a default route from the colo provider. What we are looking to do, is advertise a default route to our downstream peers. If we ...

You should be able to accept any routes with an AS Path containing only your provider's AS.

Hello all, I've just attempted an upgrade from 7.6 to 7.11.2, and BGP broke. We were receiving full tables on two different circuits from the same upstream transit provider (for redundancy) however once we did the upgrade, we stopped sending our prefix to them. We rolled back and it started working ...