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 05:36:27PM +0000, Nick wrote:
> This is interesting.  I read that bug report and set a router ID in the
> first line in my config before my post.  I also did birdc configure after
> setting a router ID in the config and it did not correct the problem.
> I left the router ID in the config when I switched back to 1.2.1 and
> now when I upgraded to 1.3.0 again it sends the router ID.  Does birdc
> configure fail to update the router ID?

Generally, you can update router ID using configure (although it always
restarts all protocols in that case), but in this case it didn't
worked, because bird already used that router ID, just one internal
variable in BGP had bad value.

-- 
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/20110404/0ac832a9/attachment-0001.asc>