On Sun, Nov 04, 2007 at 11:30:20PM +0000, Tony Sarendal wrote:

quoted text
> On 11/4/07, Tony Sarendal  wrote:

> >

Thanks for all the info. I will have a look at this as well. Currently I

think it is possible that route-reflector is not bug free in cases where

you have route-reflector rings or other very complex setups. I only tested

the easy setups till now. Why you get routing loops and black-holes in

your 3 AS setups is not clear (at least for me) but I guess it may be an

issue with a failed update. I have the feeling that when we get a update

with a routing loop in it we should actually issue a withdraw for the

prefix carried in it so the following code in rde.c is looking suspicious:

	/* aspath needs to be loop free nota bene this is not a hard error */

	if (peer->conf.ebgp && !aspath_loopfree(asp->aspath, conf->as)) {

		error = 0;

		goto done;

	}
I'm mostly offline in the next days so maybe you beat me in finding a fix

for this.

--

:wq Claudio