RR reflects customer routes, the route is not delivered to the forwarding table.

曾小小 flyinsky2018 at gmail.com
Fri Nov 27 04:24:51 CET 2015


Hi All,

I have 3 routers connected like this.

           R1 (RR)
         /       \
        /         \  (AS100)
    /            \
    R2           R3
 (client_1)  (client_2)

 I am using Ubuntu 14.04, bird version is 1.5.0

 Between the R1, R2, R3 OSPF establish IGP full mesh. R1 is configured as
RR, R1 and R2, R1 and R3 establish IBGP connections .
 R2 redistribute static routes via BGP, to AS100, R3 can receive routing
information from R2, and R1 (RR) can also receive R2 advertised routing
information, and delivered to the forwarding.
 If this routes by the R1 will be sent to the forwarding, it will directly
affect the business.
 How to use the BIRD in BGP configuration commands let R1 is not delivered
to the forwarding?

 another question:
 Also on the use of “next hop self”, and what is the use in BGP as well?
 I know that within an AS, if learned from EBGP routing information, you
can modify the next hop address of the border router interface.



=====
 about r3 routeing information link this:

 6.6.6.6/32         via 192.168.1.68 on vlan2 [bgp_r1 07:27:16 from
192.168.10.126] * (100/?) [i]
Type: BGP unicast univ
BGP.origin: IGP
BGP.as_path:
BGP.next_hop: 192.168.1.68
BGP.local_pref: 100
BGP.originator_id: 192.168.1.68
BGP.cluster_list: 1.1.1.1


all configuration information is as follows

 R1:
  ====
##template about rr
template bgp rr_client {
        debug { states,interfaces,events };
        description "ibgp-rr1";
        local 192.168.10.126 as 64600;
        multihop;
        rr client;
        rr cluster id 1.1.1.1;
        }


 filter bgp_out_r1
{
        if net ~ [ 6.6.6.6/32, 7.7.7.7/32 ] then accept;
        reject;
}


protocol bgp rr_r2 from rr_client {
        neighbor 192.168.1.68 as 64600;
        export filter bgp_out_r1;
        import all;
        #next hop self;
        }

protocol bgp rr_r3 from rr_client {
        neighbor 192.168.2.69 as 64600;
        export filter bgp_out_r1;
        import all;
        #next hop self;
        }

 ====
 R2:
filter bgp_out_r2
{
        if net ~ [ 6.6.6.6/32, 7.7.7.7/32 ] then accept;
        reject;
}

protocol bgp bgp_r2 {
debug { states,interfaces,events };
    description "ibgp-rr1";
import all;
export filter bgp_out_r2;
    local as 64600;
    neighbor 192.168.10.126 as 64600;
    source address 192.168.1.68;
next hop self;
}

 ===
 R3:
  protocol bgp bgp_r3 {
debug { states,interfaces,events };
        description "ibgp-rr1";
import all;
export all;
        local as 64600;
        neighbor 192.168.10.126 as 64600;
        source address 192.168.2.69;
next hop self;
}
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20151127/b8e43f95/attachment.html>


More information about the Bird-users mailing list