On Wed, May 02, 2007 at 11:50:33AM +0100, Jon Morby wrote: > On 21 Apr 2007, at 14:38, Henning Brauer wrote: > > > * Ond??ej Sur?? <[EMAIL PROTECTED]> [2007-04-21 14:58]: > >> Hi, > >> > >> Jon Morby pm9e v So 21. 04. 2007 v 12:13 +0100: > >>> Not sure if you're still trying to fix this, or if you're > >>> sorted .... > >>> but if you're still having problems > >>> > >>> What does your filters section look like ? > >> > >> It's very simple now - none. But filters just modify prefixes > >> accepted > >> and not coupling. I do receive IPv6 prefixes they are just not > >> coupled > >> into kernel. > > > > i guess there is some bug. > > since i have no v6 here it is a bit hard to reproduce and fix > > > > I must admit I'm starting to notice some weirdness .... mostly > anecdotal at this stage, however it seems that > > with "announce IPv4 none" but a "global" filter allowing export of v4 > prefixes we're still announcing / saying we have v4 addresses - we're > finding some peers rejecting sessions from us when we have "announce > all" and "allow to any community xxxx:yyyy" > > I'm trying to throw enough hardware into a pool to be able to test > this in more detail. You're welcome to accounts on them if necessary > for testing / etc if it will help ? >
This sounds rather strange. "announce IPv4 none" should have precedence over the filters so no IPv4 update should go out at all. Can you provide mrt dumps of the problematic sessions? e.g. "dump updates out" I added it to my overflowing todolist, I hope I find the time to look at it sooner rather then later. -- :wq Claudio
