Community-list delete

[Bogdan Zapca]

Hello,

There seems to be a problem with community-lists and route-map's "set 
community-list NAME delete"

Having an expanded community-list like:
Named Community expanded list comm-client
    deny 8708:120
    deny 8708:80
    deny 8708:100[0-3]
    deny 8708:200[0-3]
    deny 8708:1999
    deny 8708:2900
    deny 8708:10000
    permit 8708:.*

and a route-map

route-map map permit 100
 set comm-list comm-client delete
 set community 8708:3000 additive
!

the resulting community on any prefix is always 8708:3000(the initial 
prefix has several communities including valid ones).

Even with a standard community-list like:

deny 8708:1000
permit 8708:1000 (both are 8708:1000)

the 8708:1000 community is deleted.

The problem seems to be the aproach: instead of doing a 
COMUNITIES_ATTRIBUTE check against the COMMUNITY-LIST(each community 
checked against the list until a match is found) the 
functions(route_set_community_delete and community_list_match_delete) 
are building a list(based on COMMUNITY_PERMIT - permit statements only) 
that is checked against the COMUNITIES_ATTRIBUTE.

Affected zebra versions:
0.93 (a and b) and current CVS version. Haven't tested versions prior to 
0.93a.


Regards,
--
 Bogdan Zapca
 Romania Data Systems NOC in Bucharest
 Network Engineer
 Phone: +40 21 30 10 888
 Fax: +40 21 30 10 851
==------------------------------------------------------------------------==
Privileged/Confidential Information may be contained in this message.
If you are not the addressee indicated in this message (or responsible for
delivery of the message to such person), you may not copy or deliver 
this message
to anyone. In such a case, you should destroy this message and kindly
notify the sender by reply e-mail.
==------------------------------------------------------------------------==