iBGP migration to 1.3.0 [Was: Re: Patch to fix BGP ghost routes resulting from loops]

[Ondrej Zajicek]

On Sun, Apr 03, 2011 at 03:30:56PM +0000, Nick wrote:
> 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
> something else?

No, this is bug: http://marc.info/?l=bird-users&m=130165846402471&w=2

Just explicitly configure router ID to fix that, or use bugfix from
git version.

-- 
Elen sila lumenn' omentielvo

Ondrej 'SanTiago' Zajicek (email: santiago at 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."
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20110403/d971d313/attachment-0001.asc>