mirror of
https://git.proxmox.com/git/mirror_frr
synced 2025-08-06 06:14:35 +00:00
a04f1c42eb
MPLS VPN networks can either peer with iBGP or eBGP. When calculating the distance to send to zebra, the imported prefix is never sent with distance information, even if the vty command is used under the ipv4 unicast address family: router bgp 65505 vrf vrf1 address-family ipv4 unicast distance bgp 26 27 28 [vpn config] The observation is that the distance sent to zebra for an imported prefix is still 20: [..] VRF vrf1: B> 192.168.0.0/24 [20/0] via 2.2.2.2 (vrf default) (recursive), label 20, weight 1, 00:00:12 * via 10.125.0.6, ntfp3 (vrf default), label implicit-null/20, weight 1, 00:00:12 The expectation is that the incoming prefix has to follow the distance that is configured, or the distance derived from the peer relationship established by the parent prefix. In the case, an iBGP relationship is done, and no distance configuration is done, the below show is expected: [..] VRF vrf1: B*> 192.168.0.0/24 [200/0] via 192.168.0.2, r1-gre0 (vrf default), label 20, weight 1, 00:00:12 In the case an iBGP relationship is done, and distance configuration is performed as below: [..] distance bgp 21 201 41 [..] Then the below show is expected: [..] VRF vrf1: B*> 192.168.0.0/24 [201/0] via 192.168.0.2, r1-gre0 (vrf default), label 20, weight 1, 00:00:12 To get this behaviour, get the peer origin where the prefix is coming from. Signed-off-by: Philippe Guibert <philippe.guibert@6wind.com> |
||
|---|---|---|
| .. | ||
| bgpd | ||
| helpers | ||
| isisd | ||
| lib | ||
| ospf6d | ||
| ospfd | ||
| topotests | ||
| zebra | ||
| .gitignore | ||
| Makefile | ||
| pytest.ini | ||
| runtests.py | ||
| subdir.am | ||