-
Notifications
You must be signed in to change notification settings - Fork 171
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Do a route table lookup post vrf translation
In the most common packet path, a route lookup always happens after flow lookup. But there can be cases when a flow lookup happens post a route table lookup. In such cases, if a translation happens, then the destination ip should be looked up in the new route table. Exception to this case is when packets come from fabric where the label already points to the destination nexthop and no further lookup is needed (which is what happens today). Change-Id: If2191dc73b9764107900119cffa4eabbfc23c899 Closes-Bug: #1435746
- Loading branch information
1 parent
51b96de
commit b6a64ec
Showing
4 changed files
with
65 additions
and
39 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters