437ad95646
implements a new feature: "BGP Allow list." This feature allows us to control which IP prefixes are going to be advertised via ebgp from the routes received from EBGP neighbors.
41 lines
1.5 KiB
Django/Jinja
41 lines
1.5 KiB
Django/Jinja
!
|
|
! template: bgpd/templates/general/peer-group.conf.j2
|
|
!
|
|
neighbor PEER_V4 peer-group
|
|
neighbor PEER_V4_INT peer-group
|
|
neighbor PEER_V6 peer-group
|
|
neighbor PEER_V6_INT peer-group
|
|
address-family ipv4
|
|
{% if CONFIG_DB__DEVICE_METADATA['localhost']['type'] == 'ToRRouter' %}
|
|
neighbor PEER_V4 allowas-in 1
|
|
neighbor PEER_V4_INT allowas-in 1
|
|
{% endif %}
|
|
{% if CONFIG_DB__DEVICE_METADATA['localhost']['sub_role'] == 'BackEnd' %}
|
|
neighbor PEER_V4_INT route-reflector-client
|
|
{% endif %}
|
|
neighbor PEER_V4 soft-reconfiguration inbound
|
|
neighbor PEER_V4 route-map FROM_BGP_PEER_V4 in
|
|
neighbor PEER_V4 route-map TO_BGP_PEER_V4 out
|
|
neighbor PEER_V4_INT soft-reconfiguration inbound
|
|
neighbor PEER_V4_INT route-map FROM_BGP_PEER_V4 in
|
|
neighbor PEER_V4_INT route-map TO_BGP_PEER_V4 out
|
|
exit-address-family
|
|
address-family ipv6
|
|
{% if CONFIG_DB__DEVICE_METADATA['localhost']['type'] == 'ToRRouter' %}
|
|
neighbor PEER_V6 allowas-in 1
|
|
neighbor PEER_V6_INT allowas-in 1
|
|
{% endif %}
|
|
{% if CONFIG_DB__DEVICE_METADATA['localhost']['sub_role'] == 'BackEnd' %}
|
|
neighbor PEER_V6_INT route-reflector-client
|
|
{% endif %}
|
|
neighbor PEER_V6 soft-reconfiguration inbound
|
|
neighbor PEER_V6 route-map FROM_BGP_PEER_V6 in
|
|
neighbor PEER_V6 route-map TO_BGP_PEER_V6 out
|
|
neighbor PEER_V6_INT soft-reconfiguration inbound
|
|
neighbor PEER_V6_INT route-map FROM_BGP_PEER_V6 in
|
|
neighbor PEER_V6_INT route-map TO_BGP_PEER_V6 out
|
|
exit-address-family
|
|
!
|
|
! end of template: bgpd/templates/general/peer-group.conf.j2
|
|
!
|