Re: Best practices for redundant iBGP/eBGP route distribution? [bird 2.0.7]

Follow up 2: it seems that bird1.6 behaves differently to bird 2.0.7: bird> show route all for 2a0a:e5c1:111:111:6aa6:5bc:535a:8e21 2a0a:e5c1:100::/40 via 2a0a:e5c0:1:8::6 on bond0.8 [router2_place6_ungleich_ch_v6 2019-12-03] * (100) [i] Type: BGP unicast univ BGP.origin: IGP BGP.as_path: BGP.next_hop: 2a0a:e5c0:2:2:0:84ff:fe41:f24d BGP.local_pref: 500 bird> (this is from the 2nd router pair, still running bird 1.6) Is it possible that the nexthop resolution algorithm changed in bird2 vs bird1? -- Modern, affordable, Swiss Virtual Machines. Visit www.datacenterlight.ch