Open v435 opened 6 months ago
This issue is stale because it has been open 180 days with no activity. Comment or remove the autoclose
label in order to avoid having this issue closed.
This issue will be automatically closed in the specified period unless there is further activity.
Description
Hi! For some reason even when the NVE receives an RT-5 route with Gateway IP field filled in, Gateway IP won't be used as the overlay index, even though the corresponding RT-2 route is present in the FIB. RT-5 get installed as "pure" RT-5 routes (with RMAC as the overlay index).
Topology and description
Systems involved
What the systems are doing
This is how Wireshark sees one of the RT-5 routes (note that the Gateway IP is non-zero). This was captured on PE-2's e1 interface (facing PE-1).
Version
How to reproduce
TS-1 Config:
PE-1
PE-1 FRR Config:
PE-1 OS Config
PE-2
PE-2 FRR Config
PE-2 OS Config:
Expected behavior
The RT-5 routes get installed with TS-1's IP address (192.168.100.1) as the next-hop. The next-hop is resolved recursively through the RT-2 route for the TS-1 address.
Actual behavior
The RT-5 routes get installed as "pure" RT-5 routes, with the next-hop set to PE-1's VTEP address.
PE-2 FIB:
Additional context
Looking at the source code it seems to me that the issue could be related to where FRR looks for the resolved next-hop. It seems to look it up in the table which you can see by issuing the "show bgp nexthop" command which contains next-hops of the underlay BGP session. But it's hard for me to say for certain.
Checklist