On Sun, Apr 03, 2011 at 05:36:27PM +, 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
On Sun, Apr 03, 2011 at 06:32:26PM +0200, Ondrej Zajicek wrote:
> On Sun, Apr 03, 2011 at 03:30:56PM +, 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 r
On Sun, Apr 03, 2011 at 03:30:56PM +, 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 trig
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 ro
On Sat, Apr 02, 2011 at 07:53:35AM +0200, Adrian Czapek wrote:
> Oh, thanks for refreshing this thread, it gives some light on my
> mysterious problem I encountered yesterday while trying to upgrade from
> 1.2.5>1.3.0 on one of my route reflector client.
> I just switched binaries and left the
