[ixpmanager] Community Tag to 32bit ASNs

[Barry O'Donovan]

Shahab,

that would be correct and the cause is this piece of configuration [1].

While it would be possible to edit this piece of code to allow a 16bit 
ASN affect a member with a 32 bit ASN this would be unwise for a number 
of reasons Nick has gone into in the past on this mailing list.

One of the main issues is that 32bit ASNs support 16bit ASNs but the 
reverse is not true and trying to hack around this will create 
unreasonable expectations from your members around community filtering 
which are technically not possible for you to support.

The answer for this member is to use large BGP communities which are 
fully supported by IXP Manager + Bird2 [2] and have fairly broad support 
these days by vendors [3].

If your member cannot support these, then you can make an exception via 
a per member filter [4] such as this one at INEX [5].

In the next couple of months we expect to release a UI where members can 
set filters within IXP Manager rather than having to configure communities.

  - Barry


[1] https://git.io/JketD
[2] 
https://docs.ixpmanager.org/features/route-servers/#well-known-filtering-communities
[3] http://largebgpcommunities.net/implementations/
[4] 
https://docs.ixpmanager.org/features/route-servers/#per-asn-import-export-filters
[5] https://git.io/Jkeqg


Shahab Vahabzadeh wrote on 07/11/2020 05:37:
> Dear All,
> Customers are claiming that their community tags (like 0:50722) is not 
> sending to customers who has 32bit ASN but all customers with 16bit ASN 
> getting them.
> Can u help? I am using bird2.
> Thanks
> 
> -- 
> 
> Cheers, Shahab
> 
> 
> _______________________________________________
> INEX IXP Manager mailing list
> ixpmanager at inex.ie
> Unsubscribe or change options here: https://www.inex.ie/mailman/listinfo/ixpmanager
> 


-- 

Kind regards,
Barry O'Donovan
INEX Operations

https://www.inex.ie/support/
+353 1 531 3339