Community operations got broken after upgrade to 1.3.6 from 1.2.4

[Ondrej Zajicek]

On Fri, Mar 02, 2012 at 05:46:37PM +0200, Alexander Shikoff wrote:
> Hello!
> 
> After upgrade my Route Servers from 1.2.4 to 1.3.6 community processing
> got broken. Simple function
> 
> function check_community ()
> pair set wrong;
> {
>         #
>         # Delete disallowed communities
>         #
>         wrong = [
>                 # 0:XXXXX - Do not announce to peer   
>                 (0,0)..(0,99),
>                 (0,101)..(0,65535)
>         ];
>         bgp_community.delete(wrong);
> }
> 
> 
> deletes ALL communities (0,*) including (0,100).

Thanks for the bugreport. The bug was not in delete, but in pair set
parsing/construction, so (0,101)..(0,65535) was parsed as
(0,0)..(101,65535). You can use attached patch or you can workaround
it by using (0,101..65535) expression.


-- 
Elen sila lumenn' omentielvo

Ondrej 'SanTiago' Zajicek (email: santiago at 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."
-------------- next part --------------
A non-text attachment was scrubbed...
Name: clist.patch
Type: text/x-diff
Size: 566 bytes
Desc: not available
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20120304/d9f12e4b/attachment-0001.patch>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20120304/d9f12e4b/attachment-0001.asc>