812e1a3489
**- Why I did it** FRR introduced [next hop tracking](http://docs.frrouting.org/projects/dev-guide/en/latest/next-hop-tracking.html) functionality. That functionality requires resolving BGP neighbors before setting BGP connection (or explicit ebgp-multihop command). Sometimes (BGP MONITORS) our neighbors are not directly connected and sessions are IBGP. In this case current configuration prevents FRR to establish BGP connections. Reason would be "waiting for NHT". To fix that we need either add static routes for each not-directly connected ibgp neighbor, or enable command `ip nht resolve-via-default` **- How I did it** Put `ip nht resolve-via-default` into the config **- How to verify it** Build an image. Enable BGP_MONITOR entry and check that entry is Established or Connecting in FRR Co-authored-by: Pavel Shirshov <pavel.contrib@gmail.com> |
||
|---|---|---|
| .. | ||
| docker-base | ||
| docker-base-buster | ||
| docker-base-stretch | ||
| docker-basic_router | ||
| docker-config-engine | ||
| docker-config-engine-buster | ||
| docker-config-engine-stretch | ||
| docker-database | ||
| docker-dhcp-relay | ||
| docker-fpm-frr | ||
| docker-fpm-gobgp | ||
| docker-fpm-quagga | ||
| docker-iccpd | ||
| docker-lldp | ||
| docker-nat | ||
| docker-orchagent | ||
| docker-platform-monitor | ||
| docker-ptf | ||
| docker-ptf-saithrift | ||
| docker-router-advertiser | ||
| docker-sflow | ||
| docker-snmp | ||
| docker-sonic-mgmt | ||
| docker-sonic-mgmt-framework | ||
| docker-sonic-restapi | ||
| docker-sonic-telemetry | ||
| docker-teamd | ||
| dockerfile-macros.j2 | ||