Trying to configure RTBH. Pretty standard
setup:
1. static route on the trigger with a tag
2. redistribute that static into BGP and
assign community value
3. advertise it to an ISP edge router w/
the next hop of 192.0.2.1/32 so ISP
will drop traffic
The only difference between classic config
and mine is that trigger router and ISP
edge routers are in different AS (eBGP
peering).
Error message is above in the subject
received on the ISP edge routers when
receiving offending prefix from the trigger
Interesting if it is a bug or it happens because of eBGP peering instead of iBGP
between trigger and blackhole routers.
Thanks,
OW
