The public devices are assigned Public Devices directly. I am trying to separate them from my private lan completley. The only way i have been able to make it work was to but them into their own bridge. However it did not work well at all. The servers could not communicate correctly with each other at all. I assume it has somthing to do with broadcast perhaps. I am not sure.
When i use a switch in fron of the router things work properly. These servers are for Voip. It is important that there is no NAT involved.
From what you wrote in this post I understand there is no interconnection subnet, so without VRRP/HSRP, one address out of the /28 is used as the router at datacenter side, so you are left with only 13 addresses you can actually use, since the network address, the broadcast address and a gateway address are occupied. And depending on the equipment the DC uses, use of HSRP/VRRP may require anoter two IP addresses from the subnet to be used by the physical routers at their side.
You've also stated that you want to use Mikrotik as a firewall standing between those servers and the internet. The only way to insert Mikrotik's
stateful firewall into the path between the gateway provided by the DC and your servers is to have the uplink at one member port of a bridge and the servers on another one(s), and set
/interface bridge settings set use-ip-firewall=yes. This will make packets forwarded from one bridge port to another be inspected by the IP firewall rather than (or maybe in addition to? Haven't tested that yet) the bridge filter and bridge nat rules. But doing so means that the IP firewall will handle also the traffic among your servers in that subnet, so it must be configured accordingly. More than that, this setting is common to all bridges, so you'll also have to add rules to the IP firewall which will allow the devices connected to the LAN bridge to talk to each other if necessary. If you don't need the stateful firewall and can live with a stateless one, without address lists etc., the bridge rules may be sufficient. Not knowing your requirements is hard to guess.
To further complicate things. I would also like to have some sort of redundancy routing. I plan on adding a 2nd router or using a switch for VRRP. I am not sure what the best way to go about that yet either.
...
I assume to use VRRP i will need a 2nd router or perhaps a switch and 2 routers.
...
The data center provides 2 connections for a primary and secondary connection. I can use either but only one will route at a time. I am not sure of it is even possible to have true rputer redundancy with out using cisco equipment.
VRRP/HSRP is an L3 redundancy mechanism, which means that all the members of the VRRP group must be in the same subnet and L2 segment. Hence a combination of two physical uplinks with VRRP must include also some kind of L2 redundancy, such as STP. If that is the case, you can use two Mikrotik CCR at your end as well. Provided that each of the servers on public IPs has two network interfaces which can be configured for bonding or teaming with a preference of one link, the VRRP L3 redundancy provided by the DC will be enough for these servers. The requirement to use only one uplink at a time will be fulfilled automatically as the STP works like that.
Providing redundancy for the LAN devices, however, requires the two Mikrotiks to run VRRP too, as the traffic to the LAN subnet will be routed via Mikrotik's public address. Mikrotik's implementation of VRRP allows that a different subnet on the same L2 segment is used for the VRRP communication between the physical routers, so if the DC doesn't mind having a private subnet in the same (V)LAN where the public one for you is running, you can still use only the virtual IP as a public one; if you have to use public IPs for the physical routers, two more are gone.
If the DC runs VRRP too, it is important to assign a different VRRP group ID to the Mikrotiks to avoid conflict.
To provide redundancy to the LAN hosts, another instance of VRRP must be running on the LAN subnet; you'll have to either use a script to let the VRRP at the LAN side track the one at the WAN side, or create a link subnet between the two Mikrotiks so that a traffic for the LAN subnet received by the one which is active VRRP-wise on WAN could be delivered via the second one which is active VRRP-wise on the LAN.
Another way to provide redundancy using two Mikrotiks is to use
@nathan1's High Availability setup rather than STP and VRRP at your side.
But whichever way you choose will be affected by the absence of a way to synchronize the connection tracking table between two routers in RouterOS. Which is another reason to use stateless firewall for the production traffic if possible.