[rbak-nsp] blackholing in SEOS12.x

[Tomas Lynch]

Never did black hole with SEOS but what about double next hop, something
like:

route-map whatever
 set next-hop 1.1.1.1
!
ip route 1.1.1.1/32 2.2.2.2/32
ip route 2.2.2.2/32 null0

Not a BCP way to do it but maybe it works. Another option, not tested, is
to setup the next hop close to your customer and then the null route close
to your Internet exit.


On Wed, Feb 26, 2014 at 9:34 AM, Marcin Kuczera <marcin at leon.pl> wrote:

> hello,
>
> does anyone knows how to set up BGP blackholing in SEOS 12.x  ?
>
> The problem is that in route-map you can not point null0 as next-hop, but
> if you try
> to do:
> ip route 192.168.168.168 null0
> and then in route map:
> set ip next-hop 192.168.168.168
>
> system sais that circuit is invalid and that there is no path to that next
> hop (192.168.168.168)
>
> [bgp1]R0_SE600#show bgp route 192.168.189.5/32
> BGP ipv4 unicast routing table entry: 192.168.189.5/32, version 67911247
> Paths: total 1, best path count 0, best peer 0.0.0.0
> Not downloaded to RIB (no bestpath)
> Not advertised to any peer
>
> 65530
>   Nexthop 192.168.168.168 (inaccessible), peer 195.66.73.5 (195.66.73.5),
> AS 65530
>   Origin IGP, localpref 100, med 0, weight 100, external
>   Community: 65530:9999 no-export no-advertise
>
> [bgp1]R0_SE600#show configur
> [bgp1]R0_SE600#show configuration | grep 192.168.168.168
>   set ip next-hop 192.168.168.168
>  ip route 192.168.168.168/32 null0 description BGP BlackHole
> [bgp1]R0_SE600#
>
> So SEOS can not set next hop (inaccessible) - this was working in 6.x line
> as I remember...
>
> Regards,
> Marcin
>
> _______________________________________________
> redback-nsp mailing list
> redback-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/redback-nsp
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/redback-nsp/attachments/20140227/ac68ad10/attachment.html>