On Mon, Oct 14, 2019 at 11:08:50AM +0100, Neil Jerram wrote: > Hi - I have a topology like this, using BIRD 1.6.7: > > I want BIRD-B to reflect routes within its own AS, but also propagate > routes to and from AS 65001. So for the eBGP peering I have
> My question is how to get the ideal next-hop-self behaviour, which I > think is > > - Do next-hop-self for routes from AS 65001 that are being passed on > to Router B, C etc. Otherwise those routes will be unreachable. > > - Don't do next-hop-self for reflected routes. Next-hop-self isn't > needed here, because the downstream Router B, C etc are already > directly connected. Hello We implemented extension for next-hop-self in version 2.0.3 that allows to specify 'next hop self ebgp', this solves exactly this issue. For older versions, you would need to workaround that in filters, something like: if proto = "bgpX" then bgp_next_hop = A.b.C.D; -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: [email protected]) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
signature.asc
Description: PGP signature
