iBGP migration to 1.3.0 [Was: Re: Patch to fix BGP ghost routes resulting from loops]
nick at somerandomnick.ano.mailgate.vanet.org
Sun Apr 3 17:30:56 CEST 2011
On Sat, Apr 02, 2011 at 12:16:38PM +0200, Ondrej Zajicek wrote:
> So i understand that routes appear in the routing table but with
> unreachable destination? This is related not to mentioned patch, but to
> main changes in iBGP that triggered this major release, and it is
> probably unrelated to route reflector setting. Essentially, the next hop
> from NEXT_HOP attribute have to be resolvable through the routing table.
> See option 'gateway direct|recursive' in the documentation.
I can't find that in the documentation, but it doesn't matter, because
my iBGP peerings fail when I upgrade a node to 1.3.0 (from 1.2.1).
It sends a 0 router ID, even when the first line in my config sets a
router ID. Is this also related to the main changes in iBGP, or is this
Wanna turn ICANN into ICANN't? Join a darknet today:
More information about the Bird-users