[IM] Fully disable standard community filtering if route server ASN i…

…s 32bit

While strictly speaking the first filter (0,peeasn) could work, the other
do will not. Better to be explicit and match the documentation and fully
disable community based filtering for route servers with a 32bit asn.

Reminder: we discourage using 32bit ASNs for route servers:

> You are strongly advised to use / request a 16-bit ASN from your RIR
> for route server use. If you do not, you will be unable to offer your
> members standard community based filtering.

Separatrely, we have a feature in development that will allow people to
set filters in the UI and which uses large BGP communities internally.

data/travis-ci/known-good/ci-apiv4-b2-rs1-lan1-ipv4.conf

@@ -172,7 +172,7 @@ function ixp_community_filter(int peerasn)
             return true;
 
     # it's unwise to conduct a 32-bit check on a 16-bit value
-    if peerasn > 65535 then
+    if routeserverasn > 65535 || peerasn > 65535 then
             return true;
 
     # Implement widely used community filtering schema.

data/travis-ci/known-good/ci-apiv4-b2-rs1-lan1-ipv6.conf

@@ -183,7 +183,7 @@ function ixp_community_filter(int peerasn)
             return true;
 
     # it's unwise to conduct a 32-bit check on a 16-bit value
-    if peerasn > 65535 then
+    if routeserverasn > 65535 || peerasn > 65535 then
             return true;
 
     # Implement widely used community filtering schema.

resources/views/api/v4/router/server/bird2/community-filter.foil.php

@@ -70,7 +70,7 @@ function ixp_community_filter(int peerasn)
 
 <?php endif; ?>
     # it's unwise to conduct a 32-bit check on a 16-bit value
-    if peerasn > 65535 then
+    if routeserverasn > 65535 || peerasn > 65535 then
             return true;
 
     # Implement widely used community filtering schema.