Ehhh correction. I think you could do what you wanted with VRF, but you actually could likely get by with policy based routing (PBR) so the routing table was aware of both interfaces. As ugly as PBR is in most cases, it might be a bit cleaner here. On Jan 14, 2016 11:00 AM, "Josh Reynolds" <j...@kyneticwifi.com> wrote:
> Look into VRF. > On Jan 14, 2016 10:52 AM, "That One Guy /sarcasm" < > thatoneguyst...@gmail.com> wrote: > >> We have a customer who has two connections to us >> Their firewall eth0 connects to ether4 with a /29 and their eth1 connects >> to ether5 >> They have a 3rd party 10mb fiber circuit on ether1 that terminates in our >> NOC for the /29 traffic and the ether2 connects to our wireless network for >> their /30 >> >> the /30 is for their internet traffic, the /29 is for their VOIP and VPN >> >> I have OSPF enabled on the fiber, so both subnets are routing through the >> fiber right now, Im trying to avoid any static routes on anything other >> than the CPE mikrotik to get traffic flowing the right direction, allowing >> the fiber to fail over to the wireless both in failure and as a last resort >> for spillover above the 10mb >> >> Is this clear as mud? Currently we only have static and OSPF capability >> on our network >> >> -- >> If you only see yourself as part of the team but you don't see your team >> as part of yourself you have already failed as part of the team. >> >
