Hello MK and forum members, I’ve upgraded to RouterOS 7.1.1 for the support of Large BGP communities. The following has been configured, but it is not received by the upstream provider: /routing bgp connection add address-families=ip,ipv6 as=[My-AS] connect=yes disabled=no listen=yes \ local.r…

Your rules will not set community for/48 prefix. If you remove the first rule, then communities will append to all prefixes. And if those are your prefixes then probably you should use “set” instead of “append”.

Your rules will not set community for/48 prefix. If you remove the first rule, then communities will append to all prefixes. And if those are your prefixes then probably you should use “set” instead of “append”. Hello mrz, So if I understand correctly. If I remove the first rule, it will be a…

yes As far as I see it is not working yet with the following: /routing bgp connection add address-families=ip,ipv6 as=[My-AS] connect=yes disabled=no listen=yes \ local.role=ebgp name=peer2 output.filter-chain=BGP-OUT-HEP3 .network=\ bgp-networks remote.address=[IPv6-Peer-address]/128 …

You should understand that { accept ; } terminates rule processing at that point for the condition that you have matched. So when you want something else to happen (like the append community) it has to happen before that rule. Of course that should be the case in the last example that you mentione…

You should understand that { accept ; } terminates rule processing at that point for the condition that you have matched. So when you want something else to happen (like the append community) it has to happen before that rule. Of course that should be the case in the last example that you mentio…

You can check with packet sniffer if the nlri was actually sent to the upstream peer. Also if you are advertising via output.networks make sure you have corresponding route in the routing table for synchronisation.

You can check with packet sniffer if the nlri was actually sent to the upstream peer. Also if you are advertising via output.networks make sure you have corresponding route in the routing table for synchronisation. Hello mrz, Excuse my lack of knowledge, but what settings needs to be used to …

You can do a packet sniffer capture for the BGP traffic using Tools->Packet Sniffer where you select the proper interface, IP address of your router, and protocol TCP port 179 (this all to limit the capture size), and capture to a file. Then Start it, wait a while (look in Packets to see if you cap…

You can do a packet sniffer capture for the BGP traffic using Tools->Packet Sniffer where you select the proper interface, IP address of your router, and protocol TCP port 179 (this all to limit the capture size), and capture to a file. Then Start it, wait a while (look in Packets to see if you c…

RouterOS 7.1.1 Large BGP Communities

RouterOS RouterOS beta

BryanBarb January 27, 2022, 5:40pm 13

Thank you! I’ve found the packet containing the Large Community. So it is sending, datacenter is still pending on my request to look for any received community.