Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

rcv UPDATE about 2.2.2.2/32 -- DENIED due to: non-connected NEXTHOP

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

1 REPLY
New Member

Re: rcv UPDATE about 2.2.2.2/32 -- DENIED due to: non-connected

Looks like not many people in this forum tried to run RTBH.

346
Views
0
Helpful
1
Replies
CreatePlease login to create content