ffae82f8be
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.
47 lines
1.2 KiB
YAML
47 lines
1.2 KiB
YAML
constants:
|
|
deployment_id_asn_map:
|
|
"1" : 65432
|
|
"2" : 65433
|
|
bgp:
|
|
traffic_shift_community: 12345:12345
|
|
families:
|
|
- ipv4
|
|
- ipv6
|
|
use_deployment_id: false
|
|
use_neighbors_meta: false
|
|
graceful_restart:
|
|
enabled: true
|
|
restart_time: 240
|
|
multipath_relax:
|
|
enabled: true
|
|
maximum_paths:
|
|
enabled: true
|
|
ipv4: 64
|
|
ipv6: 64
|
|
allow_list:
|
|
enabled: true
|
|
default_action: "permit" # or "deny"
|
|
drop_community: 5060:12345 # value of the community to identify a prefix to drop. Make sense only with allow_list_default_action equal to 'permit'
|
|
default_pl_rules:
|
|
v4:
|
|
- "deny 0.0.0.0/0 le 17"
|
|
- "permit 127.0.0.1/32"
|
|
v6:
|
|
- "deny 0::/0 le 59"
|
|
- "deny 0::/0 ge 65"
|
|
- "permit fe80::/64"
|
|
peers:
|
|
general: # peer_type
|
|
db_table: "BGP_NEIGHBOR"
|
|
template_dir: "general"
|
|
monitors: # peer_type
|
|
enabled: true
|
|
db_table: "BGP_MONITORS"
|
|
peer_group: "BGPMON"
|
|
template_dir: "monitors"
|
|
dynamic: # peer_type
|
|
enabled: true
|
|
db_table: "BGP_PEER_RANGE"
|
|
peer_group: "BGP_SPEAKER"
|
|
template_dir: "dynamic"
|