BGP: Malformed attribute list

[Wolfgang Hennerbichler]

Allright, reply to myself: 

This seems to be a bug in BIRD. 
What I actually added was a rule that certain communities should be deleted: 
if ((1120,1)) ~ bgp_community then bgp_community.delete((1120,1));

this actually seemed to delete the only community attached to a certain prefix, which led to a bgp announcement that contained the community attribute which was in fact empty. this causes some cisco routers to throw up on the bgp session. So I think this is a bug in BIRD - if the last community is deleted on a prefix, the community tag must no longer be attached to the prefix. What do you think? Are there any chances you could fix this in the coming update? 

Wolfgang

On Apr 8, 2010, at 14:05 , Wolfgang Hennerbichler wrote:

> Hi BIRD-Users, 
> 
> I just got into a situation here... 
> I reconfigured my bird (with some new filter rules on BGP), but now some peerings don't come up anymore: 
> 
> bird> show protocols R8596x130
> name     proto    table    state  since       info
> R8596x130 BGP      T8596x130 start  12:03       Idle