Static route bgp_next_hop attribute.

oldnick nsp oldnick.nsp at gmail.com
Tue May 29 13:23:30 CEST 2018


Hi all!

I'm trying to use Bird to announce route with predefined bgp next hop and
to avoid filter manipulation on this route to set next-hop on it. My goal
is to put route configuration into separate include file with fewer lines
as possible.

Relevant part of my config is as follows:

protocol bgp 'test_nbr' {
       local as 65001;
       neighbor 10.0.0.2 as 65002;
       hold time 30;
       multihop 5;
       import all;
       export all;
       next hop keep;
}

protocol static test {
  route 192.168.0.1/32 blackhole {
    bgp_next_hop = 172.16.0.1;
};
}

I can see that route has bgp_next_hop attribute with command "show route
all":
bird> show route all
192.168.0.1/32     blackhole [test 07:05:07] * (200)
    Type: static unicast univ
    BGP.next_hop: 172.16.0.1

But when neighbor receives this announce, it still gets the peer address as
a next-hop. This is debug output at neighbor side:
*May 29 14:05:02.327: BGP(0): 10.0.0.1 rcvd UPDATE w/ attr: nexthop
10.0.0.1, origin i, merged path 65001, AS_PATH
*May 29 14:05:02.331: BGP(0): 10.0.0.1 rcvd 192.168.0.1/32

So, the question is: is there any way to keep bgp_next_hop attribute from
static route into protocol bgp announces?

--
Regards,
Sergey
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20180529/32e7da27/attachment.html>


More information about the Bird-users mailing list