On Mon, Oct 14, 2019 at 02:45:37PM +0100, Neil Jerram wrote: > > 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; > > > > Thanks Ondrej. Am I right in thinking that I should do this in the import > filter? (From reading the code, it appears that "next hop self" takes > effect on import.)
No, in the export filter. You import the route with the original next hop (e.g. one from AS 65001), but when exported to B,C it is reset to the local value. -- 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
