Re: Best practice for route preference

Hi, Speaking about general routing (not specially Bird), I would say that what you want would be perfectly managed by the «advertise best external» feature, which makes a router advertise in iBGP its best external paths, even if they are not the overall best path. This way, in conjunction with so

Re: New RIP MD5 interface option to avoid sequence check

crit : > > On Mon, Oct 03, 2022 at 04:20:51AM +0200, Olivier Benghozi via Bird-users > wrote: >> Hello, >> >> I'm currently using RIP/Ripng with md5 auth with some Cisco/Juniper and >> Quagga gears. >> I'm looking to switch from quagga to Bird(2

New RIP MD5 interface option to avoid sequence check

Hello, I'm currently using RIP/Ripng with md5 auth with some Cisco/Juniper and Quagga gears. I'm looking to switch from quagga to Bird(2). I would have a feature request about the RIP MD5 sequence number check (RFC rule, implemented by BIRD, is: accept only increasing sequence numbers, or accep

Re: Routes received from another AS marked as IGP

This is the (now completely useless) mandatory ORIGIN attribute in BGP. It can be either IGP, EGP, or INCOMPLETE. It was used in prehistoric times to allow proper transition from EGP to BGP. Actually it has nothing to do with IGP today. BGP implementations can mark redistributed routes as IGP (B

Re: BGP Connection reset on fast timers

Just a comment: here we use 5/15 on some 10GE links between Redback/Ericsson/SmartEdge and Cisco routers (so, unrelated to BIRD and Linux) with success (never flaps if the link is OK). These links are used to receive/transmit L2TP tunnels traffic. The usecase was: 1) there are some intermediate

Re: BGP origin attribute

But as a mandatory attribute, how can it be conceptually allowed to remove this attribute between BGP and BGP ? > Le 31 mai 2018 à 16:10, Ondrej Zajicek a écrit : > > If the route is from BGP but bgp_origin attribute was removed by filters -> > use ORIGIN_INCOMPLETE.

Re: BGP origin attribute

And on Juniper side, all redistributed route are IGP :P Which is probably smart, since BGP origin attribute is an oldie created for compatibility with EGP, and that should have since been killed a long time ago, so everything as IGP makes sense (to basically remove origin from the best route cho

Re: Syntax for setting bgp_origin

bgp_origin = 2; >accept; >} >reject; > } > > > 22.12.2015, 03:05, "Olivier Benghozi" : >> Yep, it's not very user friendly... The doc is problematic about this >> attribute. >> >> In fact it appears

Re: Syntax for setting bgp_origin

Yep, it's not very user friendly... The doc is problematic about this attribute. In fact it appears that you must use 0/1/2 (values following the RFC), so for incomplete you must use 2. > Le 21 déc. 2015 à 21:48, Гаврилов Игорь a écrit : > > Hi everyone! Could someone show me how to set bgp_or

Re: BFD and Juniper?

So you're trying to use BFD with iBGP, or eBGP? iBGP is multihop by nature, so BFD would also be... Anyway, did you try to use something else than APIPA addressing (Link-Local only), that might interfere with what you're trying to do? > Le 19 août 2015 à 02:21, Leighton, Russell a écrit : > >

Re: OSPF and mass route deletion

OSPF doesn't delete "routes", it sends LSAs. It seems that you are redistributing a lot of single IP addresses in OSPF (as external routes). So there's one LSA type 5 for each single redistributed /32. OSPF is not the proper choice for this usecase, and it's not a Quagga or BIRD issue. BGP is th

Re: How to export address from loopback via BGP

Use protocol direct, as detailed in http://bird.network.cz/?get_doc&f=bird-6.html#ss6.4 > Le 11 nov. 2014 à 12:54, Eugene Prokopiev a écrit : > > Hi, > > How to export address 1.1.1.1/32 from lo interface via BGP? I tried to do: > > route

Re: Best route selection

> Le 3 nov. 2014 à 17:13, Ondrej Zajicek a écrit : > On Mon, Nov 03, 2014 at 04:42:55PM +0100, Olivier Benghozi wrote: >> Firstly, in classical BGP implementations (but not in BIRD), for eBGP >> connections, router-id is never used as tie-break. Instead, route age is >&

Re: Best route selection

Firstly, in classical BGP implementations (but not in BIRD), for eBGP connections, router-id is never used as tie-break. Instead, route age is used (the oldest one wins) as tie-break. It avoids frequent route changes and probably improves a little routes distribution. You'd better use "prefer ol