Hi Eelco, use the iproute2 tool: # ip route show Testing this on my workstation: # ip route add 66.66.66.66/32 nexthop via 55.55.55.1 nexthop via 55.55.55.3 # ip route show ... 66.66.66.66 nexthop via 55.55.55.1 dev du weight 1 nexthop via 55.55.55.3 dev du weight 1 ... # route -n ... 66.66.66.66 55.55.55.1 255.255.255.255 UGH 0 0 0 du ... MQ On 08/09/2016 11:35 AM, Eelco Nieuwstad wrote:
Hi Ondrej,
after upgrading to 1.6 the config parses ok, but when I learn the same route from two different neighbors only one (the youngest) is added to the routing table bird> show route all 172.20.1.1/32 via 172.16.2.11 on ens9 [bgp3 05:27:12] * (100) [AS65001i] Type: BGP unicast univ BGP.origin: IGP BGP.as_path: 65001 BGP.next_hop: 172.16.2.11 BGP.local_pref: 100 via 172.16.2.12 on ens9 [bgp4 05:26:58] (100) [AS65001i] Type: BGP unicast univ BGP.origin: IGP BGP.as_path: 65001 BGP.next_hop: 172.16.2.12 BGP.local_pref: 100 bird> exit root@firewall-1:/usr/src/bird-1.6.0# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 172.16.1.1 0.0.0.0 UG 0 0 0 ens8 172.16.1.0 0.0.0.0 255.255.255.0 U 0 0 0 ens8 172.16.2.0 0.0.0.0 255.255.255.0 U 0 0 0 ens9 172.16.3.0 0.0.0.0 255.255.255.252 U 0 0 0 ens10 172.20.1.1 172.16.2.11 255.255.255.255 UGH 0 0 0 ens9 root@firewall-1:/usr/src/bird-1.6.0#
are the two routes not considered equal as they are originated from two different BGP speakers? I am trying to build a anycast solution in which multiple end-hosts announce the same ip address.
Eelco Nieuwstad
On 09-08-16 10:28, Ondrej Zajicek wrote:
On Tue, Aug 09, 2016 at 09:23:24AM +0200, Eelco Nieuwstad wrote:
Hi,
I am running the default Bird install (1.5.0-4build1) from Ubuntu 16.0.4 and when I enable merge paths on the kernel protocol bird refuses to start because of a syntax error. This is the very default config I use. Do I miss something obvious? Hi
Merge paths feature was added in 1.6.0.