On Fri, May 06, 2011 at 08:34:07PM +0200, Daniel Suchy wrote: > On 05/06/2011 01:50 AM, Ondrej Zajicek wrote: > > There are (AFAIK) only two things that may generate such error - malformed > > NLRI or its next hop attribute. Also NLRI of unexpected kind (like IPv4 in > > bird6). Perhaps the other side sends both IPv4 and IPv6 in one session? > > Just a note - we had similar issue caused by IPv6 prefix originated > somewhere (we also have full BGP). In our setup, BGP communities was not > filtered and additionaly, metric was set. If there was high ammount of > the communities and metric was set, in this case Cisco router malformed > update packet - there was empty NLRI sent out...
We found that in this case it was also a problem on the other side, which send malformed packets - NLRI was smaller that needed and one prefix in it was truncated (just two bytes for /48 prefix). Unfortunately, i don't know yet type and version of the other side. -- Elen sila lumenn' omentielvo Ondrej 'SanTiago' Zajicek (email: santi...@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."
signature.asc
Description: Digital signature