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

Unanswered Question
Mar 7th, 2007

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

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
owaisberg Thu, 03/08/2007 - 08:33

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

Actions

This Discussion