On Tue, May 29, 2018 at 02:23:30PM +0300, oldnick nsp wrote: > Hi all! > > I'm trying to use Bird to announce route with predefined bgp next hop and > to avoid filter manipulation on this route to set next-hop on it. My goal > is to put route configuration into separate include file with fewer lines > as possible.
Hi In BIRD 1.x, default BGP route attributes were preinitialized for non-BGP routes before BGP export filter was called, so the value set in static protocol is ignored. You have to set bgp_next_hop attribute in the BGP export filter. In BIRD 2.x, the behavior was simplified to work as one expects - bgp_next_hop can be set anywhere and then it is handled similarly to one received from BGP peer (so it would work with 'next hop keep'). -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santi...@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
