The filter matches communities TRANS-ANNOUNCE, but it does not delete TRANS-ANNOUNCE prior to sending the advertisement on to the provider. This is used as a outbound filter on a BGP peer.
delete bgp-communities other; Works, but it then removes all communities, and not only the communities in the TRANS-ANNOUNCE community-list
And yes, given the equals statement as well as manual confirmation - TRANS-ANNOUNCE includes 1 community in the list, and it is a complete, and full match.
deleting and filtering on BGP communities is currently broken…
“delete bgp-communities …” and “filter bgp-communities …” are currently inverted when a community list used or the community is specified inline.
On the other hand, if a regex is used, the community is always deleted regardless if delete or filter.
I reported it to support in March (SUP-110901) but never got any response.
The problem still exists on the current release and I was surprised that no one else has noticed it.
Thank you for the report, we will swap filter and delete behavior in one of the next versions.
September 21st:
This is an automated message. Our bug tracker reports, that your issue has been fixed. This means that in the upcoming days, we plan to release a RouterOS update with this fix.
I’d say it’s looking good and I’m looking forward…
BUT I’m still looking for an equivalent for ROS 6 - IS there any chance I can delete a community via route filter on ROS6?!?
Thanks for responding, but that doesn’t remove a community per se, so I would have to “know” the complete list of communities that need to stay in the community string except for the one I need to remove.
Or am I reading you wrong?
Looks like once again a “delete bgp-communities 65001:999” results in deleting all BUT this community.
I disovered this in our production network right now, will setup a small test for this, but I wondered, whether somebody else here uses delete bgp-communities with 7.19.6 successfully?
Will report back after further tests… with more debug.