-
Notifications
You must be signed in to change notification settings - Fork 265
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
ovn-controller: Enforce ovn-encap-ip-default for non-lsp traffic.
Currently, when multiple encap IPs are configured using ovn-encap-ip, it is possible to specify a default encap IP using ovn-encap-ip-default. This default is used when an encap IP is not explicitly specified for certain VIFs associated with LSPs, ensuring the default encap IP is selected instead of a random one. However, this default configuration does not take effect at the egress side in scenarios where packets are generated from non-LSP interfaces or external networks into the overlay. The issue arises because the default encap-id is 0, which corresponds to the index of the encap-ips array. The array order, however, does not account for the ovn-encap-ip-default setting. This patch addresses the issue by ensuring that the default encap IP, if configured, is always placed at index 0 of the encap-ips array. Fixes: 6559b44 ("ovn-controller: Support ovn-encap-ip-default option.") Signed-off-by: Han Zhou <hzhou@ovn.org> Acked-by: Mark Michelson <mmichels@redhat.com> (cherry picked from commit 17605c3)
- Loading branch information
Showing
2 changed files
with
122 additions
and
0 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