7059f42385
What I did: Make Sure for internal iBGP we are one-hop away (directly connected) by using Generic TTL security mechanism. Why I did: Without this change it's possible on packet chassis i-BGP can be established even if there no direct connection. Below is the example - Let's say we have 3 LC's LC1/LC2/LC3 each having i-BGP session session with each other over Loopback4096 - Each LC's have static route towards other LC's Loopback4096 to establish i-BGP session - LC1 learn default route 0.0.0.0/0 from it's e-BGP peers and send it over to LC2 and LC3 over i-BGP - Now for some reason on LC2 static route towards LC3 is removed/not-present/some-issue we expect i-BGP session should go down between LC2 and LC3 - However i-BGP between LC2 and LC3 does not go down because of feature ip nht-resolve-via-default where LC2 will use default route to reach Loopback4096 of LC3. As it's using default route BGP packets from LC2 towards LC3 will first route to LC1 and then go to LC3 from there. Above scenario can result in packet mis-forwarding on data plane How I fixed it:- To make sure BGP packets between i-BGP peers are not going with extra routing hop enable using GTSM feature neighbor PEER ttl-security hops NUMBER This command enforces Generalized TTL Security Mechanism (GTSM), as specified in RFC 5082. With this command, only neighbors that are the specified number of hops away will be allowed to become neighbors. This command is mutually exclusive with ebgp-multihop. We set hop count as 1 which makes FRR to reject BGP connection if we receive BGP packets if it's TTL < 255. Also setting this attribute make sure i-BGP frames are originated with IP TTL of 255. How I verify: Manual Verification of above scenario. See blow BGP packets receive with IP TTL 254 (additional routing hop) we are seeing FIN TCP flags as BGP is rejecting the connection Signed-off-by: Abhishek Dosi <abdosi@microsoft.com>
33 lines
1.3 KiB
Django/Jinja
33 lines
1.3 KiB
Django/Jinja
!
|
|
! template: bgpd/templates/voq_chassis/peer-group.conf.j2
|
|
!
|
|
neighbor VOQ_CHASSIS_V4_PEER peer-group
|
|
neighbor VOQ_CHASSIS_V6_PEER peer-group
|
|
address-family ipv4
|
|
{% if CONFIG_DB__DEVICE_METADATA['localhost']['type'] == 'ToRRouter' %}
|
|
neighbor VOQ_CHASSIS_V4_PEER allowas-in 1
|
|
{% endif %}
|
|
neighbor VOQ_CHASSIS_V4_PEER activate
|
|
neighbor VOQ_CHASSIS_V4_PEER addpath-tx-all-paths
|
|
neighbor VOQ_CHASSIS_V4_PEER soft-reconfiguration inbound
|
|
neighbor VOQ_CHASSIS_V4_PEER route-map FROM_VOQ_CHASSIS_V4_PEER in
|
|
neighbor VOQ_CHASSIS_V4_PEER route-map TO_VOQ_CHASSIS_V4_PEER out
|
|
neighbor VOQ_CHASSIS_V4_PEER send-community
|
|
neighbor VOQ_CHASSIS_V4_PEER ttl-security hops 1
|
|
exit-address-family
|
|
address-family ipv6
|
|
{% if CONFIG_DB__DEVICE_METADATA['localhost']['type'] == 'ToRRouter' %}
|
|
neighbor VOQ_CHASSIS_V6_PEER allowas-in 1
|
|
{% endif %}
|
|
neighbor VOQ_CHASSIS_V6_PEER activate
|
|
neighbor VOQ_CHASSIS_V6_PEER addpath-tx-all-paths
|
|
neighbor VOQ_CHASSIS_V6_PEER soft-reconfiguration inbound
|
|
neighbor VOQ_CHASSIS_V6_PEER route-map FROM_VOQ_CHASSIS_V6_PEER in
|
|
neighbor VOQ_CHASSIS_V6_PEER route-map TO_VOQ_CHASSIS_V6_PEER out
|
|
neighbor VOQ_CHASSIS_V6_PEER send-community
|
|
neighbor VOQ_CHASSIS_V6_PEER ttl-security hops 1
|
|
exit-address-family
|
|
!
|
|
! end of template: bgpd/templates/voq_chassis/peer-group.conf.j2
|
|
!
|