[quagga-users 14898] Zebra / quagga with BGP combined with policy based routes.
Stephan Viljoen <steph-AbhRyTB+pGlmR6Xm/[email protected]> Thu, 11 Jan 2018 11:30:24 +0200
| Newsgroups | gmane.network.quagga.user |
|---|---|
| Message-ID | <CAMCWjp0e5E9+aK50jp6exVXjYWXaofcxPU9fuR330_G50=OxAQ@mail.gmail.com> |
Hi There, I'm fairly new to working with dynamic routing protocols and would appreciate it if someone is willing to give me some advice with the following scenario. I've configured an edge router with three wan connection on it. 1: The first link goes to my primary upstream provider which acts as my default gw .. nothing special here. 2: The second link goes to a secondary upstream provider where I'm using policy based routes for only certain internal pre-fixes . 3: The third link is where things gets interesting :) This is a local peering connection with other service providers using BGP .. so I've configured Zebra / quagga with BGP which works pretty good. So my question is , is it possible to give the routes received via BGP priority over the policy based routes ? So for instance , if a customer comes from an ip-prefix with a policy based route in place is it possible to follow the BGP route first before following the policy set for it ? I did find a cumbersome way around the problem but I'm pretty sure this is an unnecessary step. I ended up configuring a second based policy for all those pre-fixes with a lower priority for the BGP routes . So if a customer wants to access content via the peering link it will try and route there first following the lower priority route but this comes with it's own problems like when a peering host is down it's still going to try and follow the route configured via policy based which kinda makes the whole idea behind using BGP useless. Small example. 500: from 10.0.243.0/24 lookup PEERING : This I feel is unnecessary and would like to configure the incoming BGP pre-fixes with a higher priority so this route will get followed first instead of creating a policy based route for each of the incoming pre-fixes which renders the BGP setup useless. ip route list table PEERING 168.167.252.0/24 via 192.168.179.40 dev enp2s0f1.555 168.167.253.0/24 via 192.168.179.40 dev enp2s0f1.555 168.167.254.0/24 via 192.168.179.40 dev enp2s0f1.555 168.167.255.0/24 via 192.168.179.40 dev enp2s0f1.555 510: from 10.0.243.0/24 lookup UPSTREAM2 default via 41.191.x.x dev enp2s0f0.210 : Gateway to second upstream; I really hope I'm making some sense here. Thanks in advance,