2025-02-05 10:03:58 +01:00
|
|
|
router bgp 65001
|
|
|
|
|
no bgp ebgp-requires-policy
|
|
|
|
|
no bgp network import-check
|
2025-02-05 10:17:20 +01:00
|
|
|
bgp route-reflector allow-outbound-policy
|
2025-02-05 10:03:58 +01:00
|
|
|
neighbor 192.168.35.3 remote-as internal
|
|
|
|
|
neighbor 192.168.35.3 timers 1 3
|
|
|
|
|
neighbor 192.168.35.3 timers connect 1
|
|
|
|
|
neighbor 192.168.35.3 aigp
|
|
|
|
|
neighbor 192.168.35.3 route-reflector-client
|
|
|
|
|
neighbor 10.0.0.6 remote-as internal
|
|
|
|
|
neighbor 10.0.0.6 timers 1 3
|
|
|
|
|
neighbor 10.0.0.6 timers connect 1
|
|
|
|
|
neighbor 10.0.0.6 update-source lo
|
|
|
|
|
address-family ipv4
|
2025-02-05 10:17:20 +01:00
|
|
|
redistribute connected route-map connected-to-bgp
|
|
|
|
|
neighbor 192.168.35.3 route-map set-nexthop out
|
2025-02-05 10:03:58 +01:00
|
|
|
exit-address-family
|
|
|
|
|
!
|
2025-02-05 10:17:20 +01:00
|
|
|
! Two OSPF domains should be isolated - otherwise the connected routes
|
|
|
|
|
! on r5 would be advertised to r2 (via r5 -> r6 -> r4 -> r2), and can
|
|
|
|
|
! mess up bgp bestpath calculation (igp metrics for the BGP nexthops).
|
|
|
|
|
!
|
|
|
|
|
route-map connected-to-bgp permit 10
|
|
|
|
|
set community no-advertise
|
|
|
|
|
!
|
|
|
|
|
route-map set-nexthop permit 10
|
|
|
|
|
set ip next-hop peer-address
|
|
|
|
|
exit
|
|
|
|
|
!
|
