This is more of a BGP question I think. We are advertising RTBH to an upstream router, which broke after an upgrade to 7.16.2
We have a script that was issuing this command to trigger the RTBH:
/ip route add dst-address=$ip type=blackhole bgp-communities=7018:86,7922:666,65530:666
The type and bgp-communities options are no longer available, so I changed the command to this:
/ip route add blackhole dst-address=$ip
Previously I was advertising these communities to an upstream router for RTBH. The upstream router was looking for these communities. What is the recommended way to advertise these routes now?
Here is my peer, template, and filter:
/routing bgp connection
add cisco-vpls-nlri-len-fmt=auto-bits connect=yes listen=yes local.role=ebgp
name=peer1 remote.address= .as= .port=179 templates=
default
/routing bgp template
set default disabled=no output.filter-chain=bgp-out .network=bgp-networks
.redistribute=static,vpn,dhcp
add as= disabled=yes name=bgp1 output.network=bgp-networks
.no-client-to-client-reflection=yes .redistribute=bgp router-id=
/routing filter rule
add chain=bgp-out disabled=no rule=“if (protocol static && bgp-communities inc
ludes 65530:666,7018:86,7922:666) { accept; }”
add chain=bgp-out disabled=no rule=“if (protocol static) { reject; }”
Thanks!