Brillant.
Works wonderfully.
Just tried it on a spare prefix.
Seem to be effective quite quickly.
It blackholed traffic within 5/10 secs ans stops blackholing within
10/20 secs from removal.
Thanks
On 12/02/2016 15:43, Peter Hessler wrote:
We also have the same RTBH service with the same provider, and this is
how we do that:
group {
announce all
....
}
deny to group "BLACKHOLE"
allow to group "BLACKHOLE" community $MY_AS:666
(btw, they are not the fastest at removing the blackhole. Seconds for
it to apply, minutes to remove.)
On 2016 Feb 12 (Fri) at 14:23:08 +0100 (+0100), Laurent CARON wrote:
:Hi,
:
:I'm trying to achieve the following:
:
:I have a RTBH peer configured (router from my ISP I access over multihop).
:
:Config is the following:
:
:group "eBGP_RTBH_COGENT" {
:
: remote-as 174
: holdtime 30
: holdtime min 3
: announce none
: set med 325
: set localpref 50
: multihop 64
:
: neighbor $COGENT_RTBH_PEER_IPv6 {
: descr ev6_gw-003_to_RTBH_COGENT
: local-address $COGENT_MY_IPv6
: announce IPv4 none
: announce IPv6 none
: }
:
: neighbor $COGENT_RTBH_PEER_IPv4 {
: descr ev4_gw-003_to_RTBH_COGENT
: local-address $COGENT_MY_IPv4
: announce IPv4 none
: announce IPv6 none
: }
:
:}
:
:
:I have a community I defined:
:COMMUNITY_RTBH="$MY_AS:666"
:
:When i set this community to prefixes a match clause adds the carrier
:specific community to get the blackholing done on their side (easy when the
:BH prefix is carried by the regular BGP session).
:
:Now I wonder how to send BH prefixes to this very peer in the same way.
:
:Thanks
:
